Skip to main content
Kokonut is an open-source, open-data ecosystem for regenerative farms, DAO governance, MRV evidence, and agent-powered coordination. Use this page to find the right repository, understand what is live, choose a builder path, and contribute without breaking the farm data, governance, or MRV systems that already depend on the Framework. Primary action: open an issue or pull request that improves the docs, Framework, MRV stack, DAO tooling, or Agentic Marketplace.

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

Do not describe planned infrastructure as live. Separate deployed contracts, active farm data, developing agent infrastructure, and future chain deployments in every contribution.

GitHub repositories

Repository rules

Before opening a pull request:
  1. Check open issues for related work.
  2. Open an issue first for non-trivial changes.
  3. Run the local preview or test suite.
  4. Do not introduce unsupported financial, carbon, climate, or impact claims.
  5. Do not treat forecasts as actuals.
  6. Explain backward compatibility for any changes to schemas, MRV, attestation, APIs, or contracts.
The docs are MDX. Avoid custom <Table> components unless the component exists in the Mintlify setup. Use Markdown tables for safer rendering. Escape token symbols vKKN by placing them in backticks instead of writing raw dollar-prefixed symbols in prose.

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.
When building integrations, key against these field names. Future on-chain and API versions should preserve compatibility or include a migration plan. Read the Common Data Schema →

MRV data primitives

MRV is the trust layer that turns farm activity into public evidence.
A complete MRV event should include the farm ID, timestamp, measurement type, data source, payload, and, when available, an attestation reference.

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.
EAS attestations make records inspectable; they do not automatically prove that a claim is scientifically certified, financially guaranteed, or eligible for carbon credits. Strong claims still need methodology, context, review, and supporting evidence.

Direct contract queries

Until dedicated subgraphs are available, builders can query the DAO directly through Gnosis RPC or existing DAOHaus indexing.
Suggested builder tasks:
  • Build a member balance viewer for vKKN Loot.
  • 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

Read Kokonut x AI Agents →

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:
  1. Draft the proposal using the right template.
  2. Keep it open for the required feedback window.
  3. Secure sponsorship from a proposal-authorized person.
  4. Move to DAOHaus voting when ready.
  5. Execute and report if the proposal passes.
Read Proposal Templates →

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.
Not sure where to start? Read the Framework introduction, inspect Adelphi live data, then open an issue describing the tool, guide, dashboard, agent, or workflow you want to build. The Technology Guild can help route the work.