Holdings
What sits in the Chamber treasury and how to verify it onchain
The Chamber protocol treasury holds the DAO's accumulated revenue plus direct holdings allocated by governance. It sits onchain, multisig-controlled, and is fully visible.
Live view
The canonical source — total balance, composition, per-asset holdings, and per-protocol positions — is the Analytics page:
Treat it as the source of truth. Figures drift with market prices and ongoing inflows, and the app always reflects the live state.
What's in there
The treasury's composition reflects how Chamber earns. Because every fee is paid in vault shares, the treasury accumulates shares in every fee-earning vault across the protocol, alongside whatever the DAO chooses to hold directly.
Broadly, holdings fall into three categories:
Vault shares — 10% of every vault fee (entry, exit, performance, management) is minted to the DAO as vault shares. The treasury holds shares across the platform's fee-earning vaults.
Stablecoins — realised revenue redeemed from vault shares, plus assets held for operations and grant payouts.
Volatile assets — BTC, ETH, and a smaller allocation of alt exposure, held directly or through yield-earning positions.
The Analytics page splits this into App Holdings (positions inside Chamber vaults and partner protocols) and Token Holdings (direct token balances).
Revenue concentration
Worth being explicit: revenue is concentrated. A large share of fee flow currently comes from Toros Finance vaults, with the remainder from market-making and yield-farming vaults. Depositor-driven retail flow is a smaller slice than it looks from the front page.
This matters for how the DAO thinks about treasury sustainability — a large drop in any one vault's AUM would move revenue noticeably. Buyback and grant programs are sized against this, not against an assumed steady flow. See Revenue and buybacks.
Verifying onchain
Every transaction into and out of the treasury is visible onchain. Multisig addresses and per-chain treasury contracts are documented alongside the deployment addresses; follow the addresses directly from the Analytics page.
Last updated