CoinYQ
Protocol Wars & Forks4 min readEthereum (ETH)

Block 1,920,000: The 28-Day DAO Hack That Shattered 'Code is Law' and Birthed Ethereum Classic

In June 2016, a hacker exploited a vulnerability in , draining 3.6 million ETH (14% of all Ethereum). Trapped by a 28-day contract countdown, developers and cypherpunks clashed in a historic ideological war between algorithmic immutability and ecosystem survival—culminating in the at Block 1,920,000 and the permanent birth of Ethereum Classic.

Block 1,920,000: The 28-Day DAO Hack That Shattered 'Code is Law' and Birthed Ethereum Classic

3-Minute Fast Briefing

  • The ParadoxOn June 17, 2016, an attacker exploited a flaw in 's split function, siphoning 3.6 million ETH—roughly 14% of the entire circulating Ethereum supply.
  • The Turning PointA built-in 28-day withdrawal lock on child prevented the attacker from cashing out immediately, giving the global Ethereum community a dramatic four-week window to debate an unprecedented rollback.
  • The LegacyAt Block 1,920,000 on July 20, 2016, Ethereum executed a historic to refund victims, but cypherpunk purists who defended 'Code is Law' preserved the original ledger, creating Ethereum Classic (ETC).

Chronological Timeline

May 2016The DAO Crowdfunding Triumph

Raises over 12 million ETH ($150 million), establishing the largest crowdfunding campaign in financial history.

June 17, 2016Reentrancy Exploit Strikes

Attacker drains 3.6 million ETH into a Dark by exploiting the split function's state-update lag.

June–July 2016The 28-Day Clock & Whitehat Rescue

While funds are locked by the contract delay, the Robin Hood Group rescues 7 million remaining ETH as fork debates rage.

July 20, 2016Block 1,920,000 Hard Fork

EIP-779 redirects all balances into a recovery Withdraw contract, launching the new ETH chain.

August 2016Ethereum Classic Declaration

Unforked node operators and miners maintain the original unaltered chain, declaring independence as ETC.

1. The $150 Million Autonomous Experiment and the Hidden Crack

In the spring of 2016, the nascent Ethereum ecosystem was buzzing with euphoria over (Decentralized Autonomous Organization). Spearheaded by the Slock.it team, it was pitched as the world's first decentralized venture fund—governed entirely by immutable without corporate boards, managers, or intermediaries.

Within 28 days, enthusiastic crypto investors poured in over 12 million ETH—representing an astonishing 14% to 15% of the entire circulating Ethereum supply at the time, worth over $150 million. Vitalik Buterin's young network had suddenly graduated from an academic playground into the custodian of massive institutional capital.

Yet underneath the fanfare lurked a fatal flaw in the Solidity code. Hidden within the splitDAO function, designed to let dissenting investors exit the fund, lay a sequencing trap that would test the philosophical foundations of Web3.

2. The Endless Loop: The Reentrancy Trap

In the early hours of June 17, 2016, automated monitors picked up massive, continuous withdrawals from contract. The attacker had not cracked cryptographic keys or broken consensus; they had exploited the execution order of the .

When processing a withdrawal, the contract sent Ether to the recipient's address before decrementing the user's internal token balance. The attacker programmed an address with a malicious fallback function that immediately invoked splitDAO again the microsecond it received Ether. Because the balance was never zeroed out, the contract repeatedly executed the transfer in an infinite recursive loop.

The attack is a vulnerability, where an attacker called the 'split' function, and then calls the split function recursively inside of the split before the internal state balance is decremented.
Vitalik Buterin (Ethereum Foundation Blog, June 17, 2016)

Within hours, 3.6 million ETH (roughly $50 million then, billions today) was siphoned into the attacker's 'Dark '. Ethereum's market price plummeted by over 50%, and the community descended into sheer pandemonium.

3. The 28-Day Clock and the Whitehat Robin Hoods

