Most conservation groups run on a treadmill: write the grant, spend the grant, write the next grant. The people who should be restoring creeks and running fire crews spend half their time fundraising, and the money arrives in cycles that never match the work. The mission is permanent; the funding is temporary.
You can fund a conservation group by giving it an onchain namespace, letting members create agents and instruments under it, and routing the proceeds — trading fees, royalties, and distributions — back to the group and its members. It turns one-time donations into recurring, shared income that grows with the work.
This is the group-scale companion to how to make money with ensurance. If you organize people around a place — a watershed council, a land trust, a tribe, a community, a DAO — this is how the organizing itself becomes fundable.
the treadmill, and the way off it
Grants and appeals are one-time by design. They fund a project, not a permanent capacity, so the group is always one cycle from a gap. Worse, none of the value the group creates — a restored floodplain, a protected forest, a healthier river — flows back to fund the next thing. The work produces value; the value leaves.
A group on the protocol works the other way: the value the community protects becomes instruments that trade, and the activity around those instruments routes proceeds back to the group. Instead of raising money against the mission every year, the group builds an asset base that funds the mission continuously.
what a "group" is here
A group is a namespace — your community's onchain identity, like .yourwatershed or .yourtrust. Under it, members create agents: onchain accounts that each represent a place, a person or organization, or a purpose within your mandate. A watershed group might hold agents for its headwaters, its riparian corridors, the beaver it's reintroducing, and the ranchers doing the work.
Each agent has its own wallet and holds the instruments tied to it — certificates for specific places and purposes, coins for the broader cause. The group is the umbrella; the agents are the members; the proceeds flow between them through routing you control. See what is an ensurance group and the group playbook for the mechanics of forming one.
the income lines a group earns
Once your namespace is live and agents are minting under it, several streams pool into the group and its agents' accounts:
| income line | where it comes from | how it works |
|---|---|---|
| secondary royalties | agents minted under your namespace trading on secondary markets | you set the royalty rate; it defaults to a protocol split and you can redirect it to your group's own account — a standing cut of your community's market activity |
| instrument proceeds | coins and certificates tied to your agents | trading fees and mint proceeds pool in the relevant agent accounts, not off to a stranger |
| distribution incentive | routing proceeds to members | small permissionless reward for the party that triggers a distribution |
| the group's own holdings | certificates and coins the group treasury holds | the group is a member too — it earns distributions like any holder |
The royalty line is the one most groups miss: when you own the namespace, the resale royalty on everything minted under it is a lever you control. As your community's agents grow in number and value, that becomes a real, recurring income stream tied directly to the health of what you protect.
sharing the proceeds
Earning is half of it; the point is to route the value where it does the most good. The protocol's proceeds system lets a group split every inflow across destinations — automatically, transparently, onchain.
A group can route, say, a share to the fieldwork, a share to a treasury that funds next year's projects, and a share distributed to the members who hold its certificates. Because ensurance is a member-owned protocol, those certificate holders are members: distributions reach them pro-rata, wherever they hold their certs. A group can reward the people who showed up early, fund the crews doing the work, and build a reserve — from one stream of activity, split however the community decides.
That's the shift. A conservation group stops being a pass-through for other people's grant money and becomes a small, self-funding economy around a place — one where protecting the land and funding the group are the same act.
how to start
- Claim a namespace. Register your group's identity on the protocol — see how to create an ensurance group.
- Mint the first agents. Represent the places, people, and purposes at the center of your mandate. Start with one or two that matter most.
- Attach instruments. Give those agents certificates and, where it fits, coins — so capital has somewhere to land.
- Configure the routing. Decide how proceeds split between the work, the treasury, and the members. Set the namespace royalty to your own account.
- Grow the commons. As more members mint under your namespace and more capital flows in, the income lines compound — and so does the protection.
frequently asked questions
do we have to be a crypto group to do this?
No. Watershed councils, land trusts, tribes, and community groups are exactly who this is built for. The onchain namespace is infrastructure — like a bank account and a registry combined — that runs underneath your existing organizing. You bring the community and the mission; the protocol handles the plumbing.
how is this different from a normal nonprofit or fiscal sponsor?
A fiscal sponsor passes grant money through and takes a cut. A group here owns the instruments tied to the value it protects, so it earns from ongoing activity — royalties, proceeds, distributions — not just from the next appeal. It's an asset base, not a pass-through.
who controls the money?
You do. Proceeds routing is configured by the group and executes transparently onchain. You decide the splits between fieldwork, treasury, and members, and you can see every flow.
what if we're small or just starting?
Start with one agent for the place you care most about and one instrument. The model works at any size and compounds as you grow — from seedlings to syndicates.
next steps
- form a group — claim your namespace and mint your first agent → ensurance groups.
- map your proceeds — decide how value should flow between the work, the treasury, and your members → proceeds.
- talk it through — if you run a watershed council, land trust, tribe, or community and want help structuring it, start a conversation.
- tell your board — forward this to the people who spend their year chasing grants. A self-funding model is worth a meeting.