Skip to main content

​
Answers for people trying to understand Kokonut quickly.

Kokonut is open coordination infrastructure for regenerative agriculture. It connects locally operated farms with:
  • capital governance;
  • contributor coordination;
  • shared implementation methods;
  • public farm evidence;
  • open-source data infrastructure;
  • developing automation and AI-agent workflows.
Kokonut is not one DAO controlling everything. Different responsibilities belong to different actors:
  • the Moloch DAO governs shared capital and DAO-level rights;
  • Guilds coordinate useful work and domain review;
  • local farm operators make day-to-day agricultural decisions;
  • the Kokonut Framework provides shared methodology and data structures;
  • MRV, the Kokonut Hub, and Kokonut Intelligence make farm activity easier to inspect;
  • contracts and agents support bounded execution and automation.
The quickest way to evaluate Kokonut is to separate documented state, measured activity, forecasts, attestations, interpretations, and developing infrastructure instead of treating them as the same thing.

Start with Kokonut 101

Read the concise orientation to the live farm, coordination layers, Framework, MRV, and participation paths.

Inspect the live reference farm

Use the Kokonut Hub for current published Adelphi records rather than relying only on static documentation.

Understand governance

See how capital, contribution, farm operations, methodology, evidence, and technical execution are separated.

Contribute without capital

Start with useful, reviewable work in agriculture, research, MRV, software, documentation, governance, finance, or partnerships.
This FAQ is an orientation layer. For legal, tax, investment, land-title, employment, securities, regulatory, or professional scientific questions, use qualified professional advice and the relevant primary records.

​
FAQ at a glance

​
Choose your path

Understand the ecosystem

Start with Kokonut 101 and the live-vs-developing map.

Inspect Adelphi

Review the first live reference farm, documented state, physical systems, forecasts, MRV, and SDG evidence.

Contribute useful work

Enter through work rather than capital.

Participate in capital governance

Understand membership, $vKKN, Loot, proposals, treasury rules, and rage-quit.

Build with Kokonut

Work with the public docs, Framework, data schemas, MRV tooling, governance infrastructure, and developing agent systems.

Work with farm data

Explore Kokonut Intelligence, canonical records, analytics, reporting, and Celo EAS infrastructure.

​
Basics

Kokonut Network is open coordination infrastructure for regenerative agriculture.The current ecosystem combines:Start with the Executive Summary.
Kokonut includes a live DAO, but Kokonut is not one DAO governing everything.The Moloch DAO governs shared capital and DAO-level rights.It does not automatically control:
  • farm operations;
  • scientific truth;
  • Guild expertise;
  • every Framework method;
  • MRV review;
  • all software decisions.
Read DAO Architecture.
Kokonut focuses on coordination gaps around regenerative agriculture.A farm can have land, local knowledge, ecological potential, and community value while still lacking:
  • capital coordination;
  • infrastructure;
  • shared implementation methods;
  • evidence;
  • contributor coordination;
  • market and reporting capacity;
  • reusable learning.
Kokonut’s response is to connect those functions without requiring one institution or token to control them all.Read The Problem and The Solution.
The Kokonut Framework is the shared methodological baseline for Kokonut farms.It includes areas such as:
  • the Common Data Schema;
  • development phases;
  • regenerative principles;
  • MRV expectations;
  • value-accounting concepts;
  • impact methods;
  • documentation and governance interfaces.
The Framework is intended to create interoperability, not uniformity.A future farm should be able to reuse common structures without copying Adelphi’s crops, operators, market, ecology, or local context.Read the Kokonut Framework.
Syntropic farming is a regenerative agriculture approach built around diversity, succession, multiple vegetation layers, biomass, soil cover, and long-term ecological relationships.Kokonut uses syntropic principles as part of its agricultural methodology, but the Framework is broader than one farming technique.Read Why Syntropic Farming.
The ecosystem is at different maturity levels.A developing system should not be described as if it already has the authority or production maturity of a live contract or operating farm.

​
Farms and real-world implementation

Adelphi is Kokonut’s first live reference farm in Gonzalo, Monte Plata, Dominican Republic.Current documented reference values include:It is a women-led project founded by sisters Yanny and Neury Hernández and was supported by Public Nouns Proposal #69.These are documented reference values, not a substitute for current farm records.Use the Kokonut Hub for current published data.
Adelphi demonstrates that several Kokonut components can operate together in one real farm context:
  • local farm operations;
  • farm funding;
  • Framework methods;
  • crop and infrastructure systems;
  • MRV;
  • public records;
  • governance;
  • contributor coordination.
Adelphi does not by itself prove:
  • universal multi-farm scalability;
  • guaranteed farm economics;
  • biodiversity restoration;
  • verified carbon outcomes;
  • identical results at future farms;
  • automatic community-level social impact.
