Finite-Weight Principles
Hold principles seriously without granting them infinite weight
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 70%
Buterin's reading of the DAO fork is not that principles were abandoned but that they were revealed to have finite weight. Input is a crisis where a stated principle produces an unacceptable outcome; the process is threefold. First, break the principle explicitly and frame the break as a moral statement — that you can believe in principles without assigning them infinite weight — rather than pretending no principle existed. Second, accept that the exception creates a precedent risk, since many people expected that violating immutability once would make it open season. Third, and this is the load-bearing move, deliberately pass on the next comparable opportunity to set a counter-precedent: a year later a bug in the Parity multisig wallet caused a massive loss of funds and the community valued not fixing it. Output is a community that has proven both that it will act in extremis and that it will not act casually. Buterin also separates the decision from its handling — he does not regret the decision, but names the social environment where opposing the fork made you evil as his least proud moment.
Origin
Extracted from Naval — Vitalik Buterin's retrospective on the 2016 DAO hard fork, the Ethereum Classic split, and the decision a year later not to rescue the Parity multisig wallet.
Core principles
- 01A principle with infinite weight will eventually meet a scenario that breaks it.
- 02Purists who commit to never compromising end up in a worse rhetorical position when they do.
- 03Declaring the finite weight in advance is cheaper than discovering it under pressure.
- 04A deliberate refusal to intervene afterwards is what stops one exception becoming open season.
- 05Even a correct decision is a failure if the process makes dissenters feel evil for dissenting.
How to run it
- 1
Declare finite weight before the crisis
State early and transparently that your principles carry great weight but not infinite weight. Doing this in calm conditions costs almost nothing; doing it mid-crisis reads as rationalisation.
Pro tip Name the class of scenario that would justify an exception, not the exception itself.
Watch out Committing too hard to never compromising leaves your rhetorical posture badly damaged when reality forces the compromise anyway.
- 2
Establish that this case is genuinely exceptional
Show why the situation is unlike the ordinary case. The DAO was unusual in magnitude and, unusually, was even fixable — in most hacks the attacker gets the money instantly and there is no way to reverse it even if you want to.
Pro tip Fixability is itself part of the exceptionality test; if you could not have fixed a similar past case, say so.
Watch out If you cannot articulate what makes this case different, you are not making an exception, you are changing the rule.
- 3
Make the break as a stated moral position
Frame the action as a deliberate statement about moderation rather than as an emergency improvisation. The point being made is that moderation between purism and expediency is itself a value.
Pro tip Write the reasoning down at the time — the record is what later distinguishes principle from convenience.
- 4
Protect the dissenters through the process
Actively prevent an environment where opposing the decision marks someone as evil or as siding with an attacker. Buterin identifies this social environment, not the fork itself, as the thing he is least proud of.
Pro tip Give the strongest opposing case a formal, visible platform run by someone who actually holds it.
Watch out People who feel their opinion was disrespected leave permanently, and some treat the episode as a watershed that redefines the whole project for them.
- 5
Set the counter-precedent at the next opportunity
Find the next comparable case and deliberately decline to intervene, saying explicitly that you are declining in order to establish that the exception was an exception. Ethereum did this by not fixing the Parity wallet loss a year later.
Pro tip The counter-precedent is most convincing when declining is genuinely costly to sympathetic victims.
Watch out Without this step, the prediction that one violation makes it open season becomes self-fulfilling.
- 6
Hold the line afterwards
Sustain the new norm over years so the record itself becomes the argument. Buterin notes there has been no comparable violation of immutability since, which is what many people did not expect.
Pro tip Point at elapsed time and at the specific cases you declined; both are stronger evidence than restated intent.
In the wild
Less than a year into Ethereum's history, a large application called the DAO was hacked and a big portion of all the ETH was stuck in it; without action the attacker would have extracted it after a couple of months. A change to the protocol rules was made to bail out the application's users. The community split, with Ethereum Classic refusing the fork on principle. A year later a bug in the Parity multisig wallet caused a massive loss of funds and the community chose not to fix it, explicitly to set the counter-precedent that immutability is taken seriously.
→ One acknowledged exception followed by a deliberate refusal, and no comparable violation of immutability since — against widespread predictions of open season.
A widely used library promises never to break its public API. A security flaw appears that cannot be fixed compatibly. Rather than quietly shipping the break or refusing on principle, the maintainers publish a note stating that compatibility is a heavily weighted commitment, not an absolute one, and explain the specific magnitude test this case passes. Six months later a smaller ergonomic wart that many users want removed is deliberately left in place, with the maintainers saying openly that they are leaving it to prove the earlier break was exceptional.
→ The security fix ships without the promise collapsing, and the visible refusal afterwards restores confidence in the compatibility guarantee.
Common mistakes
Assigning principles infinite weight
Purists eventually meet a scenario extreme enough that they have to compromise anyway, and having committed too hard to never compromising leaves their position far worse than honest moderation would have.
Skipping the counter-precedent
An exception with no subsequent visible refusal validates the fear that one breach opens the door to many. The refusal has to be public and costly to count.
Winning the decision, losing the dissenters
Letting a social environment form where opposing the decision means you are pro-hacker turns a governance choice into a permanent exodus, independently of whether the choice was right.
Is it for you?
Best for
Founders and stewards of communities whose legitimacy rests on stated principles — protocols, open-source projects, member-owned institutions.
Not ideal for
Domains where the principle is a hard external constraint such as law, safety regulation or fiduciary duty, where discretion is not yours to exercise.
From the transcript
“you can believe in principles without assigning those principles infinite amount of weight”
“most people that try to take a more purist approach end up hitting a scenario that is extreme enough that you have to compromise”
“people valued not fixing the parity wallet a year later in order to set the counter precedent”
From the episode
Vitalik: Ethereum, Part 2