Ethereum News
The DAO Hack and the Ethereum Split

The DAO raised a record US$150 million in ether during its 2016 crowd sale, setting a benchmark for decentralized fundraising. The project aimed to create an automated venture capital fund where investors could withdraw uncommitted funds at will. This structure allowed rapid depletion of treasury assets if safeguards failed. Researchers identified multiple security vulnerabilities before launch. The system relied on smart contracts that were immutable once deployed.
The Exploitation and Immediate Response
In June 2016, an unknown hacker exploited these flaws to steal approximately US$50 million worth of DAO tokens. The attack initiated a large withdrawal of funds from the original contract. The Ethereum community immediately debated whether to perform a contentious hard fork. A hard fork would alter the blockchain history to reverse the theft. Critics argued this violated the core principle that code is law. Supporters insisted that fixing the bug was necessary to protect user assets. The debate split the developer community along ideological lines regarding immutability.
On July 20, 2016, the Ethereum network executed the hard fork. This action reversed the hack and restored the stolen money to the original investors. The fork created two separate blockchains with distinct histories. One chain accepted the reversal and continued as Ethereum. The other chain rejected the change and kept the original transaction history. This second chain became known as Ethereum Classic. The split forced users and developers to choose which version of reality to support. The decision impacted wallet compatibility and exchange listings globally.
| Feature | Ethereum (ETH) | Ethereum Classic (ETC) |
|---|---|---|
| Hard Fork Status | Accepted reversal | Rejected reversal |
| Hack Outcome | Funds restored | Funds retained by attacker |
| Chain Continuity | Modified history | Original history preserved |
| Developer Support | Majority of foundation | Minority dissenters |
Technical Mechanics and Governance
Ethereum operates as a decentralized platform where smart contracts execute exactly as written. The DAO’s code contained a recursive call vulnerability that allowed infinite withdrawals. Smart contracts cannot be modified after deployment without consensus. This immutability protects against malicious changes but also prevents quick bug fixes. If a security hole exists, it remains open until a new contract is written. Users must migrate their funds to the new version manually. This process requires agreement among all stakeholders.
Vitalik Buterin proposed that Turing-complete platforms enable autonomous organizations. Ethereum met this threshold with its Virtual Machine. The DAO demonstrated both the potential and the risks of such systems. Investors trusted the code rather than a central authority. However, the code had a fatal flaw. The operational procedure allowed investors to withdraw any money not yet committed to a project. This feature enabled the rapid drain of funds during the attack. Safeguards aimed to prevent vote manipulation but failed to stop the direct exploit.
Legacy and Current State
The split established Ethereum Classic as a persistent alternative chain. It continues to operate on the original pre-fork history. Ethereum proceeded with upgrades like London in August 2021. The London upgrade introduced EIP-1559, which burns a portion of transaction fees. This mechanism reduces inflation and can make the asset deflationary. The original reward in 2015 was 5 ETH per block. It dropped to 3 ETH in late 2017 and then to 2 ETH in early 2019. These changes adjusted the issuance rate for network security.
The legal status of DAOs remains unclear in many jurisdictions. Wyoming recognized them as legal entities in July 2021. Other states like Vermont and the Virgin Islands have similar laws. The DAO incident highlighted the need for robust code auditing. It showed that trust in code does not equal safety. Developers now prioritize security reviews before deployment. The event proved that even sophisticated systems can fail under pressure. It also revealed that community consensus can override technical rules. Whether future forks will follow this precedent remains an open question.