Read the Adelphi Overview.
Adelphi uses diversified production across different timelines.Current documentation includes:
  • short-cycle vegetables such as lettuce;
  • passion fruit and other medium-cycle crops;
  • coconut and perennial agroforestry species;
  • poultry eggs;
  • nursery propagation;
  • syntropic plots;
  • biological inputs and biochar.
Production forecasts should not be confused with recorded harvest actuals.Read Crops, Biodiversity & Infrastructure and Crops & Harvest Forecast.
No.The crop page contains a planning model.Its combined crop figure is a steady-state gross-revenue scenario built from assumptions about:
  • crop counts;
  • yield;
  • losses;
  • prices;
  • harvest frequency;
  • crop maturity.
It is not:
  • realized revenue;
  • net income;
  • profit;
  • distributable DAO cash;
  • guaranteed operator income.
Actuals should be compared against the forecast over time.Read the Forecast Model.
No universal revenue split should be assumed.Revenue allocation depends on the approved economic and governance arrangements for the specific farm.The repository currently documents conflicting historical Adelphi allocation models, which is why newer farm pages avoid presenting one percentage as a universal rule.A current approved agreement or governance record should take precedence.
Terra Viva is the next documented replication test, not an already operating extension of Adelphi.Current Kokonut documentation describes roughly 50,000 m² of adjacent land under agreement entering Phase I — Planning & Preparation.It should be treated as planning-stage work until operating records show otherwise.
Visits should be coordinated with the Kokonut team and the local farm operators.The public documentation does not establish Adelphi as an unrestricted walk-in site.A visit should respect:
  • current farm operations;
  • local operator priorities;
  • safety;
  • privacy;
  • community context.
Book a meeting →

​
Governance, $vKKN, Loot, and rage-quit

The Kokonut Moloch DAO is the capital-governance layer.It covers areas such as:
  • membership;
  • treasury allocation;
  • funded proposals;
  • $vKKN issuance;
  • Loot issuance;
  • DAO-level governance parameters;
  • rage-quit protections.
It does not automatically control farm operations, scientific review, or every Guild/Framework decision.Read Kokonut Moloch DAO.
The current architecture is designed so the Core Team does not have unilateral authority over the DAO treasury.DAO-level treasury actions are intended to follow the applicable governance and execution process.That statement should not be expanded into “no trusted role exists anywhere.”Kokonut also has:
  • farm accounts;
  • technical systems;
  • operational processes;
  • legal/off-chain relationships;
that are not all identical to the Moloch treasury.
$vKKN is the current non-transferable Moloch voting token.Under the current docs:
  • 1 $vKKN = 1 Moloch vote;
  • issuance happens through approved DAO proposals;
  • it is non-transferable / soulbound;
  • it participates in the current Moloch governance model.
Kokonut documentation also relates $vKKN issuance to coconut trees.That relationship does not by itself create:
  • legal title to land;
  • ownership of an individual tree;
  • authority over farm operators;
  • guaranteed financial returns.
Read Kokonut Moloch DAO.
Loot is the current non-voting, non-transferable DAO token primitive used for recognized participation / economic rights under the current model.Loot differs from $vKKN because it does not carry Moloch voting power.Loot issuance still requires the applicable DAO proposal and approval process.A contribution does not automatically become Loot.
No.Token ownership is not land title.Local farm ownership, operating rights, legal agreements, and land records are separate from Moloch token rights.A treasury vote can authorize capital.It does not automatically transfer:
  • land ownership;
  • local farm authority;
  • agronomic decision-making.
Rage-quit is a Moloch exit mechanism for eligible members and eligible treasury assets under the applicable rules.It can allow an eligible member to burn applicable tokens and receive a proportional share of eligible treasury assets.Rage-quit is not a guarantee of recovering the original contribution value.Actual outcomes depend on:
  • treasury composition;
  • eligible assets;
  • token supply;
  • contract state;
  • applicable governance rules.
Read the Moloch DAO page.
The current capital path uses a membership proposal.A prospective member proposes a stablecoin tribute and requested $vKKN amount under the current rules.Membership terms can change.Do not rely on an old static tribute ratio, member percentage, or token supply.Check the live DAO before acting.
Under the current core governance documentation, both are non-transferable.If another page says otherwise, the live contracts and current Moloch documentation should be checked before relying on that older language.

​
Guilds and contribution

Yes.The contribution path exists so useful work does not require capital membership first.Common contribution areas include:
  • agriculture;
  • research;
  • MRV;
  • documentation;
  • software;
  • governance;
  • finance;
  • partnerships;
  • community coordination.
