potlock.org/legos-explained to share and for full miro checkout potlock.org/legos

Funding Layer; denotes the composable stack & phases of interaction / modules for PotLock protocol under the hood.

Funding Layer both denotes part of the stacks and also interactions between phases.

It is important to note rather than experiment, we are looking to use this stack to translate to direct technical implementation.

Objectives

• Outline public goods primitives to signal builders to build this out
• Build plural funding mechanisms
• Encourage others to contribute to the stack

The Stack

The stack consists of a high level overview of all the clients (front end portals), middleware (APIs, RPCs, sybil providers, MPC solutions, onramps and offramps, and smart contracts consists of PotLock’s NEAR Smart contract, future contracts on other Rust based L1s, and other EVM based contracts from ecosystem in the ALlo Stack. Additionally through account aggregation and different front ends we aim to composable put these modular public goods funding mechanisms into a unified experience.

Front Ends

• BOS Components: Denotes decentralized front ends
  • Monolithic application: denotes a decentralized front end app that is embedded into one experience accesible through any gateway
  • A PotLock gateway: denotes a specialized clients that leverages these BOS components
  • Mobile BOS Gateway: denotes a specialized mobile native application that runs decentralized front ends in a VM to that device.
• Mobile App:
  • Denotes leveraging NEAR Social API, NEAR API and other tools to build a mobile first experience where components are not rendered from front ends, but rather data is retrieved on chain.
  • This can experience issues like wallet connections. Ultimately we belive most donations will be mobile first. However interopability, i.e integration into other dAPps and sybil providers will be a difficult issue
  • As of 2023, over 60% of the global population owns a smartphone, with this number expected to reach 80% by 2025.
• Traditional Progressive Web Apps
  • This can take the form of a tranditional Web App like ReactJS or NextJS
  • This allows us to use more composable
  • Additionally traditional PWAs can elverage decentralized hosting solutions like Fleek.co for redundnace
  • THe ultimatley goal is for faster render times, integration into external SDKs and non evms blockchains, use of hooks, and a plethora of functionality that BOS limits
• Data Dashboards
  • Traditional front end dashbaords for tracking on chain and client based activiity.

Middleware

Middleware consists of APIs, authentication services, onramps, offramps, metransactsion relayers that serves a microservcies to the funding legos.