Skip to main content
The Governance Framework is the operating manual for collective decision-making in the Kokonut Network. It defines who can propose, who can vote, where decisions happen, how long they take, and what a valid proposal must contain. Every farm funding decision, Guild bounty, framework upgrade, and ecosystem partnership passes through this framework — on-chain and off-chain — before any treasury funds move. This document is a baseline established by the Core Team to launch the ecosystem in a community-oriented direction while optimizing for efficiency and outcomes. It is deliberately designed to evolve: amendments are made through the same proposal process it describes.
Disclaimer: This is a foundational framework of governance mechanics, not a comprehensive legal document. It serves as the baseline for developing the Kokonut Framework and growing the ecosystem in a community-oriented way. It is subject to amendment via DAO proposal.

Quick reference — key parameters

ParameterDesignationNotes
Drafting platformCharmverseWhere proposals are written, versioned, and discussed
Voting platform (off-chain)Charmverse1 person = 1 vote
Voting platform (on-chain)DAOHaus1 $vKKN = 1 vote
Minimum drafting duration5 daysAll vote-authorized members notified at start
Voting duration5 daysAfter drafting window closes
Minimum total timeline10 daysBefore any proposal can execute
Default voting optionsFor / AgainstUnless the proposal requires others
On-chain quorum (onboarding)0%Any participation = valid outcome. Permissionless entry by design.
On-chain quorum (other types)Varies by proposal typeUpgradable via DAO proposal
Token retention threshold66%If rage-quits during grace period reduce supply below 66%, the proposal does not execute
Proposal-authorized personsTeam Members + Guild StewardsGuild Stewards co-sign proposals flowing from the Guild layer
Vote-authorized personsDAO MembersAll $vKKN token holders

I. Definitions and Designations

A. Proposal-Authorized Person
  1. Definition: People recognized for making and sponsoring proposals to the active voting stage.
  2. Designation: Team Members — and, in practice, Guild Stewards co-signing proposals that originate in the Guild operational layer and require treasury disbursement. B. Vote-Authorized Person
  3. Definition: A person recognized to vote on proposals.
  4. Designation: DAO Members — all holders of at least one $vKKN token on Gnosis Chain. C. Designated Drafting Platform
  5. Definition: The platform where proposals are drafted, edited, versioned, and opened for community feedback before moving to a vote.
  6. Designation: Charmverse — the Kokonut community coordination hub where proposal drafts live, feedback threads run, and all vote-authorized people are notified when a new draft is posted. D. Minimum Drafting Duration
  7. Definition: The minimum time a proposal must be available for feedback before it can advance to the Active Stage.
  8. Designation: 5 days. No proposal can be sponsored to the active voting stage before its 5-day drafting window has elapsed. This protects vote-authorized people from being surprised by proposals they haven’t had time to review. E. Designated Voting Platform
  9. Definition: The platform where proposals are voted on.
  10. Designation:
    • Off-chain: 1 person = 1 vote (used for lighter-weight coordination decisions)
    • On-chain: DAOHaus — 1 $vKKN = 1 vote (used for all treasury-affecting proposals) F. Designated Voting Duration
  11. Definition: The duration for which an active proposal may be voted on.
  12. Designation: 5 days. Combined with the minimum drafting duration, no proposal that affects the treasury can be passed in fewer than 10 days from when it is first posted. G. Designated Voting Method
  13. Definition: The method for calculating or weighting votes.
  14. Designation:
    • Off-chain (Charmverse): 1 person = 1 vote
    • On-chain (DAOHaus): 1 $vKKN = 1 vote H. Designated Voting Quorum
  15. Definition: The minimum number of votes needed for the outcome to be considered legitimate.
  16. Designation:
    • Off-chain: Varies by proposal type
    • On-chain: 0% for the Onboarding Stage — any level of participation produces a valid result. This is intentional: permissionless entry requires that new member proposals can pass even with low participation, ensuring no coordinated blocking of new members.
    • All other on-chain proposal types: quorum is configurable and upgradable via DAO proposal. See the Moloch DAO page for current parameters. I. Designated Voting Retention
  17. Definition: The percentage of tokens required to remain in the DAO after the grace period for a proposal to execute. If the total supply falls below this threshold through rage-quits, the proposal is not executed.
  18. Designation: 66%. This is the protection against governance attacks: a majority cannot pass a large treasury disbursement and then simply allow minority holders to rage-quit — if enough members exit during the grace period to reduce supply below 66%, the proposal fails.
    • Token-based voting retention applies to on-chain proposals only.
    • See rage-quit mechanics for a full explanation of how the grace period and retention threshold interact. J. Default Voting Options
  19. Definition: The standard voting options are used unless a specific proposal requires alternatives.
  20. Designation: “For” and “Against”.

II. Proposal Process

A. Preamble
With this agreed-upon proposal process, any proposal-authorized person may draft and post a proposal for all vote-authorized people to vote on, in order to formally facilitate group decisions. This process may evolve over time and may eventually be further formalized through the establishment of bylaws or other operating agreements.
B. The three stages Every Kokonut DAO proposal passes through three mandatory stages in sequence. No stage can be skipped.