Start with Open Collaboration.
Guilds are the contribution-coordination layer.Current domains are:Guilds can coordinate domain work and review.They do not have unilateral treasury authority.Read Kokonut Guilds.
Guild Points are a developing contribution-reputation mechanism.The design intent is that they represent reviewed, non-transferable, domain-specific contribution.But the exact mechanics remain evolving, including areas such as:
  • point values;
  • thresholds;
  • formal standing;
  • voting weight;
  • Steward selection;
  • on-chain representation.
A contribution does not automatically create:
  • Guild Points;
  • payment;
  • Loot;
  • $vKKN;
  • employment;
  • governance rights.
The most durable model is:
useful work → contribution record → domain review → accepted contribution history → recognition
Significant contributions can later support a separate Loot proposal if appropriate.The contribution record matters because it preserves:
  • what was done;
  • who did it;
  • evidence;
  • reviewer;
  • status;
  • dependencies;
  • follow-up.
Steward is best understood as a coordination function, not automatic permanent authority.Stewardship can include:
  • maintaining work queues;
  • helping contributors find tasks;
  • review coordination;
  • documenting decisions;
  • routing mature work toward governance when needed.
Selection, term, rights, and removal should be explicitly documented by the relevant Guild process rather than assumed.
A Guild can provide expertise, research, tools, review, and recommendations.It does not automatically replace local farm operators.Routine decisions such as:
  • crop timing;
  • irrigation;
  • maintenance;
  • field response;
  • labor coordination;
remain within the relevant farm-operating scope.

​
Proposals and decision-making

No.Governance starts by asking:
Which authority actually owns this decision?
Examples:Read the Governance Framework.
The current governance process generally separates:
  1. decision routing;
  2. drafting;
  3. domain review;
  4. authorized activation;
  5. Moloch voting where required;
  6. grace / retention checks;
  7. transaction execution;
  8. operational delivery;
  9. evidence and acceptance;
  10. closeout.
Passed, executed on-chain, and completed in the real world are different statuses.
The current Governance Framework documents:
  • minimum 5-day drafting baseline;
  • 5-day active Moloch voting baseline;
  • grace after a passing on-chain proposal;
  • current 66% token-retention protection;
  • 0% onboarding quorum under the current membership framework.
These are current governance parameters, not permanent natural laws.Verify live rules before a binding action.
The current toolkit includes six families:Read Proposal Templates.
A strong proposal clearly defines:
  • authority requested;
  • out-of-scope authority;
  • evidence;
  • budget;
  • recipients;
  • reviewers;
  • execution owners;
  • acceptance criteria;
  • risks;
  • dependencies;
  • conflict-of-interest disclosures;
  • material-change rules;
  • closeout.
A proposal should be auditable before approval and closeable after execution.

​
MRV, evidence, and impact claims

MRV means Measurement, Reporting, and Verification.In Kokonut, it is the evidence layer that asks:
  • what happened?
  • where?
  • when?
  • how was it measured or reported?
  • what source supports it?
  • was it reviewed?
  • was it published?
  • was it attested?
  • what can reasonably be concluded?
A useful shorthand is:
observe → structure → review → publish → attest when useful → interpret
Read MRV.
No.A sensor reading, farm record, review state, EAS attestation, and impact conclusion are different things.Strong claims still depend on:
  • methodology;
  • baseline;
  • reporting period;
  • evidence quality;
  • reviewer competence;
  • uncertainty;
  • context.
In the Kokonut Intelligence record lifecycle, Verified is an internal workflow state.It means an authorized reviewer or process approved the record.It does not automatically mean:
  • independent scientific certification;
  • regulatory approval;
  • third-party audit;
  • carbon-credit eligibility;
  • external assurance.
The record lifecycle is:draft → submitted → verified / rejected → published
EAS stands for Ethereum Attestation Service.Kokonut uses attestations to improve provenance around important records.An attestation can help show:
  • who made or signed a claim;
  • when it was recorded;
  • which schema it used;
  • which evidence reference it points to.
It does not make the underlying claim scientifically true merely because it is on-chain.
No.Not every sensor reading, photo, invoice, or field note needs an on-chain transaction.Detailed evidence can remain:
  • in governed databases;
  • off-chain;
  • in private storage;
  • in IPFS/Filecoin evidence packages when useful.
Significant claims can be attested when public provenance adds value.Sensitive evidence can remain off-chain with selective disclosure where appropriate.
The documentation follows a proof-before-claims approach.Important distinctions include:
  • documented state vs. forecast;
  • measurement vs. interpretation;
  • attestation vs. scientific verification;
  • implemented practice vs. demonstrated ecological outcome;
  • SDG alignment vs. verified impact.
A claim should become stronger only as the supporting evidence becomes stronger.
The SDGs are an evidence-mapping and interpretation layer, not automatic impact certification.Adelphi currently uses five primary SDGs:
  • SDG 1 — No Poverty;
  • SDG 2 — Zero Hunger;
  • SDG 5 — Gender Equality;
  • SDG 8 — Decent Work and Economic Growth;
  • SDG 15 — Life on Land.
