Skip to content

Home

Jump to bottom
Janison Sivarajah edited this page Dec 21, 2022 · 21 revisions

👋🏼 Welcome to the NFAs wiki!

This is the landing point for Fleek's initiative to implement infrastructure as Solidity contracts. The vision is to have this on a suitable L2 or L3 based on EVM so there is flexibility in terms of which chains to work with. And we can create a network of smart contracts that represent the different parts of your stack. The goal is to be a more verifiable and crypto-friendly Serverless.yaml or Cloudformation manifests and unlock useful features on top of that framework.

❓Why Contracts

With the availability of L2's like Polygon. It made sense for us to develop this as Solidity contracts to leverage the crypto benefits that you get by moving some of this stuff on-chain but still not sacrifice on performance or cost. Some of the motiviations for this to unlock the following future benefits:

  • governance: on-chain management of your dapp (e.g., build settingss and integrations to DAOs)
  • automation: automate control of on-chain infrastructure (e.g., remove team member address from access control across your infra)
  • access: create an unstoppable access point for your apps (e.g., access your app through decentralized access points like Ethereum and IPFS) and most noteably our community hosting capability that will be our first priority after the baseline contracts are done
  • tokenization: buy, sell, stake, etc (i.e., ERC721 support and other forms of tokenization as needed for the baseline contracts and features built on top)

🛣️ High Level Roadmap

  1. Standalone Proof-of-concept (POC)
  • Basic structure of contracts, static sites use case, minimal metadata, ERC721 integration, access control
  • Minimal UI (minting, listing, viewing, visiting)
  • Documentation (installing, running, testing, contributing) and Wiki (project structure, engineering topics)
  • Open source
  • Discuss utility of product and value creation/extraction

We are here 🏁

  1. Contracts and UI Updates
  • Further testing and review
  • Basic structures for community hosting
  • Update UI to support community hosting usecase
  • Add more metadata/functionality
  • Proxy
  • Gas optimizations, security review, fuzz testing
  • Finalize testnet instance

2.5 Offchain Components

  • Fleek API to verify source to build
  • DNS verification API
  • Watchers to availability sample community hosters
  1. Audit and Deploy to mainnet

At this point MVP is complete 🏁 MVP! MVP! MVP! durantcrying.gif

  1. Further Integration to Fleek XYZ

  2. Standardization

  3. Extensions

  • Verification (code, phishing, other integrations)
  • Lens integration
  • Ceramic integration
  • Meta-transactions (requires discussion)
  • New infra types (backend, contracts)

💡Background

Fleek presented "sites as nfts" originally and the idea was take make web applications deployed on Fleek NFTs and mint them on chain and find useful applications for the community. Since then we have been discussing the concept and what the next steps should be including ramping up on the POC work for it. Some of the discussion can be found at https://github.com/FleekHQ/fleek/discussions/20. This wiki is the starting point of capturing any further development in this repo and wiki with the aim to open source it as soon as possible and building this with the community.

🐛 Bug reporting

If you have found a bug to report, please create an issue. Thank you!

From Fleek ⚡ with ❤️

Clone this wiki locally