Why do DAO treasuries hold stablecoins?
A DAO, a decentralized autonomous organization, controls its treasury through onchain governance: members propose, vote, and the approved transactions execute from contracts or shared wallets the DAO controls. Many DAOs hold most of their value in their own token, which rises and falls with crypto markets. Stablecoins give the treasury a part that holds steady in dollars, so it can pay contributors, auditors, grants and service providers without selling its own token into a falling market.
That part is a stablecoin treasury, and it does the job a company's cash does: it meets known costs and keeps a reserve for the unknown ones. It differs from company cash in three ways. Every holding and transaction is public. Decisions go through governance, which can take days. And the DAO usually acts as an onchain allocator itself, holding positions in contracts it controls, or appoints a manager to act for it under a mandate.
Stablecoins left idle in a wallet earn nothing, and a large treasury that leaves them idle gives up income that could extend its runway. Putting them to work brings risks the DAO did not carry while the money sat still, which is why the rules come before the first deposit.
The Key facts box shows the size of the market these treasuries hold: the USD-pegged stablecoins in circulation, as DefiLlama counts them, with the date of the count (latest figure and source).
How do runway, reserve and longer-term buckets work?
The common approach splits stablecoin holdings by when the money will be needed, and treats each part differently.
- Operating runway covers the next few months of budgeted spending. It stays instantly available: in stablecoins held directly, or in sources a depositor can leave the same day.
- The reserve is a buffer for costs nobody budgeted and for a fall in the DAO's own token. It can sit in liquid yield sources whose redemption terms are stated in advance.
- The longer-term portion is capital the DAO does not expect to touch for a year or more. It can accept slower redemptions, such as scheduled windows, in exchange for a higher yield or a return that does not move with crypto prices.
The budget sets the size of each bucket. A DAO that spends a predictable amount each month can size its runway in months of spending and set its reserve as a further number of months; what is left is the longer-term portion. A DAO with an uncertain budget, or with large grants that can fall due together, keeps more in the first two buckets.
Buckets also make governance workable. Members vote on the size of each bucket and the sources allowed in it, and the treasury team or an outside manager works within those limits without a new vote for every move.
Which yield sources fit each bucket?
For the runway, access matters more than yield. Stablecoins held directly, or lending markets and vaults with deep same-day liquidity, fit here. Before relying on same-day withdrawals, check how much a source let depositors take out on its busiest recent day, since a vault can look instant on a quiet day and fall short on a busy one.
For the reserve, the usual candidates are tokenized Treasury funds and curated lending vaults. A tokenized Treasury fund passes through the interest on short-term US government debt, so its yield follows dollar rates such as SOFR, and money leaves through the fund's redemption process. In a curated lending vault, a vault curator chooses the lending markets and sets limits on each, and the interest comes from onchain borrowers, so both the yield and the liquidity move with crypto markets. The Key facts box gives the latest tokenized Treasury yield with its date and source (latest figure and source).
For the longer-term portion, private credit vaults that lend to businesses offchain are the main candidate. Their income is non-crypto-correlated yield: it does not rise and fall with crypto prices, which balances a treasury whose own token does. The cost is time, since withdrawals wait for scheduled windows or for loans to repay. Eligibility matters most here: these vaults commonly admit only holders who pass identity checks, so the DAO needs to know which of its entities or wallets can pass them.
That longer-term shelf is still thin onchain. In a dataset pulled on 7 August 2026, vaults tagged as real-world assets held $566 million, 5.7% of curated vault TVL, and the rest earned its return from crypto-native activity. The August 2026 market structure report explains the dataset and the tagging.
Reward programs fit no bucket on their own. A reward can raise what a source pays for a while, but the budget should assume the base yield, and the treasury should know each reward's end date. For the differences between the sources in one table, see stablecoin yield sources compared.
What limits should governance set?
Limits turn a strategy into rules a manager can follow and members can check. The usual set:
- Approved sources: the kinds of source each bucket may use and, where the DAO wants it, the named vaults or funds. Anything outside the list needs a new vote.
- Counterparty caps: the most the treasury may hold with any one issuer, curator, fund or protocol, written as a share of the treasury.
- Concentration caps: the most in any one vault or market and in any one stablecoin, so a single failure cannot take the whole reserve.
- Minimum same-day liquidity: a floor, often written in months of runway, that must stay withdrawable the same day.
- Exit rules: the events that trigger a withdrawal without a new vote, such as a stablecoin trading below its peg, a curator raising fees, an oracle failing or a source missing a redemption, and who may act on them.
- Rebalancing: how often each bucket is brought back to its target, and how far it may drift in between.
The caps are choices for each DAO; no standard number fits every treasury. What matters is that they are written down, approved and checked against the chain.
How do DAOs approve and report allocations?
Approval usually starts with a proposal: a forum post that sets out the purpose, the buckets, the sources, the limits and the risks, followed by discussion and a vote. Once approved, the transactions execute from the governance contract or a shared wallet that needs several signers, sometimes after a timelock that gives members time to object.
Many DAOs hand a bucket to an outside manager or curator under a mandate approved by vote. A mandate names the sources allowed, the caps, the liquidity floor, the fee, the reporting duties and how the DAO can end the mandate and recover its money. The assets can stay in contracts the DAO controls, with the manager given only the permission to move money between approved sources.
Reports close the loop. A regular public report shows where each bucket sits, the yield earned with base yield and rewards shown apart, any breach of a limit and what was done about it. Because the holdings are onchain, any member can check the report against the chain.
Public examples of DAOs and protocol foundations putting treasury assets to work are described in the October 2026 RWA vaults report, in its section on the onchain allocators.
What can go wrong?
- A source cannot return money when the runway needs it, because more depositors asked at once than the source held in cash.
- A stablecoin loses its peg, or its issuer freezes the tokens.
- A smart contract fails, or an oracle misprices collateral, in a vault or market the treasury uses.
- Borrowers default in a private credit vault, or collateral in onchain lending falls faster than liquidations can clear.
- A reward ends, and the yield the budget assumed falls with it.
- Governance moves too slowly: an exit needs a vote that takes days, while the problem takes hours. Exit rules approved in advance close that gap.
- A signer loses a key, or keys concentrate in too few hands.
- The DAO becomes too large a share of a vault, so its own withdrawal moves the market it is leaving.
Each of these is a reason to check a source before the first deposit and again at each report. For a checklist that does this one vault at a time, see how to evaluate a yield vault.