A bootstrap budget is the money a DAO spends before it is able to decide anything. Someone has to pay for the legal entity, the first contributors, the audits and the infrastructure, and that spending starts before there is a functioning vote to authorise it – so in practice a foundation, a development company or an elected transition body sets the first budget, and the DAO's first budget vote is held afterwards. What that vote is actually deciding varies, and the difference is worth naming: it can be a genuine appropriation, a renegotiation of terms, or a ratification of transfers that already happened.

This is the mirror image of council dissolution. Both are moments where authority sits with a body the token holders did not elect through the DAO's own process – at the start because the process does not exist yet, at the end because it is being wound down. Both are also where the gap between formal governance rights and actual control over funds is widest.

Why the first budget is never the first vote

Three constraints push the budget ahead of the vote, and none of them is avoidable by better intentions.

• The entity precedes the treasury. A DAO cannot hold a bank account, sign an employment contract or pay an auditor until some legal wrapper exists, and forming that wrapper costs money. The first spend is therefore always pre-governance by construction.
• Launch spending is front-loaded and time-boxed. Audits, listings, market making and legal opinions cluster around the launch date, when the voter base is newest and turnout is least reliable.
• The people writing the budget are the only people who know it. At launch the operating detail – headcount, vendor contracts, runway – lives entirely with the founding team. A token holder voting on it in week one is voting on a document they cannot audit.

The consequence is that the DAO's leverage over its own first budget is much narrower than its formal voting rights suggest. It rarely gets to decide whether the money is spent. It gets to decide what conditions attach to the remainder.

Ratification after the fact: Arbitrum, 2023

The clearest worked example is Arbitrum DAO's first proposal. AIP-1 was put up in March 2023 as an omnibus that, among other things, asked token holders to ratify the Arbitrum Foundation's setup – including an "Administrative Budget Wallet" already holding 7.5% of the ARB supply. Delegates read it as being asked to approve a transfer that had already occurred, and voted it down: the Snapshot record closes at 100,343,537 against to 16,418,340 for, with 14,120,336 abstaining across 26,141 voting addresses – roughly 77% against.

What happened next is the part worth studying, because it shows exactly what the rejection did and did not achieve. A follow-up proposal asked the Foundation to return 700M ARB to the DAO treasury outright. That also failed, and by a wider margin: 118,334,390 against to 20,526,942 for across 43,392 addresses, about 84% against. The same electorate that refused to bless the allocation also refused to claw it back.

What passed was the renegotiation. AIP-1.1 disclosed that 0.5% of supply had already been transferred out of the budget wallet, put the remaining 7% (700M ARB) under a four-year linear lockup running from the date of the Snapshot approval – about 175M ARB unlocking per year – and published a first-year operating budget of $36M, split $16M general and administrative, $9M R&D, $5M technical infrastructure and $6M events, marketing and communications, to be funded 50% in USD and 50% in ARB. It carried 137,012,025 for to 1,224,386 against across 45,230 addresses, roughly 98% in favour. A companion governance proposal, AIP-1.2, passed with a similar margin.

Read the four votes as a sequence and the pattern is unambiguous. Ratification failed, reversal failed, and terms-plus-disclosure passed overwhelmingly. The DAO's real instrument was never the yes/no on the allocation. It was the lockup schedule, the reporting requirement, and the itemised budget it could measure the next request against.

Appropriated in advance, and still not fixed: Uniswap, 2022–2023

Uniswap did it the other way round. The Uniswap Foundation was put to a temperature check in August 2022 and its funding approved by the DAO before it began operating – $74M in total, split roughly $52.3M in grants and $21.7M in operations, sized to run through the end of 2024. An ex ante appropriation, which is the textbook answer to the Arbitrum problem.

It still did not produce a fixed budget, for a reason specific to DAOs: the request was denominated in the DAO's own token. The first tranche was written as 2,547,002 UNI targeting $20M, and by the time it settled on 25 August 2022 UNI had fallen 13.7% to $7.05, so the Foundation received $17.3M rather than $20M. A year later it returned to ask for the remainder, $62.37M – the $56.7M outstanding plus a 10% buffer against exactly that volatility – and that request went to an on-chain vote in October 2023.

