Treasury Management for Token Projects and DAOs

Your treasury is the financial engine of your project. It funds development, incentivises growth, provides liquidity, and acts as a strategic reserve for opportunities and emergencies. How you manage it determines whether your project has a 2-year or 10-year runway.

Most token projects don't have a treasury strategy. They have a treasury allocation in their tokenomics document and a multisig wallet with tokens in it. The actual decisions around when to sell, how much to hold in stablecoins, when to deploy capital, and how to communicate treasury activity to the community are made ad hoc, often under pressure, and frequently at the worst possible time.

This guide provides a framework for thinking about treasury management as an ongoing operational discipline.

What's in a token treasury

A typical token project treasury contains:

Native tokens. The project's own token, allocated from the initial distribution. This is usually the largest position by notional value, but that value fluctuates with market conditions.

Stablecoins. USDC, USDT, or DAI acquired through fundraising rounds, OTC sales, or protocol revenue. This is the actual operating capital.

Other crypto assets. ETH, BTC, or tokens received through partnerships, grants, or strategic swaps. Sometimes held intentionally, sometimes accumulated without a plan.

Fiat. Traditional bank balances in USD, EUR, or GBP. Increasingly common as projects set up legal entities for operational expenses.

The biggest mistake is treating native token holdings at current market price as real capital. If your treasury holds 100M tokens and the token is at $1.00, you do not have $100M. You have tokens that you might be able to convert to $100M over a very long time, at significant discount, with substantial market impact. The actual liquid value of a large native token position is a fraction of its mark-to-market value.

Treasury objectives

Before making any decisions, define what your treasury is for. Most treasuries serve four purposes, and they often conflict:

Operating runway. Funding salaries, infrastructure costs, audits, legal fees, and other operational expenses. This requires stable, liquid capital, which means stablecoins or fiat.

Ecosystem incentives. Grants, partnerships, liquidity mining programs, and community rewards. This typically uses native tokens and requires careful planning to avoid excess sell pressure.

Strategic reserve. Capital set aside for unexpected opportunities (acquisitions, emergency hires, market events) or unexpected problems (security incidents, legal challenges). This should be highly liquid and conservative.

Market operations. Capital deployed for market making, liquidity provision, buyback programs, or OTC transactions. This requires both native tokens and stablecoins depending on the operation.

The conflict arises because every token sold from treasury for operating expenses is sell pressure on the market. Every token held in reserve is capital not deployed for growth. Every stablecoin spent on operations is runway shortened. Treasury management is the art of balancing these competing demands.

Liquidation strategies

At some point, you need to convert native tokens to stablecoins or fiat. How you do this matters enormously for your token's market health.

TWAP (time-weighted average price)

Sell a fixed amount of tokens at regular intervals over an extended period. For example: sell $50K worth of tokens every day for 6 months. This spreads sell pressure evenly and avoids large single-day impacts.

TWAP works best when: you have a long time horizon, daily volumes are sufficient to absorb the sell amount without moving price more than 1-2%, and predictability is more important than optimising execution price.

VWAP (volume-weighted average price)

Sell proportionally to market volume. When volume is high, sell more. When volume is low, sell less. This is more adaptive than TWAP and reduces market impact because you're selling into strength rather than against weakness.

VWAP works best when: volume varies significantly day to day, and you want to minimise price impact per unit sold.

OTC sales

Sell large blocks of tokens to a single buyer (or small group of buyers) at a negotiated price, typically at a discount to market. The tokens transfer directly, not through the exchange order book, so there's no visible market impact.

OTC works best for: large sales ($500K+), when you need capital quickly, or when the market can't absorb the size without significant price disruption. The discount (typically 5-15% depending on size and lockup) is the cost of avoiding market impact.

Structured programs

More sophisticated approaches combine multiple methods: OTC for large blocks, TWAP for ongoing operational needs, and conditional selling (only sell when price is above a certain level, or only sell during high-volume periods).

The best treasury operations use a mix. No single method is optimal for all situations.

Buyback programs

Buybacks are the opposite of liquidation. The project uses stablecoins or revenue to buy its own token on the open market. This creates buy pressure, reduces circulating supply (if tokens are burned), and signals confidence to the market.

When buybacks make sense

Protocol revenue exceeds operating costs. If your protocol generates fees and you have surplus capital after covering expenses, buybacks are a natural use of that surplus. This is the crypto equivalent of stock buybacks funded by free cash flow.

Token is trading below fundamental value. If the team genuinely believes the market is undervaluing the token and has the capital to act on that belief, buybacks signal conviction. But be honest with yourself about whether this is analysis or hope.

Community confidence is low. During bear markets or after negative events, a transparent buyback program can stabilise sentiment. The key word is transparent. Announce the program, define the parameters, and execute consistently.

