The historical molochdao.com domain appears to no longer serve official Moloch documentation as of 2026-05-10 UTC and instead resolves to unrelated Cambodia casino content. I excluded it as a trustworthy primary source and relied on the official GitHub repositories and handbook materials instead.
Key takeaways from primary sources
Moloch’s core value is not feature breadth but constrained design. The v1 docs explicitly describe the system as a minimally viable DAO built to reduce smart-contract risk and support collective funding of Ethereum public goods.
The signature mechanism is ragequit: members can burn their non-transferable shares and withdraw a pro-rata treasury claim instead of remaining trapped under an objectionable majority decision.
Proposal ordering plus the grace period is what gives ragequit teeth. Members have a defined exit window after voting but before proposal processing.
The v1 documentation is unusually explicit about the game theory: ragequit is meant to protect against majority overreach, especially dilution attacks where a coalition could try to mint itself excessive new shares.
Shares are governance and treasury claims at once. They are non-transferable, confer voting rights, and can be redeemed for treasury assets, which means membership is intentionally bound to exit economics.
The v2 materials show how the Moloch pattern generalized from single-token public-goods grants into multi-asset DAOs with tribute tokens, payment tokens, whitelist proposals, guild-kick proposals, and loot-based non-voting ownership.
The later handbook keeps the same analytical core: Moloch was popularized because of minimalism and ragequit, not because it tried to solve every DAO workflow.
Specific source signals worth retaining
v1_contracts/README.md: strongest source on original purpose, proposal flow, grace period, proposal deposit, and explicit anti-51%-attack / anti-dilution reasoning.
Root README.md: clearest source on v2 extensions such as multi-token treasury support, loot, guild kick, and collaborative standardization with other DAO groups.
Whitepaper link in the v1 README: historical canonical reference for philosophy and mechanism framing.
Handbook README: concise later-era statement that Moloch’s enduring importance comes from minimum-viable design and ragequit.
Why this entry belongs in the corpus
MolochDAO belongs because it is one of the cleanest reusable governance primitives in crypto: treasury pooling with credible minority exit.
It is especially useful next to Safe, Hats, Commons Stack, and Grant Ships because it clarifies a different axis of governance design — not permission granularity or allocator workflows, but whether dissenters can leave with assets before disputed decisions are imposed.
The reusable insight is that many later DAO systems quietly inherit, weaken, or route around the Moloch question: when a coalition wins, what credible exit or anti-dilution protection does the minority actually have?