DAO treasuries are often called the financial backbone of decentralized governance. They fund developers, security, liquidity, grants, market making, research, and community growth.

But holding a large treasury is not the same as creating sustainable value.

The real question for every DAO is simple:

Can treasury spending build recurring protocol revenue, stronger security, retained users, and long term resilience? Or is it only paying for temporary activity while the revenue problem becomes worse?

This question matters in DeFi. Many protocols hold treasury assets in stablecoins, ETH, governance tokens, and protocol owned liquidity. But operating costs, incentive programs, and contributor budgets can become larger than real protocol revenue.

A DAO can survive this gap for a period of time. It cannot ignore it forever.

A treasury is a reserve of assets. Revenue is recurring income from actual protocol usage.

These are different things.

A DAO may have millions in treasury assets. But if users do not generate enough fees, the DAO can slowly spend down its reserves while appearing active.

A simple financial view is:

Protocol revenue minus operating cost minus incentive cost minus security and risk cost equals net treasury flow.

If this number stays negative for a long time, the DAO is using treasury capital to fund operations instead of using operating income.

Treasury runway is also important.

Treasury runway means liquid treasury assets divided by monthly net burn.

For example, if a DAO has USD 9 million in liquid assets and burns USD 150,000 each month, it may appear to have about 60 months of runway.

But runway is only an estimate. Token prices can fall, treasury assets can become illiquid, security incidents can create emergency costs, and revenue can decline further.

A treasury gives time. It does not guarantee sustainability.

Balancer is a useful current case study. Its DAO is considering whether continued spending can create value or whether the protocol should wind down and return remaining treasury assets to BAL holders.

A governance proposal recommends a phased wind down. The proposal would move eligible pools to withdrawals only, end contributor contracts, and distribute eligible treasury assets to BAL holders. The proposal argues that the protocol has not restored revenue after the November 2025 exploit, even after restructuring, reduced budgets, ending emissions, redirecting protocol fees to the DAO, and pursuing product growth through Balancer v3 and AutoRange Pools.

Balancer Revenue and Treasury Data

Using the reported August revenue and burn figures, the minimum monthly operating gap was around negative USD 90,000.

The lesson is not that every DAO should wind down when revenue falls. The lesson is that every DAO needs an honest stopping point.

If a turnaround plan does not produce measurable recovery, continuing to fund it may only reduce the capital eventually available to token holders.

The proposed Balancer plan includes withdrawal only treatment for pausable pools from 30 October 2026, contributor contract termination on 31 October, a limited transition team, a USD 400,000 wind down spending cap, and a future BAL burn based treasury claim process for holders. This remains a governance proposal, not a final outcome.

Treasury spending becomes sustainable when it creates a clear chain.

Treasury capital should improve a product, security, or liquidity. That improvement should create retained usage or reduce risk. Retained usage should create recurring revenue and protocol resilience.

Not every investment must create immediate fees. Security spending can reduce expected losses. But every program should have a defined purpose and measurable evidence of improvement.

Funding a new lending market, swap product, stablecoin vault, cross chain feature, or user interface can be sustainable if it creates retained fee paying usage.

A strong funding cycle looks like this:

Grant funding supports a useful product. The product attracts retained users. Retained users generate recurring fees.

A weak funding cycle looks like this:

Grant funding supports a short term campaign. Incentives end. Users leave. Protocol revenue does not improve.

A DAO should not measure only new wallets, social media attention, a short TVL increase, or announcement reach. It should measure retained activity after incentives and grants end.

Security spending can be one of the best uses of a DAO treasury.

Examples include:

• Smart contract audits

• Bug bounty programs

• Formal verification

• Oracle monitoring

• Independent risk assessments

• Treasury diversification

• Multisig security

• Emergency response systems

• Insurance or loss reserve design

Balancer's reported USD 128 million v2 exploit shows why security is not optional. The protocol's revenue did not recover to its earlier level after the incident.

Security spending can be assessed by asking whether it reduces the probability of failure or lowers the potential loss from a failure.

Liquidity incentives can create TVL and volume quickly. But if liquidity leaves after rewards end, the DAO has rented capital instead of building a market.

