nature & climate finance onchain
Subscribe to BASIN Dispatches
Subscribe to BASIN Dispatches
nature & climate finance onchain
>300 subscribers
>300 subscribers
Support BASIN Dispatches
BASIN Dispatchesthe funding model that works like a watershed
Water fills a pool. The pool overflows into the next. Then the next. Each one sustains life while feeding everything downstream. No pump. No committee. Just gravity, connection, and abundance.
This is how a watershed works. It's also how conservation funding should work — but never has.
A wetland restoration in one region and a riparian buffer in the next apply for separate grants, report to separate agencies, and rise or fall on separate timelines. The ecology connecting them is continuous. The funding is not.
We built infrastructure to close that gap. Not a platform. Not a marketplace. Plumbing — open, free, and designed for people doing the actual work on the land.
---
You don't need anyone to explain systems thinking. You live it.
The beaver dam slows the creek. The creek raises the water table. The water table sustains the meadow. The meadow feeds the elk. The elk attract the visitors. The visitors fund the easement. You've drawn this chain a hundred times on a whiteboard for a funder who needed to see it as a budget line.
The ecology is elegant. The frustrating part is that every funding model you've been handed treats each node in that chain as a standalone project — disconnected, competitive, temporary.
What if the funding moved the way the water does?
---
An agent is an onchain account that represents a place, a group of people, or a purpose. It has a human-readable name and its own wallet that can hold and route funds.
"elk-creek.basin"
"floodplain-reconnection.syndicate"
"pollination.ensurance"
"marble-wetlands-preserve.avlt"
Support BASIN Dispatches
BASIN Dispatchesthe funding model that works like a watershed
Water fills a pool. The pool overflows into the next. Then the next. Each one sustains life while feeding everything downstream. No pump. No committee. Just gravity, connection, and abundance.
This is how a watershed works. It's also how conservation funding should work — but never has.
A wetland restoration in one region and a riparian buffer in the next apply for separate grants, report to separate agencies, and rise or fall on separate timelines. The ecology connecting them is continuous. The funding is not.
We built infrastructure to close that gap. Not a platform. Not a marketplace. Plumbing — open, free, and designed for people doing the actual work on the land.
---
You don't need anyone to explain systems thinking. You live it.
The beaver dam slows the creek. The creek raises the water table. The water table sustains the meadow. The meadow feeds the elk. The elk attract the visitors. The visitors fund the easement. You've drawn this chain a hundred times on a whiteboard for a funder who needed to see it as a budget line.
The ecology is elegant. The frustrating part is that every funding model you've been handed treats each node in that chain as a standalone project — disconnected, competitive, temporary.
What if the funding moved the way the water does?
---
An agent is an onchain account that represents a place, a group of people, or a purpose. It has a human-readable name and its own wallet that can hold and route funds.
"elk-creek.basin"
"floodplain-reconnection.syndicate"
"pollination.ensurance"
"marble-wetlands-preserve.avlt"
Not a profile on someone else's system. Your account. Your name. Permanent, searchable, and legible to every funder, partner, and auditor who needs to see where value flows.
A land trust creates agents for its priority landscapes. A watershed council creates one for the basin. A beaver reintroduction crew creates one for the program. A city creates agents for segments of its pollinator corridor.
Each agent is a pool.
Now we connect them.
---
Coins are currencies anyone in the world can trade. A coin named for your watershed, your ecosystem, your cause. When people buy or sell, trading generates proceeds that flow to the agent's wallet automatically. Continuously. No applications. No reporting cycles.
Indirect funding. The mechanism runs itself.
Certificates are direct. Tied to a specific piece of land, a specific natural asset, a specific outcome. When someone acquires a certificate on your 40-acre floodplain restoration, the funds go straight to the agent stewarding that land — a claim on the ecosystem services that restoration produces, backed by real acres.
Both instruments feed the pools.
---
Proceeds are programmable flows that split and route value between agents. When a coin generates trading fees, those fees don't land in one wallet. They split — 40% to the wetland agent, 30% to the riparian agent upstream, 20% to the beaver program in the headwaters, 10% to a "water-cycle.syndicate" that coordinates across them all.
And those agents, receiving funds, route proceeds of their own — to the agents they depend on, to the landscapes they protect, to the people doing the work.
The wetland funds the riparian buffer. The riparian buffer funds the beaver program. The beaver program raises the water table that sustains the wetland.
The pools overflow into each other.
This isn't a whiteboard sketch. It's live, running 24/7. You can watch the flows right now.
---
A regional collaborative manages restoration across a 50-mile river corridor. Four active projects: wetland reconstruction at the river mouth, riparian fencing and planting along the middle reach, beaver dam analogues in the upper tributaries, prescribed fire on the adjacent ridgeline.
With ensurance infrastructure:
Each project gets an agent — "silver-creek.basin", "lower-valley-wetlands.natural-asset", and so on. The collaborative gets one. A "silver-creek-headwaters.syndicate" coordinates across all four.
A coin exists for this watershed. People who recognize its ecosystem service value — or who simply care — trade it. Every trade generates proceeds that flow through the syndicate to the four project agents.
Each project issues certificates on its specific interventions. A water utility downstream — which depends on the clean water these projects produce — acquires certificates on the riparian and wetland sites because source protection is cheaper than treatment. A municipality that benefits from reduced flood risk acquires certificates on the floodplain.
The fire program improves soil and water retention for the riparian zone. The riparian zone provides shade and filtration for the wetland. The wetland provides base flow and biodiversity for the whole system. The proceeds routing mirrors this ecology — each agent sending a share of what it receives to the agents it depends on.
The collaborative stops being an applicant. It becomes a node in a value network.
---
The deepest expression of this model isn't a single project funding itself. It's connected landscapes funding each other across boundaries.
Wildlife corridors. Pollinator pathways. Migration routes. The spaces between protected areas that determine whether those areas actually work.
A wildlife corridor is the hardest thing to fund in conservation. It crosses ownerships, jurisdictions, land types, and management regimes. No single grant, no single easement, no single agency can hold it together. But without it, the refugia on either end become islands — and islands go extinct.
Ensurance infrastructure was built for exactly this.
Each corridor segment becomes an agent. "i-70-wildlife-crossing.natural-asset". "monarch-flyway-segment-12.earth". Each issues its own certificates. A "wildlife-corridor.syndicate" coordinates across segments, routes proceeds from corridor-scale instruments to the individual crossings and habitat patches that need them.
The elk winter range agent funds the migration corridor agent. The corridor agent funds the highway crossing agent. The crossing agent connects two refugia that, together, sustain a population that neither could sustain alone.
Connected refugia, connected funding. The model works because the funding architecture mirrors the ecology: distributed, relational, polycentric. Not one fund deciding where capital goes — many agents, each hyper-local, coordinating through shared infrastructure the way organisms coordinate through ecosystems.
---
This distinction matters.
Every conservation "solution" you've been pitched was a product owned by someone. When that someone changed priorities, pivoted, or shut down, your data and your funding stream went with them.
Ensurance is infrastructure. Open for anyone. You create an agent the way you register a domain name. You route proceeds the way you set up a bank transfer. The protocol is public.
what it is → what it isn't
plumbing you own → a platform you rent
your agent, your name, your wallet → a profile on someone else's system
composable — connects to anything → a walled garden
perpetual by design → dependent on any company's survival
open to anyone doing the work → gatekept by application or partnership
Your agent is onchain. It holds funds and routes value regardless of what happens to any organization — including ours.
---
"Composable" sounds technical. The concept isn't. Everything connects.
Your wetland agent can join a "pollinator-habitat.syndicate". That syndicate can include an urban greening project 200 miles away — because monarchs don't observe county lines. A beaver agent in Montana can join a "water-cycle.syndicate" alongside a headwater forest program in Colorado. A biocrust restoration in Utah can connect to a grassland syndicate that spans continents.
Species, water, nutrients, and energy cross every boundary we draw. This infrastructure lets funding do the same.
Each agent is modular. Each connection is voluntary. You decide who you coordinate with, how proceeds route, and what instruments you issue. The infrastructure makes it possible. You make it real.
---
Every agent has a permanent, human-readable name.
"roaring-fork-river.basin"
"marble-wetlands-preserve.avlt"
"wildlife-corridor.syndicate"
"pollination.ensurance"
Not a database ID. Not a grant number. A name — searchable, traceable, legible.
When you tell a water utility "your investment flows to "elk-creek.basin"," they can verify it. They can see what the agent holds, what it's received, where it's sent value. Transparency isn't a report you file once a year. It's the default.
And when you connect AI to a named account, something shifts. The agent can receive ecological data, respond to inquiries, communicate about its place, and coordinate with other agents across the network. A watershed agent that monitors conditions, talks to funders, and helps steward the landscape it represents.
The named agent is the seed. Everything else grows from it.
---
If you restore wetlands, streams, forests, or grasslands — each site can be an agent with its own wallet and instruments.
If you manage conservation lands — your portfolio can route proceeds between properties based on need.
If you coordinate across boundaries — syndicates pool resources and distribute them across your landscape.
If you build pollinator corridors, wildlife corridors, or urban nature networks — each segment becomes an agent, the corridor becomes a syndicate, the network funds itself.
If you run beaver reintroduction, prescribed fire, biocrust restoration, induced meandering, or any nature-based intervention — it maps.
If you steward indigenous lands — you can create agents under your own namespace, with full sovereignty over naming, governance, and how proceeds flow.
The infrastructure doesn't care about your tax status, your country, or your org chart. It cares about place, purpose, and the quality of connection between them.
---
Creating an agent costs less than a penny in gas. The infrastructure is open. There are no platform fees. A small percentage of proceeds flows through the protocol to sustain the shared infrastructure — the same way a watershed sustains the river it feeds.
---
We're not here to tell you what to protect or how. You understand your landscape, your stakeholders, your constraints better than any protocol ever will.
What we built is connective tissue. Plumbing that lets your projects support each other financially the way they already support each other ecologically. A way for the beaver program to fund the riparian buffer. A way for the floodplain to fund the headwaters. A way for the wildlife crossing to connect two refugia — ecologically and financially.
The pools are carved. The plumbing is laid.
Your work is the water.
Not a profile on someone else's system. Your account. Your name. Permanent, searchable, and legible to every funder, partner, and auditor who needs to see where value flows.
A land trust creates agents for its priority landscapes. A watershed council creates one for the basin. A beaver reintroduction crew creates one for the program. A city creates agents for segments of its pollinator corridor.
Each agent is a pool.
Now we connect them.
---
Coins are currencies anyone in the world can trade. A coin named for your watershed, your ecosystem, your cause. When people buy or sell, trading generates proceeds that flow to the agent's wallet automatically. Continuously. No applications. No reporting cycles.
Indirect funding. The mechanism runs itself.
Certificates are direct. Tied to a specific piece of land, a specific natural asset, a specific outcome. When someone acquires a certificate on your 40-acre floodplain restoration, the funds go straight to the agent stewarding that land — a claim on the ecosystem services that restoration produces, backed by real acres.
Both instruments feed the pools.
---
Proceeds are programmable flows that split and route value between agents. When a coin generates trading fees, those fees don't land in one wallet. They split — 40% to the wetland agent, 30% to the riparian agent upstream, 20% to the beaver program in the headwaters, 10% to a "water-cycle.syndicate" that coordinates across them all.
And those agents, receiving funds, route proceeds of their own — to the agents they depend on, to the landscapes they protect, to the people doing the work.
The wetland funds the riparian buffer. The riparian buffer funds the beaver program. The beaver program raises the water table that sustains the wetland.
The pools overflow into each other.
This isn't a whiteboard sketch. It's live, running 24/7. You can watch the flows right now.
---
A regional collaborative manages restoration across a 50-mile river corridor. Four active projects: wetland reconstruction at the river mouth, riparian fencing and planting along the middle reach, beaver dam analogues in the upper tributaries, prescribed fire on the adjacent ridgeline.
With ensurance infrastructure:
Each project gets an agent — "silver-creek.basin", "lower-valley-wetlands.natural-asset", and so on. The collaborative gets one. A "silver-creek-headwaters.syndicate" coordinates across all four.
A coin exists for this watershed. People who recognize its ecosystem service value — or who simply care — trade it. Every trade generates proceeds that flow through the syndicate to the four project agents.
Each project issues certificates on its specific interventions. A water utility downstream — which depends on the clean water these projects produce — acquires certificates on the riparian and wetland sites because source protection is cheaper than treatment. A municipality that benefits from reduced flood risk acquires certificates on the floodplain.
The fire program improves soil and water retention for the riparian zone. The riparian zone provides shade and filtration for the wetland. The wetland provides base flow and biodiversity for the whole system. The proceeds routing mirrors this ecology — each agent sending a share of what it receives to the agents it depends on.
The collaborative stops being an applicant. It becomes a node in a value network.
---
The deepest expression of this model isn't a single project funding itself. It's connected landscapes funding each other across boundaries.
Wildlife corridors. Pollinator pathways. Migration routes. The spaces between protected areas that determine whether those areas actually work.
A wildlife corridor is the hardest thing to fund in conservation. It crosses ownerships, jurisdictions, land types, and management regimes. No single grant, no single easement, no single agency can hold it together. But without it, the refugia on either end become islands — and islands go extinct.
Ensurance infrastructure was built for exactly this.
Each corridor segment becomes an agent. "i-70-wildlife-crossing.natural-asset". "monarch-flyway-segment-12.earth". Each issues its own certificates. A "wildlife-corridor.syndicate" coordinates across segments, routes proceeds from corridor-scale instruments to the individual crossings and habitat patches that need them.
The elk winter range agent funds the migration corridor agent. The corridor agent funds the highway crossing agent. The crossing agent connects two refugia that, together, sustain a population that neither could sustain alone.
Connected refugia, connected funding. The model works because the funding architecture mirrors the ecology: distributed, relational, polycentric. Not one fund deciding where capital goes — many agents, each hyper-local, coordinating through shared infrastructure the way organisms coordinate through ecosystems.
---
This distinction matters.
Every conservation "solution" you've been pitched was a product owned by someone. When that someone changed priorities, pivoted, or shut down, your data and your funding stream went with them.
Ensurance is infrastructure. Open for anyone. You create an agent the way you register a domain name. You route proceeds the way you set up a bank transfer. The protocol is public.
what it is → what it isn't
plumbing you own → a platform you rent
your agent, your name, your wallet → a profile on someone else's system
composable — connects to anything → a walled garden
perpetual by design → dependent on any company's survival
open to anyone doing the work → gatekept by application or partnership
Your agent is onchain. It holds funds and routes value regardless of what happens to any organization — including ours.
---
"Composable" sounds technical. The concept isn't. Everything connects.
Your wetland agent can join a "pollinator-habitat.syndicate". That syndicate can include an urban greening project 200 miles away — because monarchs don't observe county lines. A beaver agent in Montana can join a "water-cycle.syndicate" alongside a headwater forest program in Colorado. A biocrust restoration in Utah can connect to a grassland syndicate that spans continents.
Species, water, nutrients, and energy cross every boundary we draw. This infrastructure lets funding do the same.
Each agent is modular. Each connection is voluntary. You decide who you coordinate with, how proceeds route, and what instruments you issue. The infrastructure makes it possible. You make it real.
---
Every agent has a permanent, human-readable name.
"roaring-fork-river.basin"
"marble-wetlands-preserve.avlt"
"wildlife-corridor.syndicate"
"pollination.ensurance"
Not a database ID. Not a grant number. A name — searchable, traceable, legible.
When you tell a water utility "your investment flows to "elk-creek.basin"," they can verify it. They can see what the agent holds, what it's received, where it's sent value. Transparency isn't a report you file once a year. It's the default.
And when you connect AI to a named account, something shifts. The agent can receive ecological data, respond to inquiries, communicate about its place, and coordinate with other agents across the network. A watershed agent that monitors conditions, talks to funders, and helps steward the landscape it represents.
The named agent is the seed. Everything else grows from it.
---
If you restore wetlands, streams, forests, or grasslands — each site can be an agent with its own wallet and instruments.
If you manage conservation lands — your portfolio can route proceeds between properties based on need.
If you coordinate across boundaries — syndicates pool resources and distribute them across your landscape.
If you build pollinator corridors, wildlife corridors, or urban nature networks — each segment becomes an agent, the corridor becomes a syndicate, the network funds itself.
If you run beaver reintroduction, prescribed fire, biocrust restoration, induced meandering, or any nature-based intervention — it maps.
If you steward indigenous lands — you can create agents under your own namespace, with full sovereignty over naming, governance, and how proceeds flow.
The infrastructure doesn't care about your tax status, your country, or your org chart. It cares about place, purpose, and the quality of connection between them.
---
Creating an agent costs less than a penny in gas. The infrastructure is open. There are no platform fees. A small percentage of proceeds flows through the protocol to sustain the shared infrastructure — the same way a watershed sustains the river it feeds.
---
We're not here to tell you what to protect or how. You understand your landscape, your stakeholders, your constraints better than any protocol ever will.
What we built is connective tissue. Plumbing that lets your projects support each other financially the way they already support each other ecologically. A way for the beaver program to fund the riparian buffer. A way for the floodplain to fund the headwaters. A way for the wildlife crossing to connect two refugia — ecologically and financially.
The pools are carved. The plumbing is laid.
Your work is the water.
BASIN DispatchesInvesting in Nature: Transforming Risk into Resilience
5X to 100X returns ensuring the value of natural capital
BASIN DispatchesInvesting in Nature: Transforming Risk into Resilience
5X to 100X returns ensuring the value of natural capital
how conservation, nature and climate projects can fund each other — and themselves at the same time the funding model that works like a watershed
Share Dialog
Share Dialog
1 comment
how conservation, nature and climate projects can fund each other — and themselves at the same time the funding model that works like a watershed