---
title: "always-on money, a river that is not"
canonical_url: https://ensurance.app/guide/always-on-money-a-river-that-is-not
markdown_url: https://ensurance.app/guide/always-on-money-a-river-that-is-not.md
subtitle: tokenized deposits can move on a sunday. a water contract cannot
category: nature-finance
---

# always-on money, a river that is not

*tokenized deposits can move on a sunday. a water contract cannot*

**Tokenized deposits** are bank deposits recorded on a shared ledger so they can move between accounts at any hour, including the hours when the bank itself is closed. The money is still a deposit. It is still a liability of the bank that holds it, still inside that bank's regulation, still the same dollar it was on Friday afternoon. What changes is when it can move and what instructions can travel with it. For a treasury that has spent decades planning around cut-off times, that is a real utility, and this post concedes it in full.

Then it walks to a place. West of Phoenix, near Tonopah, Arizona, a large power plant runs its cooling on water five cities have already used once. That water arrives on the cities' schedule, under a contract with a cap, a delivery point, and an end date. The contract cannot be asked to deliver more on a Sunday because the balance sheet moved.

:::johnson
**always-on cash can move on a sunday. a water contract cannot.** The rail is real: a deposit that moves when the branch is closed takes a timing risk off a treasury's desk. The water, the power, and the land the rest of the book assumes keep their own hours, and the bill for keeping them in condition does not move with the cash.

[what a capital provider can fund →](/solutions/capital-providers?from=guide&topic=wrapper-is-not-the-well)
:::

## the case for always-on cash, made fairly

### what are tokenized deposits?

A tokenized deposit is a claim on a commercial bank, represented as a token on a ledger the bank operates or shares with other banks. For a treasury, that is generally an unsecured claim on the bank, inside the bank's regulatory perimeter. Deposit insurance, where it applies, stops at the statutory limit. A corporate balance sits mostly above that line. Whether a given token is a deposit for every legal purpose depends on the charter and the rule. The operational difference does not: the tokenized version can move at 2 a.m. on a Sunday, can carry conditions (release when the goods are confirmed, sweep when a threshold is hit), and settles when the ledger updates rather than when a payment system opens.

The Bank for International Settlements, in its 2023 Annual Economic Report, treats tokenised deposits, alongside tokenised claims on financial and real assets, as building blocks of a programmable financial platform. It is not new money. It is deposit money that can be instructed.

For a treasury, the utility is ordinary and real. Cash trapped over a weekend can move. An intraday shortfall in one entity can be covered from another without waiting for the next window. A supplier payment can be written so money and delivery confirmation change hands together. Concede all of it.

### how is a tokenized deposit different from a stablecoin?

Both are digital dollars that move around the clock. They differ in who owes you the money and how the transfer works. A tokenized deposit is a liability of a regulated bank; when it moves between two banks, the banks still settle with each other as they always have. A stablecoin is issued by a company that holds reserves against it, and it moves like a bearer instrument: whoever holds the token holds the claim on the issuer. The BIS report draws this line, noting that tokenised deposits and asset-backed stablecoins differ in how they are transferred and in the role they play in the system.

A treasury may hold both, and a third thing beside them: a tokenized money-market fund, which is often converted into a stablecoin at the moment someone needs to pay or settle. That conversion is still cash becoming cash. Yield-bearing on one side, spendable on the other, the same dollar throughout.

| instrument | who owes you | what you hold | when it moves |
|---|---|---|---|
| tokenized deposit | a bank | a deposit, on a ledger | any hour, within the bank's network |
| stablecoin | a non-bank issuer | a token backed by reserves | any hour, wherever the token is accepted |
| tokenized money-market fund | the fund | shares in cash, short treasuries, and repo | on the fund's terms, then often converted to a stablecoin to pay |

Every row is money and improves on what it replaces. Every row also assumes what the old wrapper assumed: that the business the cash pays for has its water, its power, and its land at a location, on the day it needs them.

## the river on the other side of the ledger

Palo Verde Generating Station sits in the desert near Tonopah, Arizona, on no river and no lake. Its cooling makeup water is treated municipal effluent: wastewater the cities of Phoenix, Mesa, Tempe, Scottsdale, and Glendale have used, treated at the regional 91st Avenue Waste Water Treatment Plant, and piped west to the plant.

That arrangement is a contract, and the contract is public. On April 23, 2010, Arizona Public Service, as operating agent for the plant's participants, and the five cities signed a Municipal Effluent Purchase and Sale Agreement, disclosed in an APS 8-K for that date. It replaced an agreement from 1973. It provides up to an annual allotment of 80,000 acre-feet of treated effluent, about 26 billion gallons a year, for the plant's cooling. It expires on December 31, 2050. Price follows a negotiated schedule that steps up and is then indexed, with a cap on the annual adjustment. Read it as a treasury would: capped volume, named delivery point, fixed term, a counterparty on each side, an escalator.

What the contract does not have is a settlement button.

### can a river settle 24/7?

No. What arrives at the plant is whatever the five cities' residents used, what the treatment plant processed, and what the pipeline carried. The cities have to keep treating water for the effluent to exist at all, with the plant running, operators on shift, and discharge standards met, and they treat it on the curve their residents set, daily and seasonal, not flat. Upstream of the cities' taps is the water they drink in the first place: the Salt and Verde river system, alongside the valley's other supplies. Effluent is that river system after a city has used it once. Its quantity and quality track what came in.