For every liquidity program, a DAO should measure:

• TVL before incentives

• TVL during incentives

• TVL 30, 60, and 90 days after incentives end

• Organic trading volume

• Incentivized trading volume

• Fee revenue per dollar of incentives

• Liquidity provider retention

• Slippage and execution quality

• Concentration among large liquidity providers

A simple question is useful: how much retained liquidity or net fee revenue was created for every dollar spent on incentives?

If a DAO spends USD 1 million on incentives but retains little liquidity and creates no lasting fee revenue, it did not create sustainable protocol value.

Protocol revenue does not automatically benefit governance token holders.

A DAO should clearly show:

• Where protocol fees are collected

• How much revenue enters the treasury

• How much funds operations, security, or growth

• Whether token holders receive value through buybacks, burns, staking, revenue sharing, or governance controlled reserves

• How token inflation affects holders

• Whether token holders carry risk without receiving economic upside

Tokenomics are credible only when the relationship between usage, fees, treasury, and token holder rights is public and understandable

Investment or Subsidy?

Treasury spending is an investment only when the DAO can define the expected return, measurement period, responsible party, and stop condition before funds are released.

A DAO should not approve spending because a proposal says it will grow the ecosystem.

Every proposal should answer four questions:

1. What specific problem will this funding solve?

2. What measurable outcome does the DAO expect?

3. When will the DAO review the result?

4. What will happen if the result is not delivered?

The full accountability process should be visible.

A proposal should define the budget. The budget should be released through milestones. Every payment should be visible onchain. The DAO should review public KPI data after funding.

Without this process, the DAO cannot distinguish genuine value creation from delayed failure.

Before funding begins, the DAO should publish the current data

A baseline turns vague growth language into a testable commitment.

Instead of writing, "This grant will grow the ecosystem," a proposal should state, "This grant will be successful only if it produces 1,000 retained monthly users, USD X in recurring fees, or a defined security improvement by a stated date."

Large grants should not be paid fully upfront.

This structure protects the treasury from funding teams that deliver presentations but never deliver a usable product.

DAOs often celebrate announcements.

• Partnership announced

• Grant approved

• New chain deployment launched

• Liquidity campaign started

• Market maker hired

• Dashboard published

But announcements are not results.

• Product live or not

• Smart contract verified or not

• Monthly active users

• 30, 60, and 90 day user retention

• Fee revenue generated

• Transactions generated

• Open source code published

• Number of integrations

• Budget used versus unused

• Milestones delivered on time

• TVL before, during, and after incentives

• Organic volume compared with incentivized volume

• Fee revenue per dollar spent

• 90 day liquidity retention

• Slippage and execution quality

• Liquidity provider concentration

• Approved budget compared with actual cost

• Features shipped compared with roadmap

• Delivery date compared with planned date

• Audit and security status

• Product usage change

• Revenue impact

• Cost per active user

• Cost per transaction

• Cost per unit of protocol revenue

• Order book depth

• Bid ask spread

• Real volume compared with suspected wash volume

• Market maker inventory exposure

• Treasury capital deployed

• Unused capital returned

• Improvement after 30, 60, and 90 days

Lido DAO's contingent LDO market making mandate is an example of a policy that should include this level of reporting. If treasury capital is deployed to support token liquidity, the DAO should disclose the amount deployed, selected provider, inventory risk, liquidity depth, spread changes, and whether the support created measurable improvement.

A public dashboard is useful. But a DAO should also issue a simple monthly Treasury Scorecard in plain language.

A useful treasury report should show:

• Total treasury value

• Liquid and non liquid assets

• Stablecoin reserve

• Asset location by chain and custody provider

• Monthly protocol revenue

• Monthly operating cost

• Incentive emissions

• Net treasury burn

• Runway estimate

• Asset concentration

• Inflows and outflows by category

• Policy compliance

• Expected liquidity needs for the next one to three months

Every major treasury program should include a review date and a stop rule.

Examples:

• Stop liquidity incentives if 90 day retained liquidity remains below 40 percent.

