In June 2016, a single line of buggy code drained tens of millions of dollars from what was, at the time, the largest crowdfunded project in history. The DAO wasn't just another failed startup — it was a live stress test of Ethereum's biggest promise, and it nearly broke the network before it ever really got going.

The story of The DAO is the story of crypto learning to walk. It's about code is law, the limits of that idea, and the messy human decisions that followed when an unstoppable program did exactly what it was told to do.

What Was The DAO?

The DAO — short for Decentralized Autonomous Organization — was launched on April 30, 2016, as a venture capital fund with no managers, no executives, and no board of directors. Built as a set of smart contracts on Ethereum, it was designed to let token holders vote on which projects deserved funding. Anyone could submit a proposal, and anyone holding DAO tokens could vote on it.

The pitch was seductive. Investors didn't have to trust a fund manager, a CEO, or even a lawyer. They just had to trust the code. Within weeks of launch, The DAO raised roughly $150 million worth of Ether from over 11,000 contributors, making it the most successful crowdfund in history at that point.

For a brief, glittering moment, The DAO felt like the future. It was a glimpse of borderless, leaderless capital allocation, and it put Ethereum on the map as more than just a platform for token sales.

The Code Behind the Curtain

The DAO's smart contracts were written in Solidity, Ethereum's programming language, and were audited before launch. Multiple security firms reviewed the code. Yet the most damaging flaw was hiding in plain sight.

The Recursive Call Vulnerability

The bug lived in the split function — the mechanism that allowed investors to exit the fund by separating their Ether into a child DAO. A recursive call exploit let an attacker request multiple withdrawals from the same balance before the contract could update its ledger.

  • Step 1: The attacker called the split function.
  • Step 2: The contract sent Ether to a child DAO.
  • Step 3: Before the balance updated, the function was called again — repeatedly.
  • Step 4: The contract kept sending funds, draining itself dry.

It wasn't a hack in the traditional sense. The attacker didn't bypass any security. They simply did exactly what the code allowed them to do, over and over.

The Hack of June 2016

On June 17, 2016, an unknown actor began exploiting the recursive call vulnerability. Within hours, roughly 3.6 million Ether — worth around $50–60 million at the time — had been siphoned into a child DAO controlled by the attacker. At then-prevailing prices, it was the largest theft in crypto history. At the peak of later bull cycles, those same tokens would be worth billions.

The Ethereum community watched in disbelief. The attacker left a message in the blockchain essentially saying: this is legal, your code said I could, so I'm taking it. And technically, they weren't wrong.

Prices crashed. Panic spread. And the crypto world faced an uncomfortable question: if the code is the law, and the law was broken, what do you do?

The Aftermath and the Ethereum Split

The Ethereum Foundation, developers, and community members faced a brutal choice. Option one was to do nothing and let the attacker keep the funds — staying true to the principle that blockchain transactions are irreversible. Option two was to roll back the chain through a hard fork, essentially rewriting history to return the stolen Ether.

After weeks of heated debate, a hard fork was implemented in July 2016. The chain that rolled back the theft became today's Ethereum. The original, unaltered chain — where the hack still stands — lives on as Ethereum Classic.

The split was more than technical. It was philosophical. Ethereum chose pragmatism over purity. Ethereum Classic chose immutability over intervention. Both communities still argue they were right.

The DAO attacker never cashed out, largely because the stolen funds sat in a child DAO with a 28-day lockup — and the forked chain made the original tokens nearly worthless. To this day, the identity of the hacker remains unconfirmed.

Key Takeaways

The DAO was a turning point — for Ethereum, for smart contract security, and for how the entire industry thinks about decentralized governance.

  • Code is law, until it isn't. The DAO proved that perfect code is impossible, and communities sometimes have to pick up the pieces.
  • Smart contracts need real audits. Modern standards, formal verification, and bug bounties exist largely because lessons learned in 2016 cost investors real money.
  • Immutability is a feature and a curse. The Ethereum fork showed that even the most censorship-resistant chains depend on humans when things go wrong.
  • The DAO still matters. Every modern DAO — from MakerDAO to Uniswap governance — owes its existence, and its caution, to what happened in June 2016.

The DAO didn't kill Ethereum. It forged it.