Madison meets Satoshi

Auxiliary Precautions in Code:
Blockchain Governance for Sovereign Wealth Funds

Madison meets Satoshi

Return to Main Page
Section 6.1.1 — Mechanism Analysis

Immutable Transaction History

Bitcoin's permanent, tamper-proof record makes altering transaction history computationally infeasible. This page explores why immutability matters for sovereign governance by contrasting Bitcoin's absolute commitment to transaction finality with Ethereum's 2016 decision to reverse history.

"In framing a government which is to be administered by men over men, the great difficulty lies in this: you must first enable the government to control the governed; and in the next place oblige it to control itself."
— James Madison, Federalist No. 51 (1788)

Bitcoin

Code is Law. No Exceptions.

Core Philosophy

Rules apply equally to all participants. No transaction, however controversial, has ever been reversed by social consensus. The blockchain is a permanent record.

August 2010
Value Overflow Bug
184 billion BTC created
A bug allowed creation of 184 billion bitcoins. Fixed via soft fork that invalidated the specific transaction—but the fix required no social override, just code correction.
Code Fix Only
February 2014
Mt. Gox Collapse
850,000 BTC (~$450M)
The largest exchange collapse in Bitcoin history. Despite massive losses and clear evidence of theft, no proposal to reverse transactions was seriously considered. Victims pursued legal remedies.
No Reversal
August 2016
Bitfinex Hack
119,756 BTC (~$72M)
Major exchange hack. Bitcoin community did not consider a rollback. Instead, blockchain analysis eventually led to arrests in 2022—the immutable record became the evidence.
No Reversal
May 2022
Terra/Luna Collapse
$40+ billion market cap
Algorithmic stablecoin failure caused massive losses across crypto. Bitcoin transactions during the chaos remained final. No intervention proposed or possible.
No Reversal

Ethereum

Code is Law... Usually.

Core Philosophy

Smart contracts execute as written, but the community reserves the right to intervene in "extraordinary circumstances." Social consensus can override code.

June 2016
The DAO Hack
3.6M ETH (~$60M)
A vulnerability in The DAO smart contract was exploited. After contentious debate, Ethereum Foundation coordinated a hard fork to reverse the theft and return funds to investors.
Hard Fork Reversal
July 2016
Ethereum Classic Born
Chain Split
Those who opposed the reversal continued the original chain as "Ethereum Classic" (ETC), preserving the "immutable" version of history where the hack remained.
Community Split
November 2017
Parity Wallet Freeze
513,774 ETH (~$150M)
A bug permanently froze funds in Parity multisig wallets. Despite the precedent of The DAO fork, no reversal was implemented. "Extraordinary" proved harder to define twice.
No Reversal
August 2021
Poly Network Hack
$611M (cross-chain)
Largest DeFi hack. No fork proposed—the hacker returned most funds after being traced. The DAO precedent remained a one-time exception.
No Reversal

The DAO Fork: A Constitutional Crisis

Apr 30, 2016

The DAO Launches

A decentralized venture fund raises $150M in ETH—the largest crowdfunding in history. Investors receive tokens proportional to their contribution.

Jun 17, 2016

The Attack

An attacker exploits a "recursive call" vulnerability, draining 3.6M ETH (~$60M) into a "child DAO." The funds are locked for 27 days by the contract's own rules.

Jun 17-Jul 15

The Debate

Ethereum community splits: Some argue code executed as written and intervention would undermine trust. Others argue the clear intent was violated and intervention is justified.

Jul 20, 2016

The Hard Fork

Block 1,920,000: Ethereum implements an "irregular state change" returning DAO funds. ~85% of miners support the fork. The attacker's transactions are effectively erased.

Jul 20, 2016+

The Aftermath

Ethereum Classic continues the original chain. The precedent is set: Ethereum can reverse transactions if enough stakeholders agree. But this power has never been used again.

Criterion Bitcoin Ethereum
Transactions Reversed 0 1 (The DAO)
Immutability Guarantee Absolute Conditional
Governance Model No central authority Foundation-influenced
Chain Splits from Reversals None 1 (ETC/ETH)
Precedent for Intervention None exists Exists but unused since 2016

Through Madison's Lens

The DAO fork illustrates precisely the governance challenge Madison identified: the difficulty of constraining those in power from acting in their own interest, even when that interest aligns with popular sentiment.

Ethereum's founders and major stakeholders had significant holdings in The DAO. When given the choice between accepting a loss according to established rules or changing the rules to recover their funds, they chose the latter. The decision may have been economically rational and even popular—but it established that Ethereum's transaction history is subject to social override.

For a sovereign wealth fund, this distinction matters enormously. Bitcoin's immutability means that once a transaction is recorded, no future administration—however powerful—can alter the historical record. The blockchain serves as a permanent, neutral witness that constrains all parties equally.

This is Madison's "auxiliary precaution" made mathematical: a system where the rules bind everyone, including those who write them.

Implications for Sovereign Governance

🔒 Credible Commitment

Bitcoin's immutability allows sovereigns to make credible commitments that future governments cannot undo. A constitutional allocation to a fund can be verified forever.

⚖️ Equal Treatment

No participant—not even the protocol's creators—can reverse unfavorable outcomes. Rules apply equally to ministers and citizens alike.

📜 Historical Integrity

The complete, unalterable transaction history provides auditors, investigators, and citizens with a reliable record that cannot be doctored by those with access to power.

🛡️ Political Insulation

Emergency interventions—however well-intentioned—create precedents. Bitcoin's absolute immutability eliminates the political pressure to "make an exception just this once."