Ethereum vs. Ethereum Classic

When Ethereum launched in July 2015, it arrived with a radically broader ambition than Bitcoin. It didn't just want to be digital money; it wanted to be a "world computer."

While Bitcoin was built as a highly secure digital ledger, Vitalik Buterin's 2013 whitepaper proposed something closer to a decentralized computing platform. Ethereum featured a built-in programming language capable of running arbitrary computations. The goal wasn't just to transfer value, but to build an entirely new foundation for applications where anyone could deploy custom tokens, decentralized insurance, and financial contracts directly onto the blockchain.

Much of the early community rallied around a simple creed: code is law. These applications, called smart contracts, would execute automatically across thousands of nodes. Ethereum promised applications resistant to downtime, censorship, and third-party interference.

That uncompromising promise was about to face its first catastrophic test.

By spring 2016, a project called The DAO emerged as a showcase for the world computer idea. Designed as a decentralized venture capital fund, it allowed anyone to send ETH in exchange for voting rights over future project funding. Its crowdsale raised roughly 11.5 million ETH, worth about $150 million at the time.

The scale was extraordinary. Roughly 14–15% of all ETH in circulation was now locked inside a single, experimental smart contract.

Then, on June 17, 2016, an attacker exploited a re-entrancy vulnerability in The DAO's code. In simple terms, the attacker could trigger another withdrawal before the contract updated its balance, repeating the process until approximately 3.6 million ETH, worth around $50–60 million, had been moved into a child DAO.

The Ethereum protocol itself hadn't been hacked. The attacker exploited a flaw in The DAO's code, and the blockchain kept processing transactions exactly as designed. The incident exposed a fundamental tension: if smart contracts were supposed to execute exactly as written, what would happen when the code produced an outcome the community considered unacceptable?

The attacker still faced one obstacle. The DAO's rules gave Ethereum a window of roughly four weeks.

Suddenly, a ticking clock hung over the entire Ethereum ecosystem. Panic spread, ETH's price fell sharply, and developers, miners, investors, and exchanges were thrown into frantic debate.

As the countdown approached zero, Ethereum faced an existential question:

If "code is law," what happens when the law allows a hacker to walk away with a fortune, and the network's credibility with it?

The Case for the Fork: ETH

• The spirit of the contract: The DAO was built to pool money for investment. The exploit was a bug, not the intended outcome. Recovering the funds, supporters argued, restored the contract's purpose rather than rewarding someone for exploiting its code.
• Protecting trust and the network: Ethereum was barely a year old. Roughly 15% of all ETH was locked in The DAO, and the attacker drained nearly a third of it, about 5% of the entire supply. Letting that stand could damage confidence and create serious systemic risk, particularly for a network planning to move toward Proof of Stake.
• Social consensus decides: A blockchain ultimately depends on people choosing which software to run. Miners, developers, and users could coordinate around the fork, making the chain with the strongest economic and social support the one that continued as Ethereum.

The Case for Keeping the Original Chain: ETC

• Code is law: Ethereum itself was never hacked. The network ran The DAO's code as written, and the exploit followed the rules of that contract. Changing the base layer to fix one application's bug, opponents argued, punished the part of the system that had worked and made finality depend on majority approval.
• A bailout with a threshold: Critics saw the fork as a bailout for The DAO's investors. If the network would not rewrite history for a small project's $1,000 loss, but would intervene when millions were at stake, what principle determines the threshold? For ETC supporters, that meant the rules were effectively negotiable when enough money or influential participants were involved.
• Principles over majority: The fork showed that developers, foundation members, miners, and other influential participants could coordinate to change the ledger. For ETC, this raised a fundamental question: does consensus mean following the rules, or following the majority?

The Philosophical Divide

• Ethereum: Consensus is the community's ability to coordinate and adapt the rules when the network's future is at stake.
• Ethereum Classic: Consensus means preserving the original rules, even at a short-term cost, because a ledger's long-term value depends on preserving the principles on which the chain was built.

The 28-Day Clock

The DAO's code gave Ethereum four weeks. Any ETH moved into a child DAO was locked for 28 days, so the attacker couldn't touch the 3.6 million ETH right away.

Plan A: Freeze It

Vitalik Buterin and other core developers proposed a soft fork that would blacklist the attacker's addresses. The funds would remain frozen without changing Ethereum's history.

Then the Flaw

Researchers, including Cornell's Emin Gün Sirer, found a problem: enforcing the blacklist meant miners had to check every transaction for links to the frozen funds. Because rejected transactions pay no fees, an attacker could flood the network with them at no cost, forcing miners to waste resources on spam and potentially bringing Ethereum to a halt.

Plan B: Move It

With the soft fork abandoned and the clock running down, Ethereum took the more radical option: a hard fork. Instead of freezing the stolen ETH, the new rules moved it, along with the rest of The DAO's funds, into a recovery contract, allowing the original DAO investors to withdraw their money.

But a hard fork requires more than code. It requires people to run it.

July 20, 2016: The Split

Most developers, exchanges, miners, and users upgraded. The new chain recovered the funds and continued as Ethereum.

A minority refused. They believed no amount of money justified rewriting the ledger. They kept mining the original chain, which survived as Ethereum Classic.

The DAO fork left Ethereum with two competing answers to the same question: should a decentralized network preserve its rules, or preserve the purpose those rules were meant to serve?

Five Twitter (X) posts from August 2016 through October 2017, showing how Ethereum Classic supporters argued that an immutable chain would outlast the one that reversed The DAO hack.

View post Apr 30, 2017

View post Oct 7, 2017

View post Sep 1, 2017

View post Jun 18, 2017

View post Aug 1, 2016

Monthly figures since ETC's fork (July 2016) through September 2026. Price and fees come from CoinMetrics' public dataset; developer activity is a first-party count of monthly unique commit authors across each chain's GitHub ecosystem (per Electric Capital's open taxonomy of which repos belong to which chain).

Parallels with ETC (Ethereum Classic): The Price of Principle

• Principle Over Consensus: Both communities chose a strict interpretation of their network's original promise, even when consensus allowed behavior they rejected. ETC refused the bailout of The DAO to preserve "code is law," while BTCB2 rejects what its proponents consider non-monetary uses of block space, including JPEGs and BRC-20 tokens, in pursuit of Bitcoin's peer-to-peer electronic cash function.
• Sacrificing Network Effects to Preserve the Principle: That choice comes at a steep cost. ETC became the minority chain after the fork, leaving it without Ethereum's dominant brand, ecosystem, and most of its hashrate. BTCB2 likewise positions itself as a minority fork, meaning it gives up the established "BTC" identity and must build its own liquidity, exchange support, and network effects. Separately, its switch from SHA-256 to BLAKE2b makes existing Bitcoin mining infrastructure incompatible with the new chain. For BTCB2, the break also extends to established Lightning channels and economic nodes built around the existing Bitcoin network.

Parallels with ETH (Ethereum): The Necessity of Intervention

• Intervention to Save the Network: Both communities decided that simply continuing under the existing rules would undermine the network they wanted to preserve. Ethereum intervened after The DAO hack, while BTCB2 intervenes to protect Bitcoin's block space from Ordinals activity and what its proponents describe as mining centralization.
• Rewriting the Rules: Both required a break from the existing protocol. Ethereum forked to reverse The DAO theft. BTCB2 restricts arbitrary data, changes the hashing algorithm, and imposes tighter block constraints.
• The Claim to Legitimacy: Neither side saw itself as the fork. Both framed their changes as necessary to preserve the network's original purpose, while arguing that the other side was the one departing from those principles.