Hard Fork

How hard forks differ from soft forks

The key distinction:

• Soft fork — backward-compatible. New rules are stricter; non-upgraded nodes still accept new blocks. No chain split.
• Hard fork — backward-incompatible. Old nodes reject new blocks. If both rule sets have ongoing support, two chains result.

Most major protocol upgrades are technically hard forks — including planned, uncontroversial ones where everyone upgrades together and no chain split actually occurs.

Routine vs. contentious

Two categories:

• Routine hard forks — scheduled protocol upgrades with broad community support. Everyone upgrades; no chain split. Ethereum has had many of these (Byzantium, Constantinople, Istanbul, London, Paris (the Merge), Shanghai, Cancun, Pectra). Bitcoin has had fewer, with SegWit and Taproot being notable but technically activated as soft forks.
• Contentious hard forks — community disagreements produce two surviving chains. Examples: Bitcoin Cash (2017), Ethereum Classic (2016).

The infrastructure to handle hard forks — exchanges adding support for both chains, wallets handling both, etc. — has matured significantly since the early years.

Famous contentious hard forks

• Ethereum / Ethereum Classic (July 2016) — after the DAO hack drained $50M+, the Ethereum community voted to fork the chain to reverse the theft. Most miners and users moved to the new chain (now called Ethereum); a minority kept the original chain (Ethereum Classic). Ethereum proper became dominant; ETC persists as a much smaller alternative.
• Bitcoin Cash (August 2017) — proponents of larger Bitcoin block sizes (8MB initially, later 32MB) split off. Bitcoin Cash itself later split again into Bitcoin SV (2018) over similar disagreements.
• Bitcoin Gold (October 2017) — forked Bitcoin to use a different mining algorithm, theoretically more decentralized but practically less secure.

What happens to assets

In a contentious hard fork:

• Holders typically receive equal balances on both chains. Someone holding 10 BTC at the moment of the Bitcoin Cash fork received 10 BTC on the original chain plus 10 BCH on the new chain.
• Each chain operates independently after the fork. Subsequent transactions on one don't affect the other.
• Replay attacks — an issue if both chains accept identical transaction formats. Modern forks usually include "replay protection" via chain identifiers.

For exchanges and custodians, supporting forks is operationally complex. Some support both; others only the dominant chain. Users with assets on unsupported chains can lose access entirely.

Why forks happen

A few drivers:

• Protocol upgrades — most common; new features require code changes.
• Disagreements — community can't reach consensus on direction.
• Emergency response — Ethereum's DAO fork was a one-time exception to "code is law."
• Failed coordination — sometimes a planned soft fork doesn't activate cleanly and produces an unintended split.

Hard forks and the "immutability" debate

Ethereum's DAO fork remains philosophically controversial. The community decided to retroactively change the chain's history to undo a theft. Critics argue this violates immutability. Defenders argue it was extraordinary action warranting extraordinary measures.

Ethereum Classic exists as the chain where the fork didn't happen. Its market value is far smaller than Ethereum's, suggesting the market broadly accepted the Ethereum decision.

The bigger picture: even Bitcoin's "immutability" is socially enforced. If sufficient stakeholders agreed to fork Bitcoin to undo something, they could. The fact that they don't is a social and economic property, not a purely technical one.

How hard forks proceed

A typical contentious hard-fork timeline:

1. Disagreement — community splits over a proposed change.
2. Code release — one or both factions release client software implementing their preferred version.
3. Activation block — the chain splits at a defined block height.
4. Replay protection deployment — to prevent transactions valid on both chains.
5. Exchange support — exchanges decide whether to support both chains and how to credit user balances.
6. Network stabilization — both chains continue operating, with their own miners/validators, communities, and value.

In a non-contentious hard fork, this process is much smoother — basically a coordinated upgrade that everyone follows.

Trends

Modern crypto sees fewer contentious hard forks than the 2016-2017 era. Most chains have settled into governance models (DAOs, foundations, formal upgrade processes) that handle disagreements through other channels. Hard forks remain a tool of last resort for protocol disputes; in practice, they're rare for established chains.

Ethereum's continued upgrades happen through hard forks but are entirely uncontentious; the community moves together. Bitcoin's deliberately conservative approach produces few changes, with both Bitcoin Cash and SV splitting off years ago and not having serious additional fork pressure since.