How KulaDAO is making impact-fund governance enforceable, not performative.

A governance layer that executes the vote.

Most DAOs end where Kula begins. A vote passes, a discord channel celebrates, and a treasury manager moves money around in a spreadsheet. The decision is onchain. The execution is not.

KulaDAO is a multi-tier impact fund. Token holders vote on which projects get funded. A governance tier distributes capital to regional organizations on the ground. The premise is that the entire path — proposal, vote, treasury movement, distribution to a RegionalDAO — should run on the same network, with the same audit trail, under the same enforceable rules.

"We are building a new standard for how governance should operate. One that begins with value alignment, embeds enforceability into its architecture and moves beyond the performative decentralisation that has defined much of Web3 to date."

— KulaDAO

Why a dedicated network

A public chain is the wrong substrate for an impact fund. Regional grantees need a network that knows who they are. Token holders need to know that only approved participants can vote. The governance council needs to know that no one outside that council can deploy a contract to the network.

KulaDAO's network on AvaCloud is permissioned by design:

• Allow-listed transactions. Only approved token holders and regional organizations can submit transactions. Access is controlled at the network layer, not bolted on by the app.
• Allow-listed deployers. Only the governance council can deploy contracts. No anonymous deployer can push code into the trust path.
• Multisig at the root. Network-level changes require Gnosis Safe approvals from the council. No single key, no single point of failure.
• Valueless native token. Gas is a DoS-prevention mechanism, not a speculative asset. The thing that has value — the Kula token — is bridged in via ICTT for distribution.

What the network executes

After four years stress-testing the model, the protocol was designed to support the full KulaDAO lifecycle on a single network:

1. Proposals. Token holders submit funding proposals through the governance contracts.
2. Votes. Only allow-listed token holders can vote. Quorum, thresholds, and timing are encoded, not negotiated.
3. Treasury tracking. Every Kula-token balance and movement is visible to participants on the network.
4. Capital allocation. Once a vote passes, the Kula token is sent — via ICTT — to the RegionalDAO that won the proposal. The vote and the distribution share a transaction trail.

What this unlocks

For impact funds, the bottleneck has always been the gap between decision and execution. KulaDAO closes it. A vote no longer authorizes a manager to move capital — it moves the capital. Regional organizations receive funds against an audit trail their funders can inspect in real time. Institutional partners get the compliance posture they need without losing the community-governance principles Kula was built on.

"Avalanche gives us the reliability and flexibility we need to ensure that governance decisions are not only made well, but executed properly, with transparency and accountability across every layer of our system."

— KulaDAO

Roadmap

• September 2025 — Testnet. Smart-contract deployment, Web3 Data API, ICTT enablement, load testing with beta token holders, end-to-end governance proposal testing.
• November 2025 — Mainnet. Full production launch with real token holders, real proposals, and real capital flowing through to RegionalDAOs.