The DAO Hack of 2016: How It Split Ethereum in Two
An Ambitious Experiment
In 2016, a project called ‘The DAO’ (Decentralized Autonomous Organization) launched on the Ethereum blockchain as one of the most ambitious experiments the crypto space had seen: a venture-fund-like entity governed entirely by code and token-holder votes, with no traditional company structure behind it. It raised the equivalent of well over $100 million worth of Ether at the time, making it one of the largest crowdfunding events in history up to that point.
The Vulnerability
The DAO’s code contained a flaw in how it handled withdrawal requests, which allowed an attacker to repeatedly withdraw funds before the smart contract could update its internal balance record — a type of exploit now widely known as a ‘re-entrancy attack.’ Using this flaw, an attacker drained a substantial portion of The DAO’s funds — roughly a third of the total raised — into a separate account.
The Decision That Followed
The Ethereum community faced an unprecedented question: should the network’s history be altered to reverse the theft, or should the core principle that blockchain transactions are immutable be upheld, even at significant financial cost to victims? After intense debate, the majority of the community supported a ‘hard fork’ — a coordinated software change that effectively rewound the affected transactions and returned the stolen funds to their original owners.
The Split: Ethereum and Ethereum Classic
Not everyone agreed with this approach. A minority of the community held that altering the blockchain’s history — even to undo a theft — violated the core promise of immutability that makes blockchains trustworthy in the first place. This group continued running the original, unaltered chain, which became known as Ethereum Classic (ETC). The chain that implemented the fork became what is known today simply as Ethereum (ETH) — now one of the largest cryptocurrency networks in the world.
| The forked chain | The unaltered chain | |
|---|---|---|
| What it did | Rewound the affected transactions | Kept running the history as recorded |
| The principle it put first | Returning the funds to the people who lost them | A history no majority can rewrite |
| What it accepted as the cost | An intervention in a record meant to be final | Leaving the losses where they fell |
| What it is called today | Ethereum | Ethereum Classic |
Why This Event Still Matters
The DAO hack remains one of the most cited case studies in blockchain governance, because it forced the industry to confront a genuine philosophical tension: is a blockchain’s history truly unchangeable no matter what, or can — and should — a community intervene when something goes catastrophically wrong? There’s no universally agreed answer, and the Ethereum/Ethereum Classic split stands as a live example of a community reaching two different conclusions.
Lessons for Smart Contract Security
Beyond the governance debate, the technical vulnerability itself — re-entrancy — became one of the most studied bug classes in smart contract development, directly shaping how developers write and audit contract code today. Many of the security practices standard in blockchain development now exist specifically because of lessons learned from this incident.
Related Reading
For another foundational case study in crypto history, this time centered on exchange custody rather than smart contract security, see The Mt. Gox Collapse, and for a broader look at the technology underlying events like this one, see What Is Blockchain? A Beginner’s Guide.
