Skip to main content

Kokonut governance turns community decisions into enforceable action.

The Governance Framework is Kokonut Network’s operating manual for collective decision-making. It defines who can propose, who can vote, where proposals are drafted, how long decisions take, what every proposal must include, and how treasury-affecting decisions become executable on-chain. Kokonut uses this framework so farm funding, Guild bounties, Framework upgrades, partnerships, and ecosystem decisions can move through a clear process instead of informal approval.
This framework is a governance operating manual, not a comprehensive legal document. It is the baseline for Kokonut Network decision-making and can be amended through the same proposal process it describes.

Governance at a glance

The Governance Framework is the process layer. The Kokonut Moloch DAO is the on-chain execution layer. The Kokonut Guilds DAO is the contribution and domain-expertise layer.

Why this framework exists

Kokonut Network coordinates real farms, real capital, real contributors, real community commitments, and real public-goods outcomes. That requires more than a chat vote or informal agreement. The Governance Framework exists to make sure every important decision has:

Time to review

Every proposal must remain in draft for at least 5 days before it can move to an active vote. This gives members time to ask questions, request edits, and surface risks.

Clear authorization

Proposal-authorized people and Guild Stewards move proposals from draft to vote, making sponsorship visible and accountable.

Defined voting rules

The framework separates off-chain coordination from on-chain treasury voting, so lightweight decisions and capital decisions use the right venue.

Treasury protection

On-chain proposals include a grace period, rage-quit protection, and a 66% retention threshold before execution.

Measurable execution

Every proposal must define success metrics and next steps so the DAO can evaluate whether the work was completed.

Upgradeability

The framework itself can evolve, but only through the same proposal process it governs.

Who can propose and who can vote

Kokonut separates proposal sponsorship, domain contribution, and voting power so the system can recognize both capital and useful work.
Capital gives voting power through $vKKN. Contribution gives operational standing through Guild Points. Significant contribution can later be recognized through Loot, but only if approved through the Moloch DAO proposal process.

Proposal lifecycle

Every Kokonut DAO proposal passes through three mandatory stages. No stage can be skipped.

Drafting Stage

The proposal is written in Kokonut Forum using the required ten-field structure. Vote-authorized members are notified when the draft is posted.The proposal must remain open for a minimum of 5 days. During this window, members and contributors can request clarification, challenge assumptions, suggest edits, and surface risks before a binding vote begins.

Active Stage

A proposal-authorized person sponsors the proposal into the active stage after the drafting window closes.
  • Off-chain coordination proposals can be voted on in Kokonut Forum.
  • Treasury, token, or on-chain execution proposals move to DAOHaus.
Active votes remain open for 5 days and use the voting method assigned to the proposal type.

Grace Period

After an on-chain proposal passes, a grace period opens before execution. DAO members who disagree with the result can rage-quit before the proposal executes.If rage-quits reduce $vKKN token retention below 66%, the proposal does not execute and must be resubmitted.

Execution Stage

Once the vote passes and the grace period closes without breaching the retention threshold, the proposal executes through the DAO.The proposal team then becomes responsible for the stated next steps, success metrics, reporting, and any follow-up documentation.

Minimum timeline

A proposal that affects the treasury cannot be rushed through in one meeting or private conversation.

Voting methods and proposal venues

If a proposal moves treasury funds, mints tokens, awards Loot, changes DAO parameters, or affects on-chain execution, it should be treated as an on-chain governance proposal.

Required proposal fields

Every proposal must include the same ten base fields, regardless of proposal type. Use a ready-made proposal template →

Proposal types

Farm Funding Proposal

Request treasury funding for a new syntropic farm or a material expansion of an existing farm. Requires the strongest documentation: farm overview, crops, revenue model, public-goods allocation, local problem, solution, and MRV plan.

Guild Bounty Proposal

Commission scoped work from contributors through a Guild Steward. Useful for development, MRV, documentation, governance, finance, partnerships, and other operational work.

Framework Upgrade Proposal

Propose changes to the Kokonut Framework, Common Data Schema, MRV methodology, agent architecture, or documentation standards.

Partnership Proposal

Establish a formal relationship with an external organization, funder, farm operator, research partner, tool provider, or ecosystem collaborator.

What makes a proposal strong

A strong Kokonut proposal should be easy to inspect, hard to misunderstand, and possible to measure after execution.
For farm funding proposals, the standard should be especially high. New farm proposals should include location, coordinates, land area, operator wallet, Framework phase, Data Hub link or plan, crop model, revenue streams, target markets, public-goods allocation, and local problem/solution context.

Governance protections

Kokonut governance is designed to reduce the need for personal trust.

Amendments and rejected proposals

Amendments

This Governance Framework can evolve. Any amendment must include the exact proposed change and pass through the full proposal lifecycle. A strong amendment proposal should include:
  • the current text,
  • the proposed replacement text,
  • why the change is needed,
  • who is affected,
  • whether it changes treasury risk,
  • whether it changes rights or responsibilities,
  • and when the amendment becomes active.

Rejected proposals

Rejected proposals may be revised and resubmitted. There is no required cooling-off period, but resubmissions should address the reasons the original proposal failed. A useful resubmission should include a short changelog explaining what changed since the previous version.

Before you submit a proposal

Choose the right proposal type

Farm Funding, Guild Bounty, Framework Upgrade, and Partnership proposals each need different supporting evidence. Start with the relevant template.

Write the ten required fields

Do not skip mission alignment, financial implications, success metrics, or next steps. Those fields are what turn an idea into an accountable proposal.

Share the draft in Kokonut Forum

Open the proposal for the required 5-day drafting window. Treat feedback as part of the proposal process, not as a delay.

Route through the right steward

Guild-originating work should involve the relevant Guild Steward. Treasury-affecting work should be prepared for on-chain voting.

Prepare for execution and reporting

Know who will execute the work, how funds will be used, when updates will be posted, and how success will be measured after approval.

Next steps

Proposal Templates

Copy ready-to-use templates for Farm Funding, Guild Bounty, Framework Upgrade, and Partnership proposals.

Kokonut Moloch DAO

Understand the on-chain system that enforces treasury execution, $vKKN, Loot, rage-quit, and the 66% retention threshold.

Kokonut Guilds

Learn how contributors earn Guild Points, gain standing, and route domain work into the DAO proposal process.

DAO Layers

See how governance, logic, execution, production, and infrastructure layers work together across the full Kokonut DAO architecture.

Kokonut Forum

Draft proposals, collect feedback, and run the required governance review window.

DAOHaus

View the on-chain DAO where treasury-affecting proposals are voted on and executed.