Skip to main content

Network Architecture

Actor Overview​

Kariba​

Policy Engine​

The policy engine defines the funding policy for the program. It takes as input, preferences from the community (e.g. governance votes) and metrics as measured by OSO, and produces a funding schedule to the funding agent.

Some example policies we could take inspiration from:

  • linear - users directly choose how much projects get (e.g. Optimism RF3)
  • quadratic - users influence quadratic funding (e.g. Gitcoin matching funds)
  • metric funding - users choose which metrics are worth funding, which generates a project funding schedule (e.g. Optimism RF4)

Funding agent / contracts​

The policy engine should produce a funding schedule, that defines how much each project receives per funding period. The funding agent takes the schedule and allocates funding into onchain contracts for the projects to claim. Funding agents are often empowered by an ecosystem treasury, but in theory anyone could contribute to a funding pool.

Ecosystem​

Projects / Users​

Developers build applications, services, and experiences for users, which bring revenue to the ecosystem. The goal is to fund the work that best delivers value to users and increases revenue for the ecosystem. In crypto, this usually comes in the form of transaction fees, but any revenue can work (including enterprise sales).

Goverance​

The primary purpose of governance in this model is to define what "good" looks like. Good will look different in every ecosystem, and embodies a unique combination of goals and strategy into a North Star for the entire ecosystem.

Open Source Observer​

OSO serves as the measurement infrastructure across the entire ecosystem, measuring governance, project activity, user behavior, and financial flows. As an open source, open data, open infrastructure data pipeline, a public community of data scientists and engineers evolve the data models, insights, and metrics, used for better governance.