Copy-ready Kokonut DAO proposal templates for farm funding, Guild bounties, Framework upgrades, and partnerships — with guidance on when to use each one and what reviewers need to see.
Write proposals that the DAO can review, vote on, and execute.
Kokonut proposals are not informal requests. They are the bridge between community intent and executable DAO action: treasury disbursements, farm launches, Guild bounties, Framework upgrades, partnerships, token recognition, and operational commitments.Use this page when you already know what you want to propose and need the correct structure. If you are still learning how governance works, start with the Governance Framework.
Every template below follows the ten required fields used across Kokonut governance.
These templates are governance tools, not legal, tax, financial, or investment advice. If a proposal creates legal obligations, external contracts, compliance exposure, or long-term partnership commitments, include appropriate review before asking the DAO to vote.
Select the correct proposal type and copy the template
Before drafting
This page
2. Draft proposal
Fill every required section with concrete details
Day 0
Kokonut Forum / workspace
3. Review window
Members and Guilds comment, challenge assumptions, and request edits
5 days minimum
Kokonut Forum / workspace
4. Sponsor proposal
A proposal-authorized person or Guild Steward advances the proposal
After drafting window
Kokonut Forum → DAOHaus if on-chain
5. Vote
DAO members vote according to the proposal type
5 days minimum
DAOHaus for treasury / on-chain actions
6. Grace period
Members can rage-quit before execution if they disagree
After passed on-chain vote
Moloch DAO flow
7. Execute and report
Proposal team completes milestones and reports success metrics
After execution
Guilds, DAO, Data Hub, docs
Treasury-moving, token-minting, Loot-awarding, membership, DAO-parameter, or on-chain execution proposals should go to DAOHaus. Coordination-only decisions can remain in the forum if they do not require DAO execution.
A formal external relationship, data-sharing agreement, co-funding, or brand relationship
Partnership
KPP-N
Community & Partnerships Guild
Proposal numbers are assigned when the Governance Guild registers the draft. Do not self-assign the final number before your draft is posted and logged.
Before you submit any proposal, make sure it answers the reviewer’s real questions.
Reviewer question
Your proposal must answer
What exactly are we approving?
Name the action, amount, scope, deliverables, responsible people, and timeline.
Why should this happen now?
Explain the problem, opportunity, dependency, or risk that makes the proposal timely.
Who is accountable?
List authors, team members, Guilds, operators, reviewers, and wallet addresses where relevant.
What does the DAO pay for or commit to?
Include treasury amount, token effect, brand use, technical work, data access, or legal commitment.
What proves success?
Define measurable milestones, acceptance criteria, reporting cadence, and evidence sources.
What could go wrong?
Include risks, assumptions, out-of-scope items, revocation conditions, and dispute paths.
What happens after the vote?
Add concrete next steps, owners, deadlines, and reporting obligations.
Vague proposals are expensive for the DAO to review. If your proposal cannot define its budget, success metrics, responsible team, acceptance criteria, and next step, it should stay in drafting.
Use this template for new farm launches, farm expansions, infrastructure upgrades, or major farm phase transitions.Farm funding proposals are highly sensitive because they move treasury capital into real-world operations. They should include land details, operator accountability, budget, disbursement milestones, MRV commitments, SDG alignment, and revenue assumptions.
# [PROPOSAL NAME]# Example: KDP-007 · Adelphi Phase II Expansion — Coconut Long-Cycle Planting---## A. Proposal Name[Short, descriptive name. Convention: KDP-[number] · [Farm Name] — [Action]]## B. Proposal Author(s)- Name / alias:- Wallet address:- Role / relationship to farm:- Contact channel:## C. Proposal TeamList every person responsible for execution, reporting, or review.| Person / wallet | Role | Responsibility || --- | --- | --- || [Name / alias] | Farm Operator | [Execution responsibility] || [Name / alias] | Impact Reviewer | [MRV / SDG responsibility] || [Name / alias] | Technical Contact | [Data Hub / Farm Registry responsibility] |## D. Draft Start Date[YYYY-MM-DD]---## E. Proposal Description### Farm overview| Field | Value || --- | --- || Farm ID | [url-safe slug, e.g. adelphi] || Project start date | [YYYY-MM-DD] || Location | [City, Province, Country] || Coordinates | [lat,lng or UTM] || Total land area | [X m²] || Agricultural area | [X m²] || Governance mechanism | [moloch_dao / guilds / multisig / other] || Operator wallet | [0x...] || Framework phase entering | [phase_i / phase_ii / phase_iii] || Data Hub link | [hub.kokonut.network/projects/N or TBD] |### What is being funded[2–4 paragraphs explaining exactly what the DAO is funding. Be specific about physical deliverables: crops, irrigation, nursery, biofactory, poultry, labor, tools, training, MRV onboarding, certification, or infrastructure.]### Budget and use of funds| Line item | Amount USD | Why it is required | Evidence / quote || --- | ---: | --- | --- || [Item] | $[N] | [Reason] | [Quote / invoice / estimate] || [Item] | $[N] | [Reason] | [Quote / invoice / estimate] || **Total requested** | **$[TOTAL]** | | |### Crop and revenue plan| Revenue stream | Cycle | Unit assumptions | Cycles / year | Forecast annual revenue USD || --- | --- | --- | ---: | ---: || [Crop / product] | [short / medium / long / continuous] | [Density, units, loss rate, price] | [N] | $[N] || [Crop / product] | [short / medium / long / continuous] | [Density, units, loss rate, price] | [N] | $[N] || **Total forecast** | | | | **$[TOTAL]** |Forecast formula: [Include formula and assumptions. Clearly separate forecast from actuals.]### Public goods allocation[X]% of gross revenue will support: [community workshops, free seedling distribution, local education, biodiversity nursery, open data, impact reporting, etc.]### Local problem and solution**Problem:** [Describe the specific local economic, food security, environmental, or social problem this farm addresses.]**Solution:** [Describe how the farm addresses it through crops, employment, biodiversity, education, MRV, and market access.]### MRV and data commitments- Farm Registry record: [existing link or TBD]- Data Hub reporting cadence: [monthly / quarterly / each harvest]- Required records: [harvests, plantings, soil observations, biodiversity records, events, attestations]- Responsible person / Guild: [name / Guild]---## F. Mission Alignment[Explain how this farm advances Kokonut's mission: reducing obstacles to agricultural development, democratizing access to real-world regenerative projects, creating public goods, and building community-owned natural assets.]**Framework components implemented:**- [ ] 5 Principles of Regeneration- [ ] Common Data Schema- [ ] MRV methodology- [ ] SDG alignment- [ ] EBF / impact reporting- [ ] Public goods allocation**SDGs addressed:**- SDG [N]: [How this farm contributes]- SDG [N]: [How this farm contributes]---## G. Brand Usage[Describe how Kokonut Network branding will appear: on-site signage, public reports, social media, farm product labels, partner communications, grant applications, or documentation. If none, write "None at this time."]---## H. Financial Implications### Total funding requested**$[AMOUNT] USD** to be disbursed in stablecoins from the Kokonut DAO Treasury.### Disbursement schedule| Milestone | Amount USD | Condition for release | Evidence required || --- | ---: | --- | --- || Kickoff | $[N] | Proposal passed + operator wallet verified | Wallet confirmation || Infrastructure complete | $[N] | [Deliverable complete] | Photos, receipts, field record || First planting complete | $[N] | MRV event submitted | Farm Registry / Data Hub record || First harvest recorded | $[N] | Harvest record submitted | Harvest report || **Total** | **$[TOTAL]** | | |### Ongoing treasury impact[Describe expected revenue, public goods allocation, timeline to first harvest, and whether any funds return to the DAO or are reinvested locally.]### References- Treasury address: [DAO treasury address]- Farm Registry record: [link once created]- Forecast documents: [link]- Budget evidence: [link]---## I. Success Metrics### During execution- [ ] Milestone 1 completed by [YYYY-MM-DD]- [ ] Infrastructure installed and documented- [ ] MRV records submitted by [cadence]- [ ] Data Hub live within [N] days of kickoff- [ ] Community training sessions completed: [N] sessions, [N] participants### 12-month targets| Metric | Target || --- | --- || Gross revenue | >= $[N] USD || Public goods distributed | >= $[N] USD || Jobs created or sustained | >= [N] positions || Harvest records submitted | >= [N] records || SDG / MRV attestations | >= [N] attestations || Biodiversity or soil indicators | [Target] |---## J. Next Steps| Action | Owner | Deadline || --- | --- | --- || Drafting window open | [Author] | [YYYY-MM-DD] || Incorporate feedback | [Author] | [YYYY-MM-DD] || Impact Guild review | [Reviewer] | [YYYY-MM-DD] || Sponsor to DAOHaus | [Proposal-authorized person] | [YYYY-MM-DD] || Voting window | DAO Members | [YYYY-MM-DD] || If passed: create / update Farm Registry record | [Technical contact] | Within 7 days || If passed: first milestone request | [Farm operator] | Within 14 days || If passed: MRV onboarding | [Impact Guild] | Within 30 days |
Use this template when a Guild Steward requests funding for scoped contributor work.Bounty proposals should be specific, testable, and reviewable. If reviewers cannot tell whether the work is complete, the bounty is not ready.
# [PROPOSAL NAME]# Example: KBP-014 · Technology Guild — MRV Agent Proof of Concept---## A. Proposal Name[Short, descriptive name. Convention: KBP-[number] · [Guild Name] — [Deliverable]]## B. Proposal Author(s)- Name / alias:- Wallet address:- Guild role: [Steward / Member / Contributor]- Contact channel:## C. Proposal Team| Role | Person / wallet | Responsibility || --- | --- | --- || Issuing Guild | [Technology / Impact / Communications / Governance / Finance / C&P] | [Domain owner] || Guild Steward | [Name + wallet] | [Sponsor / reviewer] || Intended contributor | [Name + wallet or TBD] | [Executor] || Reviewer | [Name / Guild] | [Acceptance review] |## D. Draft Start Date[YYYY-MM-DD]---## E. Proposal Description### Bounty summary| Field | Value || --- | --- || Bounty type | [feature / research / content / audit / design / ops / finance / governance] || Skill required | [Solidity, Python, writing, agronomy, design, etc.] || Estimated effort | [e.g. 20 hours over 2 weeks] || Application open | [Yes / No] || Assigned to | [Contributor name + wallet, or TBD] || Work repository / workspace | [GitHub / Drive / Forum / other] |### Background and context[2–3 paragraphs explaining why this work matters now. What ecosystem gap does it solve? Which farm, Guild, tool, page, proposal, or workflow depends on it?]### Deliverable specification| # | Deliverable | Format | Acceptance criteria || --- | --- | --- | --- || 1 | [Primary deliverable] | [Code / doc / report / design] | [Specific, testable criteria] || 2 | [Secondary deliverable] | [Format] | [Specific criteria] || 3 | Documentation / handoff | [MDX / Markdown / Loom / README] | [Merged / published / approved] |### Out of scope[State what this bounty does not include. This prevents scope creep and payment disputes.]### Review process[Who reviews the work? What evidence must be submitted? How many revision rounds are included?]---## F. Mission Alignment[Connect this bounty to a specific Guild responsibility, roadmap item, farm need, MRV need, governance need, or contributor onboarding gap.]---## G. Brand Usage[Explain whether the output will be published under the Kokonut brand, included in official docs, posted publicly, used in grant materials, or kept internal.]---## H. Financial Implications### Total bounty amount**$[AMOUNT] USD** to be paid in stablecoins from the Kokonut DAO Treasury.### Payment schedule| Milestone | Amount USD | Condition for payment || --- | ---: | --- || Kickoff | $[N] | Contributor accepts scope and posts work plan || Midpoint | $[N] | [Midpoint deliverable] accepted || Final delivery | $[N] | All acceptance criteria met || **Total** | **$[TOTAL]** | |### Dispute processIf the contributor and Guild Steward disagree about completion, the Governance Guild is the first escalation point. Unresolved disputes can proceed to a DAO vote.---## I. Success Metrics### During execution- [ ] Contributor submits work plan within [N] days- [ ] Midpoint check-in submitted on schedule- [ ] Final delivery submitted by [YYYY-MM-DD]- [ ] Deliverables pass review within [N] revision rounds### 30-day evaluation| Metric | Target || --- | --- || Primary deliverable utility | [Target] || Adoption / usage | [Target] || Quality / reliability | [Target] || Documentation completeness | [Target] |---## J. Next Steps| Action | Owner | Deadline || --- | --- | --- || Drafting window open | [Author] | [YYYY-MM-DD] || Guild review | [Guild Steward] | [YYYY-MM-DD] || Select contributor if open | [Guild Steward] | [YYYY-MM-DD] || Sponsor to DAOHaus if treasury vote required | [Proposal-authorized person] | [YYYY-MM-DD] || Kickoff payment | [Guild Steward / DAO] | After pass || Work period | [Contributor] | [YYYY-MM-DD] || Final review | [Reviewer] | [YYYY-MM-DD] || Final payment | [Guild Steward / DAO] | On acceptance || Guild Points awarded | [Guild Steward] | Within 7 days |
Use this template when changing the Kokonut Framework, Common Data Schema, MRV methodology, development phases, governance rules, impact reporting, or technical standards.Framework upgrades are highly sensitive because they can affect every farm, every data pipeline, every MRV agent, and every future proposal that depends on the Framework.
# [PROPOSAL NAME]# Example: KFP-003 · Framework Upgrade — Add Drone Imagery CID to MRV Remote Sensing Schema---## A. Proposal Name[Short, descriptive name. Convention: KFP-[number] · Framework Upgrade — [Component]: [Change]]## B. Proposal Author(s)- Name / alias:- Wallet address:- Guild affiliation:- Contact channel:## C. Proposal Team| Person / wallet | Role | Responsibility || --- | --- | --- || [Name] | Schema author | [Design / spec] || [Name] | Technical reviewer | [API / agent review] || [Name] | Impact reviewer | [MRV / SDG review] || [Name] | Documentation owner | [Docs PR] |## D. Draft Start Date[YYYY-MM-DD]---## E. Proposal Description### Change summary| Field | Value || --- | --- || Framework component | [Common Data Schema / MRV Payload / Development Phases / Governance / EBF / Docs] || Change type | [additive / modification / deprecation / removal] || Backward compatible | [Yes / No / Partial] || Farms affected | [List farm IDs or "All registered farms"] || Agents affected | [List agent names or "None"] || API version impact | [None / Minor / Major] |### Current state[Describe what the Framework says today. Quote or link the current rule, field, schema, or process.]~~~// Current field / rule / process[Paste current definition]~~~### Proposed change[Describe exactly what changes. If schema-related, show before and after. If process-related, show old and new language.]~~~// Before[Current version]// After[Proposed version]~~~### Rationale[Explain why the change is needed. Reference a concrete data-quality issue, farm operation, MRV gap, agent integration, governance dispute, or documentation problem.]### Compatibility and migration impactAssess impact on:- Registered farms- Farm Registry API- Data Hub- MRV agents- EAS attestation schemas- Documentation- Partner tools### Migration plan[Required if backward compatible = No or Partial.]| Phase | Action | Owner | Timeline || --- | --- | --- | --- || Deprecation notice | Announce old field / rule as deprecated | [Author] | On proposal pass || Dual-write period | API accepts both formats | Technology Guild | [N weeks] || Farm migration | Farm operators update submissions | Farm operators | By [YYYY-MM-DD] || Agent migration | Agents update capability manifests | Agent operators | By [YYYY-MM-DD] || Cutover | Old format no longer accepted | Technology Guild | [YYYY-MM-DD] |---## F. Mission Alignment[Explain how this change makes Kokonut more modular, measurable, composable, credible, or scalable.]---## G. Brand Usage[Explain how public docs, API references, partner materials, dashboards, or communications must change.]---## H. Financial Implications### Treasury disbursement**$[AMOUNT] USD** — or — **No treasury disbursement required.**If funding is needed:| Work item | Amount USD | Assigned to || --- | ---: | --- || Implementation | $[N] | [Name / Guild] || Testing | $[N] | [Name / Guild] || Documentation | $[N] | [Name / Guild] || Migration support | $[N] | [Name / Guild] || **Total** | **$[TOTAL]** | |### Ongoing cost / savings[Describe ongoing effect: reduced manual work, higher data quality, new maintenance burden, partner dependency, or infrastructure cost.]---## I. Success Metrics### During implementation- [ ] Spec approved and merged- [ ] API / tool update deployed to staging if needed- [ ] At least one test record validates against the new rule / schema- [ ] Documentation updated- [ ] No open critical bugs after [N] days### 30-day evaluation| Metric | Target || --- | --- || Affected farms migrated | [Target] || Affected agents updated | [Target] || Error rate / validation failures | <= baseline || Data quality improvement | [Specific target] |---## J. Next Steps| Action | Owner | Deadline || --- | --- | --- || Draft posted | [Author] | [YYYY-MM-DD] || Technical review | [Technology Guild] | [YYYY-MM-DD] || Impact / governance review | [Relevant Guild] | [YYYY-MM-DD] || Affected operators notified | [Author / Comms Guild] | [YYYY-MM-DD] || Sponsor to vote | [Proposal-authorized person] | [YYYY-MM-DD] || If passed: implementation begins | [Owner] | Within 7 days || If passed: docs PR merged | [Owner] | Within 7 days || If migration: cutover completed | [Owner] | [YYYY-MM-DD] |
Use this template when Kokonut creates a formal external relationship with a protocol, funder, research institution, local cooperative, farm operator network, public goods program, or ecosystem partner.A partnership proposal is required when Kokonut uses another organization’s brand, makes commitments on behalf of the DAO, shares data, grants privileged access, receives or provides funds, or creates a relationship lasting more than 90 days.
# [PROPOSAL NAME]# Example: KPP-005 · Partnership — Public Nouns x Kokonut Network: Adelphi Phase III Co-Funding---## A. Proposal Name[Short, descriptive name. Convention: KPP-[number] · Partnership — [Partner] x Kokonut: [Purpose]]## B. Proposal Author(s)- Name / alias:- Wallet address:- Relationship to partner:- Contact channel:## C. Proposal Team| Role | Person / wallet | Responsibility || --- | --- | --- || Lead negotiator | [Name] | [Relationship owner] || C&P Guild Steward | [Name] | [Guild sign-off] || Legal reviewer if applicable | [Name or None] | [Legal / MOU review] || Technical contact if applicable | [Name or None] | [Integration review] |## D. Draft Start Date[YYYY-MM-DD]---## E. Proposal Description### Partner overview| Field | Value || --- | --- || Partner name | [Full name] || Partner type | [protocol / institution / farm / funder / cooperative / DAO] || Website | [URL] || Wallet / ENS | [0x... or name.eth, if applicable] || Chain(s) | [If relevant] || Partnership duration | [12 months / single event / indefinite / other] || Renewal mechanism | [Annual vote / automatic unless terminated / new proposal required] |### What this partnership is[2–4 paragraphs explaining who the partner is, how the relationship started, what opportunity it creates, what each side will do, and what the working relationship looks like.]### Value exchange**What Kokonut provides:**| Contribution | Description || --- | --- || [Contribution] | [Description] || [Contribution] | [Description] |**What Kokonut receives:**| Contribution | Description || --- | --- || [Contribution] | [Description] || [Contribution] | [Description] |### Integration requirements[If technical: describe API, smart contract, data, dashboard, agent, or attestation requirements. If none, write "No technical integration required."]### Revocation conditionsThis partnership can be terminated if:- [ ] Partner fails to deliver agreed contributions- [ ] Partner misuses Kokonut brand or represents itself inaccurately- [ ] Partner acts against Kokonut's manifesto or community-first values- [ ] Technical or data-sharing risk becomes unacceptable- [ ] DAO passes a termination proposalEither party may initiate termination by posting notice to the designated governance venue. Termination takes effect after [14 / 30] days unless the DAO votes otherwise.---## F. Mission Alignment[Explain how the partnership advances Kokonut's mission, supports farms, strengthens public goods, improves infrastructure, expands capital access, or increases credible impact reporting.]Specifically address:- Shared values- Expected benefits to farms and contributors- Precedent for future partnerships- Reputational risks---## G. Brand Usage### Kokonut use of partner brand[Where and how Kokonut may use partner name, logo, data, or public references.]### Partner use of Kokonut brand[Where and how partner may use Kokonut name, logo, data, or public references. State limits clearly.]---## H. Financial Implications### Treasury disbursement**$[AMOUNT] USD** — or — **No treasury disbursement required.**If funds move:| Line item | Amount USD | Condition for release || --- | ---: | --- || [Line item] | $[N] | [Condition] || [Line item] | $[N] | [Condition] || **Total** | **$[TOTAL]** | |### Expected value to Kokonut[Describe grant funding, revenue share, cost reduction, in-kind services, technical integrations, research outputs, community reach, or other measurable value.]### Jurisdiction / legal note[If any legal entity is involved, name jurisdiction and whether a contract, MOU, grant agreement, or data-sharing agreement will accompany the DAO vote.]---## I. Success Metrics### During the partnership- [ ] Value exchange items delivered on schedule- [ ] No unresolved brand usage disputes- [ ] Technical integration live by [date], if applicable- [ ] Quarterly check-ins completed- [ ] Public update posted by [cadence]### End-of-term evaluation| Metric | Target || --- | --- || Kokonut commitments delivered | 100% || Partner commitments delivered | 100% || Partnership-specific outcome | [Target] || Community sentiment / objections | [Target] || Renewal recommendation | Published before term end |---## J. Next Steps| Action | Owner | Deadline || --- | --- | --- || Draft posted | [Author] | [YYYY-MM-DD] || Partner reviews draft | [Lead negotiator] | [YYYY-MM-DD] || C&P Guild review | [Guild Steward] | [YYYY-MM-DD] || Legal / technical review if needed | [Reviewer] | [YYYY-MM-DD] || Feedback incorporated | [Author] | [YYYY-MM-DD] || Sponsor to vote | [Proposal-authorized person] | [YYYY-MM-DD] || If passed: agreement signed if applicable | [Owner] | Within 14 days || If passed: public announcement | [Communications Guild] | Within 7 days || First check-in scheduled | [Lead negotiator] | Within 30 days |
A passed proposal is not the end of governance. It creates responsibility.
Proposal type
First post-pass action
Ongoing reporting
Farm Funding
Create or update Farm Registry / Data Hub records
Milestone reports, MRV events, harvest, and impact data
Guild Bounty
Confirm contributor, payment wallet, and work plan
Deliverable reviews, Guild Points, final handoff
Framework Upgrade
Open implementation and documentation PRs
Migration status, validation checks, operator support
Partnership
Confirm written acknowledgment or agreement
Quarterly check-ins, value exchange updates, and renewal review
If a passed proposal cannot be executed as written, post an update immediately. Material changes to the budget, scope, timeline, or obligations may require an amended proposal.
