Custody, execution, and transparency
Because no individual may unilaterally move the funds, a treasury is held either in an m-of-n multisig – most commonly a Safe – or directly in a governance contract that releases assets only on a passed vote. Spending follows the DAO's governance process: a proposal names the recipient and amount, the membership votes, and an approved transfer executes on-chain. Frameworks such as Aragon bundle treasury permissions, voting, and payments together; analytics platforms such as Dune and Boardroom give members a public, real-time view of what the treasury holds and how it is being spent – the size, composition, and runway figures that feed a DAO's overall health metrics.
That radical transparency – every balance and every disbursement visible on-chain – is both a DAO treasury's greatest accountability advantage and a standing invitation to governance attackers. Because the DAO and the recipient of a transfer read the same on-chain record of it, neither keeps a private version to reconcile against the other's, which is the property Ian Grigg designed triple-entry accounting to provide; the invoices, expense categories and statutory accounts around a transfer are still kept off-chain. Large treasuries increasingly delegate day-to-day allocation to a non-custodial manager such as karpatkey, granted scoped permissions over a DAO-owned Safe via the Zodiac Roles Modifier – it can deploy funds into pre-approved strategies but can never withdraw them to itself.
That arrangement is one instance of a broader pattern: authority the DAO grants once and does not re-vote, bounded by scope, magnitude, direction and a cooldown rather than by a ballot. Standing authorizations and delegated mandates reads four production examples at contract source and sets out which bounds they share and which they omit.
Custody is often split on purpose. A DAO with separate budgets, such as payroll, grants, rewards and reserves, may hold each in its own account with its own signers, which makes the treasury harder to read as one balance sheet. Aragon's Linked Accounts, released in March 2026, join such accounts into one organisation view without merging them (Aragon). Two accounts link only when each acknowledges the other on-chain, which stops an outsider attaching itself to a DAO's page. No new contract is deployed, each account keeps its own executor and permissions, and linking gives neither account any control over the other. The app sums balances across linked accounts and offers a proposal only the actions its account is permitted to take.
On Radix the multisig is part of the account itself rather than a separate contract such as a Safe. The Radix DAO's first treasury account is a native account whose owner rule requires two of three signature badges, and in August 2026 it held 200 $XRD and the master badge of the Consultation app the DAO votes through; the share of its runway to hold in $XRD rather than stablecoins had not been decided. radix.wiki tracks the decision on its custody card.