A peculiar architectural constraint turned what could have been an instant liquidation into a tense four-week thriller. Because the attacker's Dark inherited 's original contract rules, any funds inside it were subjected to a mandatory 28-day creation and voting window before they could be withdrawn to external wallets.

The hacker held 3.6 million ETH, but was completely powerless to spend or move it for 28 days. This gave the global Ethereum community a crucial breathing window.

A clandestine squad of core developers—dubbed the Robin Hood Group (including Alex van de Sande and Griff Green)—sprang into action. Using the exact same exploit against the remaining funds, they drained over 7 million ETH into a secure whitehat-controlled , saving nearly 70% of investor capital from the attacker's grasp.

4. 'Code is Law' vs. 'Ecosystem Survival': The War of Ideologies

As the 28-day countdown ticked toward zero, the blockchain world erupted into an unprecedented philosophical civil war. The question was existential: Should Ethereum modify state history to rescue the funds?

Vitalik Buterin and the Ethereum Foundation favored an irregular state change—a to redirect the stolen funds into a dedicated recovery contract called WithdrawDAO. They argued that letting a single malicious actor hold 15% of the total network supply would permanently cripple Ethereum's security and destroy user trust.

The is a delicate topic and the way we see it, no decision is the right one.
Jeffrey Wilcke (Ethereum Foundation Co-Founder)

On the other side, cypherpunk purists and Bitcoin maximalists vehemently objected. To them, 'Code is Law' was the sacrosanct foundation of decentralized blockchains. If developers could arbitrarily rewrite the ledger whenever influential investors lost money, Ethereum would be no better than a central bank bailing out corrupt institutions.

5. Block 1,920,000 and the Permanent Genesis of Ethereum Classic

On July 20, 2016, Ethereum reached Block 1,920,000. Core developers activated EIP-779, executing an irregular state transition that swept all exploited balances into WithdrawDAO, allowing token holders to redeem their ETH 1:1. The succeeded, and the vast majority of hash power moved to the new chain.

However, the old chain refused to die. A steadfast group of miners and ideological purists continued mining the non-forked chain, defending the unaltered immutable ledger. Days later, crypto exchange Poloniex listed the original chain as Ethereum Classic (ETC), giving it instant market value and liquidity.

hack remains the most formative crisis in history. Technically, it established the 'Checks-Effects-Interactions' pattern as the golden standard of Solidity security. Philosophically, it proved that blockchains are ultimately human socio-economic networks, forever balancing mathematical immutability against community governance.

Key Takeaways for Investors & Builders

Engineering / Product

Checks-Effects-Interactions Security Pattern

hack permanently codified the rule that must update internal balances and states before making any external calls.

Market / Investor

Chain Splits, Liquidity & Replay Hazards

Contentious s fragment liquidity, brand equity, and developer tooling while introducing critical cross-chain replay attack risks.

Philosophy / Governance

The Threshold Between Code and Social Consensus

A blockchain's ultimate rule is not just its virtual machine code, but the human social consensus that governs when catastrophic failure warrants state intervention.

Connected Lore & Universe

Connected Stories in this Universe

Explore the chain reaction of historical breakthroughs, blunders, and legends.

Sources & References

  1. [1]Source 1: The DAO Smart Contract Source Code (DAO.sol)Slock.it / blockchainsllc GitHub Archive · 2016-04-28Accessed 2026-08-20
  2. [2]Source 2: CRITICAL UPDATE Re: DAO Vulnerability AnalysisEthereum Foundation Blog · 2016-06-17Accessed 2026-08-20
  3. [3]Source 3: To Fork or Not to Fork: Philosophical & Technical AssessmentEthereum Foundation Blog · 2016-07-15Accessed 2026-08-20
  4. [4]Source 4: EIP-779: Hardfork Meta — DAO Recovery SpecificationEthereum Improvement Proposals · 2017-11-26Accessed 2026-08-20
  5. [5]Source 5: The Ethereum Classic Declaration of IndependenceEthereum Classic Community · 2016-08-13Accessed 2026-08-20