​

Interoperability for real-world regenerative projects.

Kokonut Protocol is Kokonut Network’s approved architectural direction for a chain-agnostic Web3 policy and execution layer with NEAR as its interoperability hub. Instead of moving every system onto a single blockchain, it aims to coordinate approved actions across the chains where Kokonut’s communities, treasuries, identity systems, attestations, and markets already operate.

​

Four systems, four responsibilities

Intelligence owns truth. Protocol owns execution policy. NEAR coordinates signing. Destination chains enforce their own settlement and rights.

​

The cross-chain execution contract

NEAR Chain Signatures can help a governed NEAR account obtain a signature for a destination-chain payload. Signing does not itself build the transaction, fund destination gas, broadcast, guarantee finality, or prove a real-world outcome. A safe Protocol workflow is:

1. Prepare a structured, chain-specific request and simulate the exact intended effect.
2. Validate project scope, policy, budget, destination, expiry, and human or DAO approvals.
3. Bind the approval to the exact action hash.
4. Request an authorized Chain Signature on NEAR.
5. Assemble and broadcast through the destination adapter.
6. Wait for applicable finality, verify the intended effect, and reconcile the result into Kokonut Intelligence.
7. Route failed, stalled, or ambiguous actions to independent manual review.

The Syntropic Agent can propose, analyze, and monitor these operations; it does not approve its own protected financial actions.

​

How the existing chains fit

NEAR Intents and Chain Signatures solve different problems. Chain Signatures provide governed signing capability for destination transactions. Intents can provide an optional asset exchange or settlement pathway. Neither changes the canonical farm record or overrides local governance.

​

Revenue Containers and economic boundaries

Revenue Containers are proposed project-specific accounting and treasury arrangements. They should isolate each project’s liabilities, receipts, distribution policy, and any explicitly agreed economic rights. A new project token, agent token, or Revenue Container does not automatically give a holder rights to the existing Kokonut DAO treasury, Moloch Shares/Loot, Ragequit mechanism, farmland, or another project’s cash flows.

​

Build with the Protocol

Development focuses on NEAR policy/controller contracts, typed chain adapters, execution-state tracking, destination reconciliation, and security tests. NEAR Intents settlement, experimental Revenue Containers, and additional chain families can follow as independent workstreams.