A company that stops has a procedure waiting for it: a liquidator is appointed, creditors are ranked, assets are sold, the entity is struck off a register. A DAO has none of that. There is no court with jurisdiction over a Snapshot space, no registrar to notify, and in most cases no legal person to dissolve. What a DAO has instead is the same instrument it has for everything else: a proposal. Winding down is therefore a governance action – and like every governance action, it only reaches as far as the contracts it can actually call.

That limit is the whole subject of this page. A dissolution vote can stop new spending and authorise a redemption. It cannot reach a position locked in someone else's contract, cannot un-delegate the voting weight the DAO accumulated elsewhere, and cannot make anyone keep paying for the forum where the vote was debated. The result is that a wound-down DAO does not disappear; it decomposes, in a predictable order, leaving parts of itself running for years.

The dissolution vote is a real proposal, and it is usually unanimous

The clean case looks like ordinary governance. Aura Finance, the vote aggregator built on top of Balancer's vote-escrow system, ended itself with AIP-78, “Orderly Protocol Wind-Down and Treasury Redemption for Aura”. It opened 9 April 2026 and closed on the 12th, carrying 17,171,688.83 vlAURA for, 0 against, 0 abstain, across eight voting addresses. It is the last proposal the aurafinance.eth space has ever recorded.

The shape recurs. Swapr, the DEX that outlived DXdao, shut its token down by the same route: “Shutdown SWPR token” opened 28 January 2025 and closed on 3 February with 4,935,266.20 for, 0 against, 0 abstain on 74 voters. Two dissolutions, two unanimous results, and not a single dissenting vote between them.

The unanimity is not consensus so much as self-selection. By the time a wind-down reaches a ballot, the holders who disagreed have usually already sold; the ones left are the ones who want the redemption processed. This is the mirror image of the pathology catalogued under voter apathy – a turnout collapse that helps the vote pass, because everyone still present wants the same thing. It also means the vote tally is close to worthless as evidence that a wind-down was well designed. Eight addresses agreeing is not a mandate; it is a quorum of the remaining interested parties.

The vote ends the organization; it does not unwind the positions

This is the part most wind-down write-ups miss, and it is checkable on-chain. Aura's entire product was a locked position: its VoterProxy contract 0xaF52695E1bB01A16D33D7194C28C42b10e0Dbec2 held Balancer LP tokens escrowed in veBAL. AIP-78 dissolved the protocol. It did not, and could not, break the lock.

Read against Ethereum mainnet at block 25,758,271 (15 August 2026), four months after the dissolution vote, the proxy still held 3,684,354.766 BPT locked in veBAL with locked__end = 29 April 2027, giving it a veBAL balance of 2,592,008.185 against a total supply of 3,573,920.103 – 72.53% of the entire vote-escrow electorate of a protocol it no longer participates in. Meanwhile the constituency that used to direct that bloc had evaporated: vlAURA outstanding stood at 332,317.70 against an 86,413,430.86 AURA supply, or 0.38%.

So Balancer inherited a governance problem it did not create: a supermajority of its escrowed voting weight belonging to a dead counterparty, immovable until 2027, and – critically – still counted in the denominator when measuring turnout. The DAO's answer is BIP-924, “Exclude Aura from Governance and Reduce Quorum”, filed 14 August 2026 and open to 18 August. Its remedy is two-part: overwrite the VoterProxy to zero voting power in the aggregator, and halve the quorum from 10,000,000 to 5,000,000 because the old bar was calibrated around a participant that no longer exists.

The two proposals immediately before it are the evidence for that arithmetic. BIP-922 and BIP-923 both closed 4 August 2026 unanimously – on eleven and ten voting addresses carrying 6,473,256.62 and 6,454,723.41 respectively, both short of the 10,000,000 quorum. BIP-924 itself, checked 16 August 2026, sits at 21,837,199.55 unanimous across five addresses, comfortably over the bar it proposes to lower. A DAO that cannot reach quorum has not lost its members; it has lost the one member who used to carry the quorum single-handed, which is the failure mode quorum design is least often stress-tested against.