Drafting Stage

The proposal is written and posted to Charmverse using the Proposal Template structure. All vote-authorized people are notified when the draft is posted. The proposal must remain in the Drafting Stage for a minimum of 5 days before it can advance. During this window, proposal-authorized and vote-authorized people can give feedback, request changes, and raise concerns. This is the primary mechanism for surfacing dissent before a binding vote.A proposal advances to the Active Stage only when:
  • The 5-day minimum has elapsed
  • A proposal-authorized person sponsors it to the active voting stage

Active Stage

The proposal is posted to the designated voting platform (DAOHaus for on-chain proposals, Charmverse for off-chain), and voting opens. For a proposal to pass, it must:
  • Remain active for the designated 5-day voting duration
  • Use the designated voting method (1 $vKKN = 1 vote on-chain)
  • Meet the designated voting quorum for its proposal type
  • Receive a majority of votes in favor (“For”)
After the vote closes, a grace period opens before execution. Any DAO member who disagrees with the outcome can rage-quit with their proportional treasury share during this window.

Execution Stage

Once the active voting period closes with a passing vote and the grace period elapses without the token retention threshold being breached, the proposal executes automatically via smart contract. Action items specified in the proposal may commence immediately under the authorization of the organization. No further approval is required — the on-chain execution is final.If the grace period rage-quits reduce the total $vKKN supply below 66%, the proposal does not execute and must be resubmitted.
Minimum end-to-end timeline:
Day 0:    Proposal posted to Charmverse (Drafting Stage opens)
Day 1-5:  Community feedback window (minimum 5 days)
Day 5:    Proposal-authorized person sponsors to DAOHaus
Day 5-10: Active voting window (5 days)
Day 10:   Vote closes → Grace period opens
Day 10+:  Grace period → Execution (if retention threshold met)

III. Proposal Template

Every proposal — regardless of type — must include all ten fields below. This is the canonical base specification. For type-specific implementations with pre-filled guidance, see the Proposal Templates page, which provides ready-to-use templates for Farm Funding (KDP), Guild Bounty (KBP), Framework Upgrade (KFP), and Partnership (KPP) proposals. A. Proposal Name: The proposal’s name. May follow a codified naming scheme (e.g. KDP-007 for farm funding proposals) or be freeform. Proposal numbers in each series are assigned sequentially by the Governance Guild when a draft is registered on Charmverse. B. Proposal Author(s) The person or people authoring the proposal — name, alias, and wallet address. C. Proposal Team: The people who will conduct the affairs detailed in the proposal if it passes. Distinct from the author(s) — a proposal may be authored by one person but executed by a team. D. Draft Start Date: The date the proposal draft was first posted to Charmverse. This is the start of the 5-day minimum drafting window. E. Proposal Description The main body of descriptive text explaining what the proposal is about — what action it requests, what it will produce, and why it is being submitted now. F. Mission Alignment: An explanation of why this proposal is in alignment with the mission and goals of the Kokonut Network. Proposals that cannot demonstrate mission alignment should not advance to a vote. G. Brand Usage: A description of whether and how the proposal involves usage of the Kokonut Network brand — name, logo, or associated marks. If no brand usage is involved, state that explicitly. H. Financial Implications: A description of any disbursements, costs, or budget impacts associated with the proposal. Any proposal that affects the treasury must reference the Main Treasury and specify exact amounts, conditions for disbursement, and the timeline for fund release. I. Success Metrics: A description of how the success of this proposal can be gauged — both during the Execution Stage and after it concludes. Metrics should be specific and verifiable where possible. Proposals without measurable success criteria are harder for the community to evaluate and hold accountable. J. Next Steps: An outline of the action items that follow from the proposal passing, including who is responsible for each. Proposals without a clear next steps section create ambiguity about who executes what after the vote.

IV. Miscellaneous

A. Amendments Amendments to this Governance Framework can be made by including an edited version of this document in a DAO proposal, to be ratified by vote-authorized people. Any amendment must pass through the full three-stage proposal process. B. Revised Proposals. If a proposal is rejected, it may be redrafted and resubmitted for another vote. There is no cooling-off period required between rejection and resubmission — but resubmissions should incorporate the feedback that led to rejection, or they are unlikely to pass.

Proposal Templates

Ready-to-use templates for the four Kokonut proposal types — Farm Funding (KDP), Guild Bounty (KBP), Framework Upgrade (KFP), and Partnership (KPP) — each built on the ten fields above.

Kokonut Moloch DAO

The on-chain system that enforces what this framework describes — contract addresses, tribute process, rage-quit mechanics, and the 66% retention threshold explained.

Kokonut Guilds DAO

How Guild Stewards co-author proposals, how Guild bounties flow through this framework, and how contributions earn the right to co-sign treasury proposals.

Charmverse Workspace

The designated drafting platform — where proposals are written, feedback is collected, and the 5-day window runs before any proposal can advance to a vote.