On July 20, 2016, at block 1,920,000, the Ethereum network executed a hard fork to reverse The DAO hack. However, not everyone followed. A portion of the community chose to continue mining and using the original, unaltered chain. This chain became known as Ethereum Classic.
The Fork Moment
When the forked Ethereum chain began processing blocks that altered The DAO's state, nodes running unpatched software continued on the original chain. Rather than being abandoned, this chain found support from those who believed in blockchain immutability.
Why Continue the Original Chain?
Supporters of the original chain argued:
Immutability Matters
If transactions can be reversed when enough people disagree with the outcome, the blockchain loses its fundamental trustworthiness as a neutral ledger.
Precedent Concerns
Allowing one hard fork to reverse a hack could set a precedent for future interventions, potentially enabling censorship or favoritism.
Code is Law
Smart contracts should execute exactly as written. Users interact with code, and the code's behavior is the "agreement" - not external interpretations of intent.
Early Challenges
Ethereum Classic faced significant challenges in its early days:
- Most developers followed the forked chain
- Infrastructure had to be rebuilt
- The network had to establish its own identity
Community Forms
Despite challenges, a dedicated community formed around ETC. Supporters included:
- Advocates of blockchain immutability
- Those concerned about centralized decision-making
- Developers who valued the original Ethereum vision
Moving Forward
From this moment, Ethereum Classic established itself as an independent blockchain project. While maintaining EVM compatibility, ETC charted its own course based on the principles of immutability, decentralization, and censorship resistance.
The chain that launched on July 30, 2015, continues unbroken on Ethereum Classic.