How to Audit Your Web3 Treasury Health in 10 Minutes

You don't need a full monthly report to know whether your treasury is healthy. You need five answers, and you can pull them in ten minutes from public sources. Run this diagnostic on the first of every month — it's the lightweight cousin of a full investor report, and it'll catch problems before they require a deck.

1. What's the stablecoin floor?

Open your treasury wallet on Etherscan (or whatever explorer matches the chain). Sum up USDC, USDT, DAI, USDS, and any other major stables. Divide that number by your trailing three-month operating burn. The result is your stablecoin-only runway in months. If it's under six, you have a market-independent runway problem. Native-token price could go to zero tomorrow and this is the only number you control.

2. What's the native-token concentration?

Take the value of your project's own token sitting in the treasury (token count × current price) and divide by the total treasury value. If it's above 70%, your reported runway is fragile — a 50% price drop on your native asset rewrites your runway story in a single weekend. This is the single most underdiscussed risk on monthly investor calls, and the easiest one to spot with five clicks.

3. Where's the last 30 days of outflow going?

Open the last 30 days of outgoing transactions. Look at the top three by value. Categorise them in your head — payroll, infra, marketing, grants, partner payments, treasury rebalance. If you can't tell from on-chain data alone what the largest outflow was for, that's the single most useful piece of investor copy you'll write all month: explain it before they ask.

4. Is engineering output keeping pace with burn?

Open your main GitHub org. Sort repos by recent activity. Glance at commits-per-week and merged-PRs-per-week across the top five repos. If those have been flat or declining for three months while burn is steady, you have a productivity-per-dollar problem that investors will eventually ask about. The reverse — engineering output rising while burn is flat — is the single best signal you can put in front of your cap table.

5. What changed materially this month?

Write one sentence. Not a paragraph — one sentence. "Treasury rebalanced from native to stables: $1.5M." "Lead engineer joined from Optimism." "V2 contracts deployed to mainnet, $4M TVL within 48 hours." If you can't come up with a one-sentence material change, the month wasn't material — that's also useful information for your cap table, and worth communicating cleanly rather than padding with filler.

The point of the diagnostic

If you do this on the first of every month, you'll know which of your investor reports needs proactive explanation and which is routine. The teams that get caught flat-footed by an investor question almost always failed to ask the question of themselves first. Ten minutes, five answers, no spreadsheet.

Vault Brief automates the data-collection half of this diagnostic — balances, flows, category breakdowns, and GitHub signals are pre-filled on the first of each month. You're left with the one-sentence material change, which is the part only you can write.

Get these metrics in every report automatically

Vault Brief generates investor-ready reports from your on-chain data. No spreadsheets.