DAO Treasury Management on Arc

DAOs controlled more than $26 billion in on-chain treasuries in early 2026, and most of it is a single asset: the DAO's own governance token, typically 60–90% of holdings. That concentration — not hacks, not bad votes — is the structural risk in DAO finance, and it shapes every other decision: what to hold in stablecoins, who can move funds, and how to keep a treasury vote from becoming a theft. This page covers the practice as it stands and what a dollar-native chain like Arc changes about the operational layer.

What does a DAO treasury actually look like?

Large and lopsided. Industry trackers in 2026 put the aggregate above $26 billion, with the biggest — Uniswap, Sky (MakerDAO), Optimism, Arbitrum, Lido — each in the billions and the top five holding a majority of the total. Composition figures vary by source but agree on the shape: roughly two-thirds in the DAO's native token, under a fifth in stablecoins, the remainder in ETH and other crypto, with traditional assets a rounding error. The native-token share is the problem hiding in plain sight — it's the asset most correlated with the DAO's own failure, least liquid in a crisis, and most tempting to count as "treasury" at a market price the treasury could never realize by selling. The 20–40% held in stablecoins and ETH is the part that's actually managed; the rest is a balance-sheet illusion until diversified.

How should a DAO structure custody and control?

Around a multisig with a policy layer, because pure token voting is too slow and too capturable to run day-to-day finance. Safe is the dominant multisig; the standard setup is a hardware-backed signer set with a threshold of at least half and never all-of-all (the Safe setup on Arc). Above it sits governance tooling — proposal and delegate platforms for the votes that authorize spending, off-chain signaling for temperature checks — and increasingly policy modules that let the community set rules (spending limits, whitelisted destinations, roles) that a smaller operating group executes within. Non-custodial treasury managers — kpk (formerly Karpatkey) runs treasuries for Balancer and the ENS endowment on this model — execute strategy under permissions the DAO grants and can revoke, which is the institutional pattern arriving on-chain. Vesting for contributors and grants runs through schedule tools (the platform comparison), keeping unvested tokens in contracts rather than in the operating multisig.

What goes wrong?

Three recurring failures. Concentration: a treasury that's 80% native token can't fund a two-year runway through a drawdown without selling into its own weakness — the reason mature DAOs hold 18–36 months of expenses in stablecoins and treat the native token as reserve, not cash. Governance attacks: in July 2026 an attacker bought about $4 million of BonkDAO's token, won a treasury vote with 99.9% of a handful of voting wallets, and drained roughly $20 million — a direct descendant of Beanstalk's 2022 flash-loan governance attack and the Compound "Golden Boys" episode of 2024. Low participation plus a treasury the vote can move is the attack surface; timelocks, quorum floors, and separating vote authority from execution keys are the defenses. Operational drag: 30-day governance cycles for routine payments, off-ramp complexity, and unclear legal wrappers slow everything a treasury does — which is where the chain underneath starts to matter.

What does Arc change?

The operational layer, concretely — not the governance problem, which is chain-agnostic. Dollar-native accounting: on Arc the treasury's stablecoin reserve, its gas, and its payments are all USDC, so runway math has no gas-token line and no conversion step (corporate USDC operations). Cheap, instant execution: multisig transactions cost cents and finalize in under a second, so a DAO can pay fifty contributors monthly through a multisender run without a fee discussion, and a policy module can enforce small-payment limits without gas making small payments irrational. Verifiable commitments: contributor vesting and any locked reserves sit in contracts anyone can audit on Arcscan (the trust stack), which matters for DAOs whose legitimacy is transparency. What Arc doesn't change: a treasury that's 80% native token is 80% native token on any chain, and a vote that can move the treasury can be bought on any chain. Fix those with structure; use the chain for what it's good at.

What's the practical checklist?

Hold runway in stablecoins — commonly 18–36 months of committed expenses — and treat native token as reserve. Put custody behind a hardware-backed multisig with a sane threshold; put spending policy in modules a smaller group executes within; put the authority to change either behind a timelock the community can see. Vest contributors on-chain rather than paying lump sums. Diversify reserve assets deliberately, with a mandate the DAO voted on, rather than by drift. Publish the treasury's composition and policies — a DAO's transparency is its only moat against the "who controls this money" question. And run distributions where they're cheap and final: on Arc, a monthly payroll cycle is a single flat-fee run (treasury operations).

FAQ

How much of a DAO treasury should be in stablecoins? Common practice is 18–36 months of committed expenses. Most DAOs hold far less — under a fifth of treasury on average — with the balance in their own token.

What is a governance attack? Acquiring enough voting power, cheaply, to pass a proposal that moves treasury funds to the attacker — BonkDAO lost about $20 million this way in July 2026. Timelocks, quorum floors and execution separate from votes are the defenses.

Which tools do DAOs use for treasury management? Safe for custody; proposal and delegate platforms for governance; policy modules for spending controls; non-custodial managers such as kpk for strategy; vesting tools for contributors.

Can a DAO run its treasury on Arc? Yes — Safe contracts are deployed on Arc, gas is USDC at cents, and Team Finance's vesting, locks and multisender are live. Check Safe{Wallet}'s network list for app-level support status.

Does holding treasury in USDC carry risk? Issuer and regulatory risk rather than market risk — Circle's reserves, attestations and licenses are the diligence items (is USDC safe). It's a different risk than holding your own token, which is the point.