• Fleek Network has launched a new whitepaper for its decentralized edge platform.
• This platform is designed to provide a shared performance layer for Web 3.0 protocols, services and apps.
• Features include a protocol-agnostic architecture, stateless execution, a VM-less core and content addressing.
Fleek Network Launches Whitepaper for Decentralized Edge Platform
Fleek Network has released a new whitepaper describing the decentralized edge platform it is developing with an accompanying launch of a new open-source Github repository for the protocol. The whitepaper outlines an evolution from the original research focused on a decentralized CDN to support a much wider range of decentralized edge services such as serverless functions, SSR (server-side rendering), container orchestration and various database functions.
Motivation Behind Developing the Platform
The development of this platform was driven by recognition of infrastructure trends that have seen the modern web migrate from the cloud to the edge due to increasing user base and low latency demands globally. With this in mind, Fleek Network intends to provide a shared performance layer that all Web 3.0 protocols can leverage rather than building redundantly for every service or protocol separately.
Features of Fleek’s Protocol Design
The features included in Fleek’s protocol design result in work performed by nodes across the network being determined solely by geography and a performance-based reputation score without needing any virtual machines or other tools. This makes it possible for Fleek’s edge platform to add value to virtually any Web 3.0 protocol, service and app while also providing overall improved performance with low latency thanks to attributes like stateless execution, content addressing and several other optimizations introduced in their whitepaper release.
Impact on Web 3 Development
According to Harrison Hines, CEO and co-founder of Fleek Network, “Introducing a highly-performant decentralized edge network into the Web 3 stack as a shared performance layer could help close the gap between Web 2.0 and Web 3 performance and provide an important building block for developers on their way towards mass adoption.”