"Exit with Anger": Resistance and Freedom in DAOs
TechFlow Selected TechFlow Selected
"Exit with Anger": Resistance and Freedom in DAOs
The primary use of "rage quit" is as a protective mechanism for members in donation/investment-type DAOs.
Navigating Web3 tides with focused insightsAuthor: Wang Chao
"Rage Quit" in the DAO space, often abbreviated as "ragequit," was once a relatively niche concept. As DAOs have evolved, more and more are facing forks, founder departures, or even liquidations—making the term "Rage Quit" increasingly common in media coverage.
However, there's a widespread misunderstanding about what "Rage Quit" actually means—even some international professional media outlets frequently misuse it.
Origin
At the 2019 Ethereum Denver Conference, Ameen Soleimani and his team launched Moloch v1—a protocol designed for creating donation-based DAOs. Compared to complex DAO operating systems like Aragon, Moloch v1’s core consists of just over 400 lines of code. It is simple, elegant, easy to understand and use, enabling people to pool funds and collectively manage their usage efficiently.
In DAO governance, minority opinions are inevitable. Decisions typically follow the principle of “majority rules.” But this poses risks: when the majority gains control, they might abuse their power and harm minority interests. To mitigate this risk, the Moloch protocol introduced the concept of “Rage Quit.”
How to “Rage Quit”?
When a member opposes a proposal, even if they vote against it, the proposal may still pass. In the Moloch protocol, there is a seven-day grace period between when a proposal passes and when it executes. During this window, members who voted “no” can choose to “rage quit” if they don’t want their funds used for the approved project—allowing them to reclaim their remaining share from the contract before execution.
“Rage quitting” isn't possible at any time. Here are its key characteristics:
-
“Rage Quit” is enforced by smart contract code.
-
Only members who voted against the previous proposal are eligible to rage quit.
-
“Rage Quit” can only occur during the grace period after a proposal has passed but before it is executed.
-
Members can only withdraw their remaining proportional share from the contract.
(For example, if someone initially contributed 100 ETH and 30% of the treasury has already been spent, they can only withdraw 70 ETH.)
There’s also an implicit prerequisite: members must have made direct, traceable contributions to the DAO treasury. Only then can their remaining equity be fairly verified at the code level to enable withdrawal. In other words, if a member never contributed funds to the DAO treasury, “Rage Quit” simply doesn’t apply—even if the function exists in code, it cannot be executed.
An interesting tidbit: in Moloch v1, in pursuit of simplicity and security, “rage quit” was the *only* way to extract funds from the protocol. This meant grantees had to perform a “rage quit” to access their funding—even if they weren’t angry or planning to leave.
Evolution
Moloch v1 achieved notable success, but its functionality was limited to coordinating donations, restricting its scope. As a result, multiple teams iterated on Moloch v1 to launch Moloch v2, adding features that enabled collective investing and opened up broader commercial applications.
With improved contracts and compliance frameworks, Moloch v2 sparked a wave of Investment DAOs. The LAO, Flamingo, and MetaCartel emerged as leaders, with later iterations even spawning Investment DAOs dedicated to funding other Investment DAOs. Today, Investment DAOs are a significant force in the Web3 investment landscape, with many extending into traditional venture domains—backing standout projects like Stability AI.
Getting back to Rage Quit: Investment DAOs built on Moloch v2 and its variants naturally support “rage quitting,” though the situation is far more complex than before. V1 was a donation protocol—once funds were donated, they were gone; exiting members couldn’t reclaim spent money, so “rage quit” could simply return unspent balances. But v2 handles investments—spent funds become equity or tokenized assets awaiting returns. These assets can’t be invalidated just because someone rage quits. Hence, historical equity tracking and splitting become necessary. From v2 onward, “rage quit” became significantly more complex in both code and implementation, with variations across different protocols. While specifics vary, it’s enough to grasp the general evolution.
In summary, the primary purpose of “Rage Quit” is to serve as a protective mechanism for members within donation- or investment-type DAOs. Its core function allows members to burn their shares in the DAO and reclaim their proportional share of remaining treasury funds.
Daily exits driven by anger aren’t “Rage Quits”
For most DAOs, their structure and operations do not meet the basic conditions required for “Rage Quit” to function. Many DAO members haven’t directly funded the treasury, meaning membership isn’t tied to treasury balance—making the applicability of “Rage Quit” extremely limited.
It’s easy to understand: consider a company. If an employee resigns out of dissatisfaction, even if they hold stock options or shares, they aren’t entitled to withdraw company cash upon leaving. Similarly, if a shareholder buys茅台 stock and later discovers the company starts making chocolate liqueurs, they may be furious and decide to exit—but they can only sell their shares on the market; they cannot return the shares to茅台and demand a proportional payout of corporate cash.
We’ve seen founders propose “Rage Quit” in DAOs. But such cases are largely symbolic—just using the name—with outcomes usually resulting from negotiation. Unless a founder’s stake has a clearly defined link to treasury funds, they have no right to extract money upon exit.
Nouns DAO is an exception. It underwent a fork, and the new contract introduced “Rage Quit” functionality. Its mechanism roughly aligns with the original concept, albeit with adjusted execution details. Nouns DAO can do this mainly because it operates more like a donation-based DAO: every Noun auction generates direct, traceable inflows to the treasury. Spent funds are treated as donations toward ecosystem development—without being tied to individual member claims—making “Rage Quit” feasible.
Final Thoughts
Since both “rage” and “quit” are common words in everyday language, combining them leads people to interpret “Rage Quit” literally. And although the Moloch protocol pioneered the concept, it never formally defined it as a technical term. This ambiguity allowed “Rage Quit” to evolve and be interpreted in various—and sometimes incorrect—ways. This evolution reflects the interplay between technology and culture. Every innovation, every misinterpretation, drives deeper thinking and improvement in the DAO space. Today’s understanding of “Rage Quit” is no longer identical to its original form—it’s a dynamic, evolving institutional innovation.
As a decentralized organizational model, DAOs are still in their early stages. Each challenge they face guides us toward defining how future digital societies might operate. “Rage Quit” stands as a pivotal milestone in this journey—not merely lines of code or a feature, but a symbol of our ongoing exploration of freedom, fairness, and collective rights.
Join TechFlow official community to stay tuned
Telegram:https://t.me/TechFlowDaily
X (Twitter):https://x.com/TechFlowPost
X (Twitter) EN:https://x.com/BlockFlow_News
