What is a hard fork?

A hard fork is a protocol change that old software will reject. After a hard fork, nodes running the new rules consider the new chain valid; nodes still running the old rules do not. If every operator upgrades, the network continues seamlessly. If some do not — or if some deliberately refuse — the chain splits into two separate networks.

Soft forks vs. hard forks

The distinction is about compatibility. A soft fork tightens the rules: blocks valid under the new rules are still valid under the old rules, but not vice versa. Old nodes continue to track the chain, just with a reduced view of what is allowed. Bitcoin's SegWit upgrade in 2017 was a soft fork.

A hard fork loosens or changes the rules in ways old software cannot accept. A transaction that was invalid before becomes valid, or a block's structure changes, or a new opcode lands. Old nodes reject the first block under the new rules and stop following the chain from that point.

The practical consequence is coordination. A soft fork needs a majority of miners or validators. A hard fork needs basically everyone — every exchange, every wallet, every node operator — to upgrade, or the network splits.

Planned vs. contentious

Most hard forks are planned upgrades with community consensus. Ethereum has done many: Byzantium, Constantinople, London (which introduced EIP-1559), The Merge (proof-of-stake), Shanghai (withdrawal of staked ETH), Dencun (blobs for rollups), Pectra. In each case, developers agreed on the changes, wallets and exchanges coordinated, and the network upgraded with minimal drama.

A contentious hard fork is different. It happens when a significant portion of the community disagrees about whether a change should be made, and both sides refuse to back down. The result is a permanent chain split. Each chain keeps the history up to the fork point, then diverges. Coin balances are duplicated: if you had 10 ETH before the fork, you have 10 ETH on each chain afterward.

The most famous contentious fork is Ethereum's 2016 split over The DAO. After the attacker drained tens of millions of dollars from The DAO contract, the majority of the community voted to hard-fork the chain to reverse the theft. A minority refused, arguing that immutability of the ledger was more important than any single exploit. The majority chain kept the "ETH" ticker. The minority chain continued as Ethereum Classic.

Bitcoin's forks

Bitcoin has had several hard forks driven by disputes about block size and scaling. The most consequential was Bitcoin Cash (BCH) in August 2017, which increased block size to allow more transactions per block. Bitcoin Cash itself later forked into Bitcoin SV. Each successive fork has attracted a smaller share of users, hashrate, and market cap, but the coins continue to exist.

Bitcoin proper has been unusually conservative about hard forks. The core developer culture treats changes to consensus rules as near-sacred; soft forks are preferred, and even those require extended discussion. This is one of the reasons Bitcoin is seen as more stable — and more stagnant — than Ethereum.

Replay protection and the split mechanics

When a chain splits, transactions are signed against the chain state, not the chain identity. Without careful engineering, a transaction broadcast on one chain can be replayed on the other, potentially moving coins the user did not intend to move. Modern hard forks add replay protection — chain-ID tags, transaction-format differences — so the two chains cannot share signed transactions.

Exchanges have to pause deposits and withdrawals during a fork, let the dust settle, then decide which sides to credit to users. Users holding coins on an exchange may get both sides, one side, or neither, depending on the exchange's policy.

Governance through exit

Hard forks are the ultimate governance mechanism of open blockchains. If enough people disagree with the direction of the protocol, they can fork the code and run a competing chain. Nobody can stop them. The ability to exit is what keeps the incentives of core developers and users aligned: make decisions the community will not accept, and the community takes its ball elsewhere.

The threat is usually more powerful than the execution. Most contentious forks produce a chain that loses users, value, and developer attention over time. But the option is always available, and that shapes decisions about what to upgrade and how.

Why it matters

Hard forks are how blockchains evolve and how their politics resolve. They are the point at which social consensus — which upgrades are legitimate, which are rejected — becomes technical reality. Understanding the difference between a coordinated upgrade and a chain split, and why both are called "hard forks," is essential to making sense of blockchain history. The same word covers a routine upgrade and a civil war.