When buybacks don't make sense

Using native tokens to buy native tokens. This is circular and accomplishes nothing.

Funded by selling other assets you need. If buying back tokens means shortening your operating runway, the short-term market impact isn't worth the long-term risk.

As a substitute for building. Buybacks don't fix a product problem. If your token is declining because the protocol isn't being used, buying tokens back just delays the inevitable.

Structuring a buyback

Define the program clearly before announcing:

• Total capital allocated to the buyback
• Duration (e.g. 6 months)
• Execution method (TWAP, VWAP, or discretionary)
• Whether purchased tokens are burned, locked, or returned to treasury
• Reporting cadence (monthly transparency reports)

Burning purchased tokens is the strongest signal because it permanently reduces supply. Returning them to treasury is weaker because the market knows those tokens could be sold again later.

Balance sheet diversification

Holding 95% of your treasury in your own token is not a strategy. It's a concentrated bet with correlated risk. If your project struggles, the token price drops, your treasury value drops, your ability to fund recovery drops. This is the death spiral that has killed dozens of projects.

A healthier treasury composition might look like:

Asset	Allocation	Purpose
Native token	40-60%	Ecosystem incentives, strategic deployments
Stablecoins (USDC/USDT)	25-40%	Operating expenses, market operations
ETH/BTC	5-15%	Diversification, gas reserves, strategic holdings
Fiat	5-10%	Legal, payroll, jurisdiction-specific expenses

The exact split depends on your stage, burn rate, and risk tolerance. The principle is: don't let your entire financial position depend on the price of the asset you're trying to build.

Diversification should happen gradually, using the liquidation strategies described above. A sudden announcement that "we're selling 30% of our token treasury for stablecoins" will panic the market. A quiet, consistent TWAP program that builds stablecoin reserves over 12 months is invisible.

Governance and transparency

For DAOs and community-governed projects, treasury management carries an additional layer of accountability. The community owns (or believes it owns) those tokens. Decisions about how they're deployed need to be transparent and, in many cases, subject to governance approval.

Reporting

Publish regular treasury reports. Monthly is ideal, quarterly is the minimum. Include:

• Current holdings (by asset, with USD values)
• Inflows (revenue, grants received, token unlocks)
• Outflows (operational expenses, grants distributed, tokens sold)
• Changes in strategy or policy
• Forward-looking plans for the next period

The format doesn't need to be complex. A simple table with commentary is sufficient. The discipline of regular reporting forces better decision-making and builds community trust.

Decision frameworks

Not every treasury decision needs a governance vote. Define thresholds:

• Routine operations (under $X or Y% of treasury): executed by the core team, reported after the fact
• Significant deployments ($X to $Y): proposed to governance with a review period, executed after approval
• Major strategic decisions (over $Y or structural changes): full governance proposal with community discussion

This prevents governance fatigue (voting on every $5K expense) while maintaining accountability for material decisions.

Multisig security

Your treasury multisig is the most security-critical piece of infrastructure in your project. Standard practices:

• Minimum 3 of 5 signers for any transaction
• Signers distributed across geographies and organisations
• Hardware wallets required for all signers
• Regular key rotation and signer review
• No single person should be able to approve a transaction alone

If your treasury is a 1-of-1 wallet controlled by the founder, you don't have a treasury. You have a personal account with a governance narrative.

Common treasury mistakes

No stablecoin reserves. The project holds 100% native tokens and needs to sell into every downturn to cover expenses, accelerating the decline.

Panic selling. Token price drops 50%, team panics, sells a large block at market, and creates additional sell pressure at the worst time. A defined liquidation strategy prevents emotional decisions.

Undisclosed OTC deals. The team sells large blocks of tokens OTC without telling the community. When the buyer's tokens unlock and hit the market, the community doesn't understand the sell pressure and trust erodes.

No budget. The treasury is treated as an unlimited resource without a defined annual or quarterly budget. Spending is reactive rather than planned, and runway estimates are perpetually optimistic.

Mixing treasury and market making. Using treasury tokens for market making without a clear framework creates confusion about whether sell activity is treasury liquidation or market making. Keep these operations separate and clearly defined.

Building a treasury function

Treasury management isn't a side project. For any token with meaningful treasury value, it should be a defined function with:

• A named responsible person or committee
• Written policies for liquidation, buybacks, and deployment
• Regular reporting cadence
• Defined risk limits (maximum single-day sell, minimum stablecoin reserve, etc.)
• Tools for tracking and analytics

This doesn't require a dedicated hire on day one. It requires taking the discipline seriously and not treating your treasury as a set-and-forget allocation in a tokenomics PDF.

The projects that survive multiple market cycles are the ones that manage their treasury like institutional capital, not like a community fundraiser.