Daohaus ragequit burns membership tokens for a proportional withdrawal from the main treasury

Daohaus ragequit lets a member burn shares, loot, or both to withdraw a proportional amount of eligible main treasury assets. In the Safe-based Moloch v3 design, shares carry voting and financial rights; loot carries financial rights without votes. Before a first withdrawal, identify the main Safe, the assets included in the exit, and the membership balance you intend to surrender. Sidecar balances sit outside that claim. A smaller burn leaves some membership intact, while a successful burn permanently consumes the selected units. The payout follows treasury balances and total membership supply when the transaction executes.

Last updated · October 19th, 2026

In a v3 ragequit, the token list determines which assets the burned membership units redeem.

The main treasury sets the boundary of your exit

One Safe is the ragequittable main treasury in a Moloch v3 DAO; additional sidecar Safes hold assets outside members' exit rights. The Safes view marks the main treasury with a ragequittable badge. A combined view of organizational assets can therefore exceed the balances available through ragequit. The treasury address identifies the account that supplies eligible assets for an exit on the DAO's network.

Settings lists the governance, treasury, voting token, and non-voting token contracts. These records connect the membership balance to the correct Safe. A matching token name elsewhere does not establish ownership in this DAO or a claim against its treasury.

Can I burn only part of my shares or loot?

V3 accepts separate burn amounts for shares and loot, so an exit can use part of either balance. Choosing shares spends voting tokens as well as financial weight. Choosing loot spends financial weight while leaving the share balance intact. Each burn amount must fit the initiating member account's holdings. The rights attached to any remaining tokens continue with that remaining balance.

Choosing a smaller amount makes the exit smaller; it does not make the completed burn reversible.

Each selected asset uses the same ownership fraction

In Safe-based v3, the withdrawal fraction equals the combined shares and loot burned divided by their combined supply before burning. That supply covers all holders. The contract multiplies each selected treasury asset's balance by this fraction. Integer division rounds down when the result includes a fraction of the asset's smallest unit. This calculation produces an amount of each asset. It does not calculate a cash value or return the member's original contribution.

Treasury spending can lower a payout, while deposits can raise it. Changes to membership supply also change the denominator. Those inputs come from the chain when the withdrawal executes. A displayed estimate can therefore change before inclusion, even when the burn amounts remain the same.

The asset list determines what this burn claims

Safe-based v3 takes an explicit asset list, which determines the balances that a particular burn redeems. The contract processes those assets within the withdrawal transaction. Omitting an asset leaves it in the treasury, with no saved entitlement attached to the units already burned. Remaining shares or loot carry the future claim that their remaining proportion provides. Token selection therefore matters even for a partial exit, especially when the intention is to redeem a share of every compatible treasury asset.

Withdrawal interfaces differ across Baal implementations. Some use a default guild-token list and a separate advancedRagequit call for selected tokens. The Safe-based implementation accepts the asset list directly in ragequit and handles native coin separately from ERC-20 transfers. These signatures describe different contract layouts, so the deployed implementation determines the required inputs.

Open full-size image

Proposal grace periods define time before execution

A proposal's grace period delays processing after voting ends, giving objecting members time to exit before that proposal executes. Its duration comes from the DAO's governance settings. A passing vote therefore does not immediately move the funds. An intended exit before a treasury transfer depends on the proposal's grace end and execution state. If the transfer executes first, the withdrawal uses the changed treasury balance. Governance can change configured timing, so a duration used by another DAO does not determine this window.

Member exits can also prevent proposal execution when the combined supply of shares and loot falls below the required retention level. That condition compares remaining combined shares and loot with a supply reference recorded for the proposal.

Token calls and recipient behavior can prevent completion

An incompatible or malicious token can make its balance unreadable or cause its transfer to fail. The withdrawal also relies on the main Safe's module permissions. If a required asset transfer reverts, the v3 transaction also rolls back its membership-token burn. A contract recipient that rejects a native-coin payment can prevent completion too. Excluding a troublesome token changes the payout covered by that burn, so it requires a new decision about the exit.

Completed burns leave transaction and balance records

A successful v3 withdrawal emits a Ragequit event identifying the member, recipient, burn amounts, and selected tokens. Membership reductions and treasury transfers establish what the exit changed. The event identifies the selected assets; it does not specify every transferred amount. An asset whose calculated payout rounds to zero produces no transfer. A successful transaction therefore needs interpretation alongside its asset movements, especially if an intended token was absent from the list.