Hard Fork in Crypto

A hard fork is a permanent, backward-incompatible change to a blockchain's protocol rules. Nodes that do not upgrade to the new software can no longer validate blocks produced under the updated rules and are effectively cut off from the upgraded chain. If enough nodes and miners reject the change and continue running the old software, the result is a permanent chain split, creating two separate blockchains that share a common history up to the fork point but diverge completely afterward.

Think of a hard fork like revising the rulebook of a sport so fundamentally that the old teams refuse to adopt the new rules and start their own league using the original ones.

Why Hard Forks Happen

Hard forks are initiated for three primary reasons: security fixes that require breaking backward compatibility, network upgrades that improve performance or functionality, and governance disputes where the community cannot reach consensus on the protocol's direction.

Security-driven hard forks are typically uncontroversial. When a critical vulnerability requires changes that old nodes cannot handle, the community upgrades quickly and in unison. Controversy enters when hard forks are driven by governance disagreements, which produce contentious splits that divide communities, liquidity, and developer talent.

The Bitcoin Cash Fork: The Most Studied Example

Bitcoin's most significant hard fork occurred on August 1, 2017, when Bitcoin Cash (BCH) split from Bitcoin (BTC). The disagreement centered on block size. Bitcoin's block limit of 1 megabyte constrained transaction throughput and was driving up fees. One faction wanted to increase the block size to allow more transactions per block. The other argued that larger blocks would centralize the network by making it impractical for individuals to run full nodes.

The result was a permanent split. Anyone who held Bitcoin at block height 478,558 received an equal amount of Bitcoin Cash on the new chain. Both chains continued independently, with Bitcoin maintaining the majority of hash rate, market value, and developer activity.

Ethereum and the DAO Fork

Ethereum's most consequential hard fork came in July 2016, following the hack of the DAO, a decentralized autonomous organization built on Ethereum. The hacker exploited a reentrancy vulnerability and drained approximately 3.6 million Ether, worth around $60 million at the time. The Ethereum Foundation and a majority of the community proposed a hard fork to reverse the transactions and return funds to investors.

A minority of the community refused, arguing that immutability was a core principle of blockchain and that reversing transactions set a dangerous precedent. The majority proceeded with the fork. The chain that reversed the transactions became the Ethereum we know today. The chain that continued without the reversal became Ethereum Classic (ETC).

Hard Fork vs. Soft Fork

The backward compatibility question is what separates hard forks from soft forks. A soft fork is a tightening of the rules: the new blocks are valid under both old and new software. Old nodes can still participate in the network, even if they cannot produce blocks that use the new features. A hard fork loosens or changes rules in ways that old software cannot recognize as valid, which is why it requires universal adoption to avoid a chain split.

In practice, the Ethereum Merge in September 2022 was one of the most technically complex hard forks ever executed. It replaced the entire consensus mechanism, switching from energy-intensive Proof-of-Work mining to Proof-of-Stake validation, but achieved near-universal adoption with no lasting chain split because the transition was years in the making and had overwhelming community support.

What Happens to Your Coins During a Hard Fork

If you hold coins on a chain that undergoes a contested hard fork, you typically receive equivalent coins on both resulting chains. Your private key works on both networks because they share the same transaction history up to the fork point. Protecting replay attacks, where a transaction broadcast on one chain is also valid on the other, requires the forked chain to implement replay protection measures that differentiate their transaction format from the original.

Exchanges handle hard fork distributions differently. Most major exchanges credit users with the forked coin if they held the original at the snapshot block, but some do not. Reviewing your exchange's policy before a significant fork is a practical step that prevents missed distributions.

Sources:
https://ethereum.org/en/history/
https://bitcoin.org/en/faq
https://bitcoincashnode.org/