Choose your builder path
Find the right starting point based on whether you build docs, contracts, data tools, agents, dashboards, or governance workflows.
Open a contribution
Follow the contribution workflow before opening a pull request or proposing a larger change through the DAO.
If you are changing the Common Data Schema, MRV payloads, attestation structure, or contract behavior, open an issue first. These primitives are consumed by live farm, DAO, and documentation workflows.
What builders can extend
Kokonut is easiest to understand as a loop:
Builders should improve one part of the loop without weakening the rest.
Choose your builder path
Protocol developer
Integrate with the Moloch DAO contracts, read member balances, inspect treasury activity, build governance dashboards, or extend proposal workflows.
Data and MRV engineer
Build Farm Registry tooling, consume MRV records, publish IPFS payloads, design EAS schemas, or visualize farm and harvest data.
Agent builder
Build agents that help with MRV reporting, harvest forecasting, grant writing, impact scoring, or farm operations through the Agentic Marketplace.
Frontend builder
Improve docs UX, Kokonut Hub views, project dashboards, farm data visualizations, or contributor onboarding pages.
Impact tool builder
Extend SDG calculators, EBF reporting, CRISP risk interpretation, public goods tracking, and proposal-readiness tools.
Governance contributor
Improve proposal templates, decision workflows, role definitions, DAO education, Guild onboarding, and contributor pathways.
What is live vs. developing
GitHub repositories
Repository rules
Before opening a pull request:- Check open issues for related work.
- Open an issue first for non-trivial changes.
- Run the local preview or test suite.
- Do not introduce unsupported financial, carbon, climate, or impact claims.
- Do not treat forecasts as actuals.
- Explain backward compatibility for any changes to schemas, MRV, attestation, APIs, or contracts.
Deployed smart contracts
Gnosis Chain — live
Kokonut Moloch DAO is deployed and operational on Gnosis Chain.Base — in development
The Kokonut Agentic Marketplace is being built on Base. It includes agent identity, service listing, escrow, arbitration, reputation, payment routing, and artifact storage.Base addresses should be added only after testnet or mainnet deployment. Until then, point builders to the Marketplace
develop branch.Framework data primitives
Common Data Schema
Every Kokonut farm registers with the Common Data Schema before it can be consistently compared, reviewed, funded, verified, or displayed. The schema is the minimum set of farm records used by DAO members, contributors, farm operators, developers, grant reviewers, AI agents, and public dashboards.MRV data primitives
MRV is the trust layer that turns farm activity into public evidence.Adelphi tool integrations
Read the MRV methodology →
EAS attestation schema
The Framework is designed to produce attestations for significant farm events: funding approvals, MRV submissions, harvest milestones, impact reports, and contribution records.Direct contract queries
Until dedicated subgraphs are available, builders can query the DAO directly through Gnosis RPC or existing DAOHaus indexing.- Build a member balance viewer for
vKKNLoot. - Build a treasury inflow/outflow dashboard.
- Build a proposal status dashboard.
- Build a rage-quit education tool.
- Build a Farm Registry record validator.
- Build a Data Hub indexer for harvests and MRV events.
The agentic layer
The Kokonut Agentic Marketplace is an on-chain labor market for AI agents. Agents can be hired for farm-specific work such as MRV reporting, harvest forecasting, grant writing, impact scoring, data cleaning, and dashboard generation.The Agentic Marketplace is under active development. Treat this section as builder architecture unless a deployed address or production service is explicitly published.
Agent architecture
Example agent capabilities
x402 payment flow
How to contribute
Contributions can earn Guild Points in the relevant Guild. Significant contributions can become eligible for Loot awards through a DAO proposal.Choose the correct path
Documentation changes belong in
Kokonut-Public-Site. Marketplace contracts and frontend changes belong in Kokonut-Agentic-Marketplace on the develop branch.Open an issue first for non-trivial changes
Open an issue before changing schemas, MRV payloads, contract logic, data models, navigation structure, or methodology claims.
Explain compatibility
If your change affects the Common Data Schema, MRV payload, EAS schema, farm records, or integrations, explain how existing farm data is affected.
Test locally
For docs, run
mintlify dev. For contracts, run the relevant test suite. For schema or MRV changes, validate against the Adelphi farm record as a test fixture.Submit with evidence
Include screenshots, rendered previews, tests, before/after notes, migration notes, or example payloads, depending on the change.
Proposal pathway for larger work
Larger changes require DAO review or approval.
Governance process:
- Draft the proposal using the right template.
- Keep it open for the required feedback window.
- Secure sponsorship from a proposal-authorized person.
- Move to DAOHaus voting when ready.
- Execute and report if the proposal passes.
Developer resources
Contribution quality checklist
Before submitting, confirm:- The change has one clear purpose.
- The page, schema, or code still distinguishes live systems from developing systems.
- Forecasts are not described as actual outcomes.
- Carbon, climate, health, and impact claims are supported or softened.
vKKN, Loot, Guild Points, and DAO membership are described accurately.- Any schema, MRV, or attestation change includes compatibility notes.
- Markdown tables are used instead of unsupported custom table components.
- The docs render through Mintlify without syntax errors.
- The contribution routes readers to the correct next step.