The current farm pages distinguish:alignment → activity → measured outcome → impact interpretationRead Adelphi SDGs.
No.Practices such as agroforestry, biochar, syntropic planting, ground cover, and biodiversity work can support ecological objectives.But claims about:
  • carbon sequestration;
  • biodiversity recovery;
  • ecological credits;
  • soil improvement;
  • erosion reduction;
require the appropriate evidence, methodology, reporting period, and any external standards or validation required by the claim.

​
Kokonut Intelligence, chains, and AI agents

Kokonut Intelligence is the data, analytics, verification, and agent-access layer of the ecosystem.It structures information across:
  • farm operations;
  • harvests;
  • expenses;
  • sales;
  • soil data;
  • remote sensing;
  • MRV;
  • attestations;
  • partner data;
  • agent logs.
It supports:
  • review workflows;
  • dashboards;
  • forecasting;
  • scoring;
  • reports;
  • EAS attestations;
  • agent access.
Kokonut Intelligence does not replace MRV methodology.MRV defines how evidence should be handled; Kokonut Intelligence implements data infrastructure around that process.Read Kokonut Intelligence.
Current documentation separates chain roles.Roadmap chains or older builder references should not be treated as active deployments unless current deployment evidence exists.
Yes, but the role is bounded.Useful agent workflows include:
  • MRV draft preparation;
  • data-quality checks;
  • harvest forecasting;
  • forecast-vs-actual analysis;
  • proposal formatting;
  • report drafting;
  • evidence packaging;
  • anomaly detection.
Agents should not independently:
  • approve treasury spending;
  • create governance authority for themselves;
  • certify scientific claims;
  • replace farm operators;
  • silently change schemas;
  • publish high-impact claims without review.
It is currently documented as in development.Builders can work against the current repository and development architecture, but production behavior should not be claimed until deployment details are explicitly published.
An AI workflow should not be treated as an autonomous treasury authority.Kokonut’s current direction emphasizes bounded, reviewable execution.Governance authorization, transaction preparation/proposal, human confirmation where required, and final execution are different steps.High-impact treasury actions should remain accountable to the applicable governance and wallet security model.
Yes.Current builder areas include:
  • public documentation;
  • Framework schemas;
  • DAO tooling;
  • farm-data tooling;
  • MRV;
  • Kokonut Intelligence;
  • dashboards;
  • attestations;
  • forecasting;
  • agent workflows.
Start with Build with Kokonut.
The public documentation and multiple core software repositories are open source.The public Knowledge Base is maintained in:Kokonut-Public-Site on GitHub →Contributions should follow the repository’s contribution and compatibility rules.

​
Risks, limits, and trust checks

No.Kokonut documentation explains:
  • governance;
  • farm methods;
  • data infrastructure;
  • forecasts;
  • contribution paths;
  • public records.
It is not legal, tax, investment, securities, or financial advice.Forecasts and scenarios are planning tools, not guaranteed outcomes.
No.Farm outcomes depend on real-world variables including:
  • weather;
  • pests;
  • disease;
  • crop survival;
  • labor;
  • irrigation;
  • prices;
  • buyers;
  • transport;
  • operating costs;
  • governance;
  • execution quality.
Token participation also does not create a guaranteed economic return.
Transparency reduces some coordination risk.It does not eliminate real-world uncertainty.
Check primary evidence rather than relying on one narrative page.Useful questions include:
  • Can I inspect Adelphi’s public records?
  • Can I see what is documented versus forecast?
  • Can I inspect DAO contracts and current governance state?
  • Are $vKKN, Loot, and Guild Points described at their actual maturity?
  • Can I trace an impact claim to evidence?
  • Does an attestation have a source record behind it?
  • Are local operators clearly distinguished from token holders?
  • Are developing agent systems labeled as developing?
  • Are material risks and assumptions visible?
Different questions have different best sources.Static documentation should not override newer live records where the underlying state can change.

​
Still have questions?

Read Kokonut 101

Get the shortest complete orientation to the model and current maturity.

Explore Adelphi

Review the first live reference farm and its evidence boundaries.

Understand the DAO

See which decisions belong to capital governance, Guilds, farms, methodology, evidence, and technical systems.

Contribute

Start with one useful, bounded, reviewable contribution.

Build

Find repositories, schemas, contracts, MRV primitives, data infrastructure, and agent development paths.

Read the Glossary

Look up Kokonut-specific governance, farm, MRV, data, and agent terminology.
When in doubt, separate the claim into its parts: what exists, what was measured, what was forecast, what was reviewed, what was attested, what was interpreted, and what is still being built.