• Pause grant payments if milestones are delayed by more than 60 days.

• Do not renew a contributor budget without verified deliverables.

• End market making support if spreads do not improve within 90 days.

• Reduce emissions if protocol fees remain below incentive costs for two consecutive quarters.

• Trigger an independent treasury review when runway falls below 12 months.

The principle is simple. If the KPI is not achieved, the DAO should pause, review, reduce, or end funding.

Without stop rules, temporary spending programs can become permanent treasury drains.

Balancer's proposed wind down can be understood as a late stage stop rule. Its governance discussion argues that a turnaround was already attempted and more spending could consume assets that may otherwise be distributed to BAL holders.

No single group should control the full spending process.

For routine spending, a DAO can delegate limited authority to an elected committee. For large strategic commitments, token holders should retain direct governance control.

Multisig treasury systems should have public signer roles, threshold rules, transaction labels, signer rotation procedures, and a verifiable link between every payment and the governance decision that approved it.

Every treasury outflow should have a public label:

• Proposal ID

• Vote result

• Recipient name

• Recipient wallet address

• Budget category

• Milestone number

• Payment amount

• Payment date

• Expected KPI

• Review date

• Completion status

The community should be able to follow the full path from forum proposal to governance vote, then to multisig transaction, recipient wallet, and outcome report.

This is the practical promise of onchain governance. Treasury funds should not become invisible after a vote passes.

A DAO may appear wealthy because it holds a large amount of its own governance token. But this can become dangerous in a market decline.

If the token price falls, treasury value can fall exactly when contributor payments, security funding, and emergency liquidity are most needed.

Research on DAO treasuries found that 81.67 percent of treasury assets in its sample were invested in native DAO tokens. This concentration creates major volatility and financial planning risk.

A more resilient treasury can use separate buckets.

The exact allocation will differ across DAOs. But a DAO should not rely entirely on the market value of its own token to pay contributors, protect users, and survive a bear market.

Large DAOs should consider an independent Treasury Review Council with a narrow accountability mandate.

The Council should not control the treasury. It should verify and report on:

• Monthly revenue and spending

• Budget compared with actual outcomes

• Grant milestones

• Multisig payment labels

• Treasury concentration

• Treasury runway

• Conflict of interest disclosures

• Market maker and service provider performance

• Emergency control use

• Security reserve adequacy

Its monthly report should answer four questions:

What did the DAO spend?

What did it receive?

What did not work?

What should be renewed, paused, reduced, or stopped?

This creates a necessary separation between people spending treasury capital and people evaluating whether spending worked.

DAO treasury spending can create sustainable protocol value. But it cannot replace a viable revenue model.

The strongest treasury programs use transparent capital, measured outcomes, independent verification, clear stop rules, and recurring revenue.

The weakest programs use treasury capital for temporary incentives, short term activity, and unmeasured costs.

Balancer's reported revenue decline from more than USD 1 million per month in October 2025 to under USD 60,000 in August 2026, while operating burn stayed around USD 150,000 per month, shows why a DAO must define when spending should stop.

For DAO delegates, the question is not, "Should we spend treasury funds?"

The better question is:

What lasting protocol value will this spending create, how will the DAO measure it, who will verify it, and when will the DAO stop funding it if it fails?

A treasury should not be judged by how much capital it holds. It should be judged by how transparently it deploys capital, how honestly it reports results, and how effectively it turns community funds into durable protocol value.

• BeInCrypto, Balancer Proposes to Wind Down After Turnaround Plan Fails to Lift Revenue, September 2026.

• Chainlink, What Is a DAO Treasury?, February 2026.

• ChainScore Labs, How to Architect a DAO Treasury for Grants and Investments, July 2026.

• Eco, Onchain Treasury Reporting Tools and Standards, September 2026.

• Chainlink, DAO Treasury Management and Onchain Governance Spend, September 2026.

• Blockchain Council, DAO Treasury Audit Guide for Multisig and Governance, May 2026.

• SSRN, How Are You DAOing? The State of DAO Treasuries, November 2023.

• Blockchain Research Lab, The State of DAO Treasuries, October 2023.