---
title: what protocol owned liquidity can and cannot buy
canonical_url: https://ensurance.app/guide/what-protocol-owned-liquidity-can-and-cannot-buy
markdown_url: https://ensurance.app/guide/what-protocol-owned-liquidity-can-and-cannot-buy.md
subtitle: a market can stay open. a price can still be wrong.
category: onchain
---

# what protocol owned liquidity can and cannot buy

*a market can stay open. a price can still be wrong.*

**Protocol owned liquidity** means a protocol holds its own liquidity-provider position in the market for its token, instead of renting that liquidity from people who leave when the extra payment stops. That is the whole definition. Most of what follows is about the gap between what that position can buy and what it gets credited with buying.

Start with a place, because the money only matters if it reaches one. Snow falls on the Colorado River headwaters, in valleys like the Roaring Fork and the Eagle, and melts into the river that much of the basin downstream depends on. The headwaters already exist, whether or not a budget, a foundation, or a fund writes a check. [**Ensurance**](https://ensurance.app/?from=guide) is how that living thing gets an account addressed to it. It is not the river, and it is not the snow.

:::johnson
**an owned market stays open. it does not make the price true, the money new, or the river well.**

Protocol owned liquidity solves one problem: depth that walks away. Keep that claim, and drop the three it is often asked to carry.

[see an account addressed to the headwaters →](/colorado-headwaters.syndicate?from=guide)
:::

## what protocol owned liquidity is

A token trades in a pool. Someone has to put both sides of the trade into that pool so a buyer can buy and a seller can sell without moving the price too far. In the early DeFi pattern, the protocol paid strangers to do it, usually with freshly issued tokens on top of trading fees. The pool looked deep. Then the extra payment ended, the depositors took their capital to the next pool that was paying, and the market thinned out behind them. The depth had been rented, and the lease ran out.

The fix is simple to say. The protocol owns the position itself. Its treasury holds the liquidity-provider position, so the depth stays for as long as the protocol keeps it there.

OlympusDAO's bonding, in 2021, was the public version. Instead of paying people to park liquidity for a while, the protocol sold its own token at a discount to people who handed over liquidity-provider positions or other assets, and it kept what it received. Over time the protocol accumulated its own liquidity-provider positions instead of renting them. The phrase "protocol owned liquidity" spread from there, and a lot of teams have since built their own variations.

Two plain statements before going further. First, **ensurance does not run a bonding program.** Second, ensurance did not invent protocol owned liquidity. The idea belongs to the DeFi teams who named it and tested it in public. This post borrows the question, not the credit.

## what it can buy

Give the idea its due. It buys something real, and it is not small.

**It buys a market that does not depend on a visitor who leaves.** Rented liquidity is a guest. It arrives for the payment and goes when the payment stops, and it has no reason to care what the market is for. Owned liquidity is a resident. It is still there next season, after the excitement has moved on, when the only people left are the ones who actually need to trade.

That matters more for a coin tied to a living thing than for most tokens. A headwaters forest does not work on a campaign calendar. The snowpack builds through winter, melts through spring, and the river runs low by late summer whether or not anyone is paying attention. Anything that pays toward that condition has to show up again next year and the year after. In this protocol, paying toward a place means buying that place's coin or certificate, and when that purchase runs through a pool, the pool has to be open when the season says pay. A pool that only exists while somebody is subsidizing it cannot promise that. A pool whose depth belongs to the account that needs it can at least stay open.

So the honest version of the claim is narrow. An account addressed to a place, signed by named people, could one day hold its own position in a market for a certificate or coin tied to that place. If it did, the market would not vanish when an outside incentive ended. That is the whole gain, and it is worth having.

## what it cannot buy

Here is the contrast, in one table.

| protocol owned liquidity can buy | it cannot buy |
|---|---|
| A market that stays open after outside incentives end | A true price |
| Depth that belongs to the account, not a guest | New money |
| A counterparty that is still there next season | The condition of a river |

### a true price

A pool that stays open will always quote a price. That price is what the last trade said, given the depth in the pool. Depth makes the price harder to push around, and owning the depth keeps it there. Neither makes the price more accurate. A market can stay open and a price can still be wrong, for years, in either direction.

That holds for anything tied to a place. A certificate or coin connected to the headwaters will trade at whatever the people trading it decide. Nothing about owning the pool forces that number to match the cost of the work on the slopes, or the value of the water downstream. And nothing in this design says the price goes up as more accounts join. More accounts mean more places with an address. They do not mean a higher number on a chart.

### new money

Every unit of capital in a protocol-owned pool came from someone. A bond is a trade: the protocol hands over its own token, usually newly minted, and someone hands over an asset they already had. The protocol ends up holding more of its market, and everyone already holding the token owns a little less of it. The world does not end up holding more money.

The same is true of any account addressed to a living thing. The funds in it came from a person or an institution. The account changes where the money lands and how often it can land there. It does not create the money.

> *A forest recycles the rain. It does not invent the ocean.* ([You can't seed a cloud that isn't there](/guide/you-cant-seed-a-cloud-that-isnt-there?from=guide) explains the moisture side.)

A forest pulls water that started at sea back into the sky and drops it again downwind. That recycling is real and it matters to every town under the cloud. But the forest needs the ocean first. An account can keep money moving toward a place, purchase after purchase. It still needs a payer first.

### the condition of a river

Liquidity is not snowpack. A full pool does not shade a creek, hold a slope, or keep a meadow wet enough to release water slowly into August. The condition of the Colorado River headwaters is measured on the ground: streamflow, forest cover, the state of the riparian strip along a named reach. None of those numbers move because a market for a related coin got deeper.

That is not a knock on the mechanism. It is just the line between a market and a place. The market can keep a door open. Someone still has to walk through it and pay for the work.

## where ensurance is today

On 12 Oct 2026 the account catalog had 2,085 active accounts. Of those, 86 had a wallet deployed.

Two of them sit on this river. [`colorado-river.basin`](/colorado-river.basin?from=guide) is the basin-wide account. [`colorado-headwaters.syndicate`](/colorado-headwaters.syndicate?from=guide) is the account the catalog describes as coordinating protection of the headwaters across the Roaring Fork Valley and the Eagle Valley. Both accounts exist and both have wallets deployed. If you want the longer case for why a place can hold an account at all, [a place and a purpose can hold an account](/guide/a-place-and-a-purpose-can-hold-an-account?from=guide) makes it.

Here is what has not happened yet. There is no published account-to-account purchase to point to. Neither of those accounts holds a liquidity-provider position in any pool, and there is no bonding program behind them. The headwaters account is the payout recipient of one coin that does have a pool, [tresses](/general/tresses?from=guide), so trading proceeds from that pool arrive at the account. That is proceeds arriving. It is not a position held, and it is not a purchase by another account. The design is ahead of the example.

## what the purchase recycles, when it happens

When an account-to-account purchase does happen, it will look less like DeFi and more like an operating line.

Picture a downstream account paying the account addressed to the headwaters, signed by named people, for a condition the downstream account depends on. The money will have come from a person or an institution: a town, a water user, a land trust partner, a donor. Neither account conjures it. What the headwaters account adds is the address. The payment lands on the place, not only on a contract that expires; it can repeat on the river's season; and it sits on a line that the next reviewer can read.

What the payer gets on the other side is the condition, not a resale. Water that does not have to be filtered. A slope that holds. Habitat that is still there in ten years. That is an avoided cost. It is the reason a dependent account would pay at all.

The money goes where the mandate says. An account with no stated purpose will spend toward nothing in particular, which is why [an agent needs a mandate before it needs a wallet](/guide/an-agent-needs-a-mandate-before-it-needs-a-wallet?from=guide): the mandate names the reach, the condition, and when to stop. And [agents don't have ethics](/guide/agents-dont-have-ethics?from=guide), which is the other half of the argument. The instruction decides whether an account protects or extracts. The model does not.

A person signs. The account addressed to the headwaters does not decide anything on its own. The named people who speak for that place set the mandate, approve the purchase, and answer for it afterward. Protocol owned liquidity, if an account ever uses it, is a way to keep that purchase from depending on a stranger's patience. It is not a way to take the people out of it.

## where to start

This is not a buyer's page. Nothing here is advice to buy or hold any coin, certificate, or token.

If you already speak for a place, whether a tribal nation, a watershed council, a land trust, a ranch, or a group that has been caring for a reach of river for years, you can [open an account for that place](/agents/create?from=guide) and write the mandate before anything else.

If you want to talk through whether an account fits the place you work for, [talk to someone who can help](/contact?from=guide&topic=give-the-herd-the-account).

## sources

[ensurance account catalog](https://ensurance.app/api/accounts) — read 12 Oct 2026: 2,085 active accounts, 86 with a wallet deployed; `colorado-river.basin` and `colorado-headwaters.syndicate` records and descriptions.

[ensurance coin catalog](https://ensurance.app/api/general) — read 12 Oct 2026: `tresses` payout recipient and pool.

## the series

1. [who pays for nature](/guide/who-pays-for-nature?from=guide)
2. [why the biodiversity funding gap does not close](/guide/why-the-biodiversity-funding-gap-does-not-close?from=guide)
3. [can an animal have a bank account](/guide/can-an-animal-have-a-bank-account?from=guide)
4. [what is the beneficiary pays principle](/guide/what-is-the-beneficiary-pays-principle?from=guide)
5. [what protocol owned liquidity can and cannot buy](/guide/what-protocol-owned-liquidity-can-and-cannot-buy?from=guide) (this post)