Summary: MolochDAO is best understood not as a full-featured DAO suite, but as a deliberately minimal governance and treasury primitive built around one core protection: members can irreversibly burn their non-transferable shares to exit with a pro-rata claim on the treasury before an objectionable proposal takes effect. Its reusable mechanism is the coupling of proposal ordering, a grace period, and the ragequit exit option, which turns “leave with your share” into a governance backstop against majority abuse, dilution attacks, and forced coordination under disputed spending decisions. That makes MolochDAO a foundational comparison class for later DAO frameworks, grant guilds, venture DAOs, and any system that claims to decentralize treasury control while quietly depending on credible exit rights.
What it does:
Uses non-transferable shares to represent membership and voting rights in a shared treasury
Lets members sponsor proposals for new members, grants, token whitelists, and in v2 guild-kick actions
Forces proposals through ordered voting and then a grace period before processing
Lets dissenting or non-participating members ragequit during the relevant window to withdraw their proportional claim on treasury assets
In v1, focuses on pooled ETH grants for Ethereum public goods; in v2, extends the treasury to multiple ERC-20 assets and more proposal types
Preserves an intentionally small feature surface so governance assurances come more from constrained design than from rich permissions systems
Key claims:
The original v1 documentation explicitly frames Moloch as a grant-making DAO and a “radical experiment in voluntary incentive alignment” for funding public Ethereum infrastructure that teams underfund individually
The most important analytical contribution is ragequit. Members who disagree strongly with a proposal can exit with their share of treasury assets during the grace period instead of relying on constitutional promises or minority-vote protections
The v1 docs make the anti-51%-attack logic unusually explicit: if a majority tries to pass a self-dealing dilution proposal, minority members can ragequit before processing and remove their share of the treasury, blunting the theft
Proposal ordering matters because votes are processed sequentially; governance in Moloch is not just about yes/no outcomes, but about queue position and the time available for dissenters to leave
Shares are intentionally non-transferable. That keeps governance tied to participation and treasury risk rather than making membership a freely tradable governance wrapper
The v2 materials show how the mechanism generalizes beyond grants: tribute token, payment token, loot, whitelist, and guild-kick features turn Moloch into a reusable multi-asset DAO framework while keeping the minimal governance skeleton intact
The later handbook still emphasizes simplicity, security, usability, extensibility, and ragequit, which is good evidence that the durable legacy of Moloch is its governance primitive rather than any particular deployment brand
Whitepaper: The v1 docs point to a canonical Moloch whitepaper PDF in the original GitHub org. See ../whitepapers/molochdao-primary-sources-2026-05-10.md for the reviewed source chain and source-quality note about the historical domain.
MolochDAO is the minimal ragequit baseline. Stronger governance notes can compare back to it without this note trying to enumerate the whole DAO branch.