The lesson generalises past this one case. A budget voted in the DAO's own token is a budget whose real size is set by the market between the vote and the transfer, and the correction is always another vote. That is one of the mechanical reasons a DAO holding only its own token has less budgetary control than its balance sheet implies – the reason treasury diversification is a governance question and not just a portfolio one.

When the treasury arrives after the entity: Radix, 2026

A third shape is currently playing out at Radix, and it inverts the ordering again: here the bootstrap grant is explicitly small, and the treasury transfer is conditional on the DAO existing first. The Radix Foundation announced in 2026 that it approved a two-stage grant of $67,000 and 10m XRD to fund the DAO's set-up and initial operation, with the community-elected Accountability Council leading the entity formation, and stated that "when a community entity is established, the intention is for the remaining treasury to transfer to it, subject to the legal and compliance steps any such transfer requires."

Sequenced that way, the pre-governance spend is a rounding error against the treasury it precedes, which removes the Arbitrum-style ratification problem almost entirely. It creates a different one. Until the transfer completes, the DAO governs a set-up grant while the assets it was formed to steward sit with the outgoing body, and the transfer itself is gated on legal steps no vote controls. A DAO in that position has full formal authority over almost none of its eventual balance sheet, which is a live risk rather than a settled arrangement – and one worth re-checking against the primary source rather than assuming, since a stalled transfer looks identical to a pending one right up until it doesn't complete.

What the DAO actually retains

Across all three shapes the token holders' effective levers are the same short list, and none of them is the headline vote.

• The unlock schedule. Converting an outright allocation into a linear release is the single change that reliably survives contact with a hostile electorate, because it costs the recipient nothing today and it is enforceable without trust.
• Itemisation, at a granularity that can be checked later. A budget published as four line items is a budget the next request can be measured against. A budget approved as one number is not.
• Tranching. The next tranche is the only reliable point of leverage, which is why splitting a multi-year budget into dated requests matters more than the total.
• Denomination. Whether the budget is expressed in the DAO's token or in stable value determines who carries the price risk between the vote and the transfer.
• Reporting obligations. The cheapest thing to win in a bootstrap negotiation and the most useful later, since it is what makes operating costs comparable across periods at all.

What the DAO generally cannot recover is money already moved. Arbitrum's electorate tried and declined by a larger margin than the original rejection. Treating the first budget as reversible is the mistake; treating it as the last unconditional grant the founding body will receive is the accurate reading.

How Caper approaches this

A caper has no pre-governance phase to budget for, because it has no launch to fund. The treasury fills from the bonding curve as people buy, from the first buy onward, so there is never an interval in which money has been raised but governance is not yet running – and there is no founding allocation to ratify later, because the founder is compensated by the per-buy skim, which never enters the treasury at all. See raising funds for how capital actually arrives.

The practical effect is that every outflow from a caper's treasury is a proposal, from the first one. There is no unconditional first tranche and nothing that got spent before the vote existed – which removes this particular failure mode rather than managing it, at the cost of not being able to spend anything before there is a community to authorise it.

References

• AIP-1: Arbitrum Improvement Proposal Framework – forum.arbitrum.foundation, March 2023. The omnibus that asked for ratification of the Administrative Budget Wallet.
• AIP-1 Snapshot record – the closing tally: 16,418,340 for, 100,343,537 against, 14,120,336 abstain, 26,141 voting addresses.
• Proposal: Return 700M $ARB to the DAO Treasury and its Snapshot record – the clawback attempt, 118,334,390 against to 20,526,942 for.
• Proposal: AIP-1.1 – Lockup, Budget, Transparency – the 0.5%-already-transferred disclosure, the four-year linear lockup on the remaining 7%, and the itemised $36M first-year budget. Snapshot record: 137,012,025 for to 1,224,386 against.
• AIP-1.2 – Foundation and DAO Governance – Snapshot record, 137,606,930 for to 280,122 against.
• [Temperature Check] Create the Uniswap Foundation – August 2022, the first of the two checks preceding the funding vote.
• [RFC]: Complete initial funding of the Uniswap Foundation – gov.uniswap.org, September 2023. The $74M approval, the 2,547,002 UNI first tranche that delivered $17.3M, and the $62.37M remainder request. Taken to a vote as [Governance Proposal].
• Foundation Update: Moving to Maintenance Mode – radixdlt.com, 2026. The two-stage $67,000 and 10m XRD set-up grant, and the treasury transfer conditioned on a community entity existing.