Fleek Network Testnet Phase {3} Official Release & Instructions

The Fleek Foundation is excited to announce the launch of Fleek Network Testnet Phase {3}! This phase is the first showcase of Fleek Network's edge computing features, establishing a foundation for future services and use cases to come in Phase {4} and Mainnet.

In Phase {3}, participants have the opportunity to create and deploy decentralized edge functions powered by Fleek Network. The code playground is live for anyone that wants to deploy their first Fleek Network Edge Function: https://play.fleek.network/

Schedule:

Important: Anyone interested is encouraged to create, deploy, and test edge functions during this phase. However, it is important to note: Phase {3} is the last temporary, short lived testnet phase before the launch of Phase {4}, which will be a more stable, long running, and permanent testnet. Therefore it is recommended to wait until Phase {4} before integrating any Fleek Network powered infrastructure or services (ex. edge functions) into your production builds.


Phase {3} Goals and Metrics Overview

There are two main goals for Phase {3}:

  1. Test different node setups (node specs, # of nodes, geographic distribution, etc.) to analyze the impact on performance.

  2. Test the first developer facing service running on the network (edge functions).

Part of the reason Phase {3} involves no external node operators is so that different node setups can be easily tested and changed between epochs.This testing will allow the core team  to better determine the initial node setup that will be used during Phase {4} testnet to balance high performance without grossly underutilizing node/network resources.

Throughout Phase {3}, the core developers will be switching node counts dramatically between epochs to test various setups, and doing that efficiently is only possible if 2f+1 number of nodes is controlled internally. This approach ensures stability and consistency in the network's performance during this service-testing-focused phase, while also allowing the core developers and community members to set their focus on deploying and testing the first Fleek Network use cases.

The performance of the Edge Compute service will be closely monitored throughout this phase, with a focus on several key metrics that the core developers have tracked throughout the testnet rollout.

Key Metrics:

  • Network performance under different levels of congestion
    • Correlation between performance and number of active nodes
  • Request distribution (geographic locations)
  • Number of requests (stress testing)
  • Node Synchronizer use frequency

Service-specific metrics:

  • Speed of Request on cache hit vs non-cache hit
  • Ratio of cache hit vs non-cache hit
  • Number of Functions Deployed

As with the previous public testnet phase, metrics from Phase {3} will be published shortly following its conclusion.


Deploying Edge Functions: How-To Guide

To deploy an edge function:


Phase {3} FAQs

How Do I Access the Edge Compute Service?

The Edge Compute service in Phase {3} can be accessed through a code playground here.

Are There Incentives for Participating in Phase {3}?

Refer to this blog for further information regarding testnet participation initiatives. In short, for now, there are no direct incentives during any of the specific testnet phases. Still, there are several overall initiatives (outlined in the Testnet Participation section of the blog linked above).

As a Developer Interested in Trying Edge Compute, What Should I Do?

Developers interested in exploring the Edge Compute service during Phase {3} are encouraged to actively participate and try out the code playground. This is a unique opportunity to interact with Fleek Network for the first time and provide valuable feedback to the core developers. However, it is important to note that Phase {3} is a short-running testnet phase and will conclude on February 14th.

Therefore, while experimentation and feedback are encouraged in Phase {3}, directly integrating these functions into your builds is not recommended until the launch of Phase {4} in late Q1 or early Q2, because Phase {4} will be a more traditional, long-standing testnet that will stay running and eventually fold into Fleek Network mainnet. This approach ensures that developers can work with a more established and reliable version of the network and the infrastructure and services running on it for integration into their builds.

Here is a list of Javascript functions supported during this phase:

  • Basic mathematical functions that can lead up to building an entire calculator.
  • Building and returning JSON objects based on conditions.
  • Deploying farcaster frames.
  • Log user activity, such as clicks or interactions, for analytics purposes.
  • Create serverless functions as custom webhooks to respond to external events in your application.
  • Develop a function to validate and sanitize user input before it's stored in a database.

The Fleek Foundation is super excited to see the cool edge functions that the community will deploy during Phase {3}! Feel free to share what you deploy on Discord or X and tag @fleek_net.

Thank you for testing and looking forward to hearing feedback from the community ⚡

  • Fleek Foundation