You could pay for that water at 3 a.m. on a Sunday with a tokenized deposit, and the payment would settle. The effluent would still arrive on the cities' curve. Sunday settlement does not create effluent. The always-on rail changes when the invoice clears. It does not change when the water shows up or how much of it there is.

### what limit does the water contract set?

The load-bearing limit is the 2010 contract, not a permit with the plant's name on it. A **cap**: up to 80,000 acre-feet in a year, and a plant that wants more has no bigger button to press. A **point**: the water is deliverable at the plant, from that facility, through that pipe; it is not fungible with treated water in another county. A **term**: the arrangement ends on December 31, 2050, and a successor has to be negotiated with cities whose own water position in 2050 is not known today. A **counterparty that must perform physically**: the cities do not owe a number; they owe treated water, which means a working plant, a discharge permit on that plant, and a source to feed it. The rivers those cities drink are appropriated supplies. Sunday cash does not enlarge either the contract or those rights.

| | tokenized deposit | effluent contract |
|---|---|---|
| moves | any hour | on the cities' treatment and pipeline schedule |
| quantity | whatever the account holds | up to a fixed annual cap |
| location | any node on the network | one delivery point |
| term | none | expires December 31, 2050 |
| if the counterparty fails | the bank's balance sheet; insurance only to the statutory limit | no water at the plant until someone else treats some |

The left column is the utility this post conceded. The right column is what the rest of the book assumes and rarely writes down.

## hold both

The objection writes itself: a payment rail and a water contract are different instruments for different jobs, and faulting one for not doing the other's is a category mistake. Agreed. The rail works at what it is for. The point is narrower. A treasury that has moved to always-on cash has removed a timing risk from the money side of the ledger and left the one on the operating side exactly where it was. The cooling water a desert plant buys under that contract, the rivers the cities drink before they sell the effluent, and the aquifer under that valley exist whether or not anyone buys an ETF, a tokenized fund, or a certificate. Ensurance is how that living system gets funded. It is not the wrapper, and it is not the rail.

A second objection: the effluent is already paid for, so this is a contract problem. The invoice is. The plant pays the cities. The cities pay to run the treatment plant. Funding the living system upstream of those intakes is the capital question the invoice does not answer. Salt River Project and the cities already spend on parts of that system. The 80,000 acre-feet is not a line item for its condition. The rivers have a year of their own, in snowpack, monsoon, and drought.

That is the one-line gloss this series allows itself. A **specific certificate** funds a named living system, a river reach or the land that feeds it, and pays for the work that keeps it in condition. It is not structured or offered as a security. It is not a stablecoin, not a water right, and not a claim on the effluent contract. It does not refill the cooling pond, and nobody here operates the pipe. It gives the living system upstream of a known payor a funding line that does not depend on that payor's next contract.

Nothing in that prices the river as worth the plant. The plant's revenue is what the plant earns; the river's worth is not that number, and an accounting that says so has confused the bridge for the far bank. The claim is only that the rail settles the money, the river sets the limit, and a book that has bought the first should know who funds the second. The stablecoin version of the same argument, written for an agent's treasury rather than a corporate one, is [stablecoins quote the price. the river sets the limit.](/guide/stablecoins-quote-the-price-the-river-sets-the-limit?from=guide)

## where this stands

Our stage, plainly. Specific certificates exist, and the [capital providers page](/solutions/capital-providers?from=guide&topic=wrapper-is-not-the-well) is live. It describes a structure in which the party that depends on a living system pays the premium and land stands as security. Volumes are small. We do not administer a tokenized deposit, a tokenized money-market fund, or an ETF, and nothing here settles through one. No bank, fund, or utility named here has endorsed any of it. None of this is investment advice or a recommendation to hold a deposit token, a stablecoin, a fund share, or a certificate.

If your treasury has already moved to always-on cash, you have done the easy half of the timing problem. The harder half is a river that keeps its own hours, upstream of a city, upstream of a plant, upstream of a line in your book. It has a payor. It does not yet have a funder.

## sources

[Arizona Public Service Company, Form 8-K, April 23, 2010](https://www.sec.gov/Archives/edgar/data/7286/000095012310038881/c99652e8vk.htm) — Municipal Effluent Purchase and Sale Agreement: five cities, 91st Avenue plant, up to 80,000 acre-feet a year, expiry December 31, 2050

[Bank for International Settlements, Annual Economic Report 2023, chapter III](https://www.bis.org/publ/arpdf/ar2023e3.htm) — tokenised deposits as a building block of a programmable platform; how they differ from asset-backed stablecoins

## the series

1. [what tokenization of real assets actually moves](/guide/what-tokenization-of-real-assets-actually-moves?from=guide)
2. [a bitcoin sleeve is not a supplier](/guide/a-bitcoin-sleeve-is-not-a-supplier?from=guide)
3. [always-on money, a river that is not](/guide/always-on-money-a-river-that-is-not?from=guide)
4. [collateral that still needs a basin](/guide/collateral-that-still-needs-a-basin?from=guide)
5. [the fourth utility of a token](/guide/the-fourth-utility-of-a-token?from=guide)