The order of death: prose first, code and ledger last

A wound-down DAO decomposes in a consistent sequence, and knowing it tells a reader where to look for the truth months later. The parts that die first are the ones somebody has to keep paying a bill for.

• The forum and the docs go first. Checked 15 August 2026, neither forum.aura.finance nor docs.aura.finance had an A record at all. The forum thread is the discussion link on AIP-78 itself – so the deliberation behind the wind-down no longer answers at the address the vote points to. It survives only in the Wayback capture of 8 May 2026.
• The front end sometimes outlives them, because a redemption UI has a reason to stay up: app.aura.finance still served one at the same check.
• The code and the chain outlive everything. aurafinance/aura-contracts is MIT-licensed, unarchived, and was last pushed 13 May 2026 – a month after the protocol dissolved – and every governance fact above is intact on Snapshot and readable by eth_call.

DXdao makes the same point from the opposite direction, and adds a wrinkle worth internalising: a collective's domain is rented; its ENS name is not. DXdao's DNS-hosted forum, daotalk.org, today serves a gambling-affiliate site – and answers HTTP 200 while doing it. The DAOstack client it used, alchemy.daostack.io, has no DNS. But the site DXdao published to ENS and IPFS still serves, unchanged, years after the collective stopped: dxdao.eth.limo loads the original “The First Super-Scalable Collective” page today.

The practical rule for anyone citing a wound-down org: archive the forum thread before you cite it, prefer the Snapshot space and the contracts for anything load-bearing, and try <name>.eth.limo before concluding the web presence is gone. A live DNS domain is the least trustworthy artefact in the set, not the most – the same lesson tooling discontinuity teaches about the software a DAO runs on.

The record that disagrees with itself

A DAO that sunsets deliberately usually publishes a retrospective. What it rarely does is take down everything that contradicted it, and the result is a corpus that tells two incompatible stories depending on which page a reader lands on.

Coordinape is the cleanest specimen. Its memorial at coordinape.com is an honest, past-tense chronicle – it names the limits of the mechanism outright, and reports 50M+ GIVE allocated through circles, 500+ organizations at peak, and 64,000+ attestations on Base. Its own subpage for CoDAO, the $CO holder community named as steward of the IP, was never taken down: it remains frozen in pre-sunset future tense, still saying “Launch Coordinape” and describing a handover the memorial dates to the past. And the destination the memorial links to, codao.xyz, is now a 114-byte shell that redirects to a GoDaddy aftermarket listing – the steward DAO's own domain is for sale.

The generalisable probe is cheap: for any org you believe is closed, fetch every first-party host it cites and grep for future-tense roadmap verbs and live-app calls to action. A hit means the citation is anchored to an unmaintained artefact. First-party is an authority claim, never a freshness claim – a distinction that matters as much for a live project's support KB as for a dead one's landing page.

Death by attrition, dated on-chain

Most DAOs never hold a dissolution vote. They stop having proposals, and the secondary literature settles on an approximate obituary date that nobody checks. The ledger disagrees more often than not.

DAOstack is the standing example. Write-ups place its wind-down “around 2021”. Read via Blockscout and eth_call, the GEN token (0x543Ff227F64Aa17eA132Bf9886cAb5DB55DCAddf) still reports a total supply of exactly 60,000,000 across 7,251 holders, and the last proposal the GenesisProtocol mechanism ever processed was created on 17 January 2024 – nearly three years after the accepted date. Its record is a fitting epitaph: staked and boosted within a day, two votes cast in favour, and then no execution event at all. The organization it was raised for was DXdao's own avatar. The mechanism's last act was a proposal that passed nothing.

DXdao's own ledger tells the ending more bluntly than any post-mortem: of 148,976.876 DXD in existence, the single largest holder is the burn address, at 125,667.619 DXD or 84.35% of supply. The members redeemed and burned their way out one at a time; there was never a vote that said “we are finished”. This is the quiet death catalogued under how DAOs fail, and its distinguishing feature is that the treasury and the token keep existing long after the organization has stopped deciding anything.

What a wind-down owes its holders

The substance of an orderly dissolution is the redemption: a stated formula, a stated pool, and a window in which a holder can claim. Swapr's shutdown published all three – 515,000 ARB liquidated into roughly $360,000, distributed at about $0.015 per SWPR across 23,988,449 circulating tokens on two chains. A holder could compute their claim from the proposal itself.

What separates that from the alternatives is not generosity but legibility. Compare the three endings on this page:

Ending	Mechanism	What a holder could do
Aura	Dissolution vote authorising treasury redemption	Redeem through a front end kept alive for the purpose – but the underlying BAL stayed locked to April 2027
Swapr	Token-shutdown vote with a published per-token rate	Claim a computable share of a fixed pool
DXdao	No dissolution vote; per-member redemption and burn	Exit individually, whenever – and 84% of supply eventually did

The third row is the interesting one, because it is the only mechanism on the list that did not require the organization to still be functioning. A dissolution vote is a collective act that presupposes a quorum, a working forum and someone to execute the result; the further a DAO decays, the less able it is to perform the ceremony that would end it cleanly. That is the argument for building the exit into the contract rather than into the constitution – the position developed at length under rage quit and exit rights, and the reason treasury management and dissolution are really the same design question asked at different times.

A checklist for reading a wound-down DAO

1. Find the vote, or establish there wasn't one. Query the Snapshot space directly rather than trusting a date in an article; an absent dissolution proposal is itself the finding.
2. Date the death on-chain, not in the press. The last executed proposal, the last contract interaction, and the last token transfer are three different dates, and all three beat a secondary source.
3. Check what stayed locked. Escrowed positions, vesting contracts and delegated voting weight survive a dissolution vote and can distort a live DAO's governance for years, as Aura's veBAL bloc still does to Balancer's.
4. Distrust the live domain. A 200 response proves someone renewed a registration, not that the content is current – and it may prove someone else bought the name.
5. Archive before citing. The forum where the wind-down was debated is usually the first artefact to go, and it is usually the one the proposal links to.

How Caper approaches this

A caper has no dissolution procedure, because it has nothing to dissolve to. There is no wind-down among the five typed executive proposal kinds the contract recognises – PAYOUT, INVEST, DIVEST, VOTE and UPGRADE – and no function anywhere in the component that closes it, freezes it, or empties it. A caper cannot vote itself out of existence.

What it has instead is the redemption running continuously from genesis. Exit is a public method (exit(), contracts/logic/src/lib.rs:1973) that any member who has voted may call at any time: it takes their governance tokens and their soulbound vote tokens, computes their share as the same canonical weight that sized their vote, and pays it out of the treasury and the bonding-curve reserve. It requires no proposal, no quorum, no working forum and no counterparty – the three things a decayed DAO can no longer supply.

That inverts the sequencing problem this page describes. In a conventional DAO the exit is the last collective act, attempted at the moment the organization is least capable of collective action; in a caper it is a standing individual right that never depended on the organization being healthy. A caper does not end with a vote and a redemption window. It ends the way DXdao actually ended – one member at a time, whenever each decides – except that this is the designed path rather than the fallback after the designed one failed.

References

• Aura – AIP-78, “Orderly Protocol Wind-Down and Treasury Redemption for Aura” (Snapshot, April 2026)
• Balancer – BIP-924, “Exclude Aura from Governance and Reduce Quorum” (Snapshot, August 2026)
• Swapr – “Shutdown SWPR token” (Snapshot, January–February 2025)
• Aura governance forum – the AIP-78 discussion thread (Wayback capture, 8 May 2026)
• DXdao – the collective's ENS/IPFS site, still serving
• DAOstack – the GEN token contract
• aurafinance/aura-contracts – the contracts, outliving the protocol