In blockchain terminology, a fork occurs when a blockchain diverges into two or more potential paths. This can happen at the protocol level (a change to the rules of the network) or at the chain level (competing blocks at the same height). Forks are one of the most significant events in a blockchain's lifecycle, and understanding the different types is essential for anyone analyzing blockchain networks, assessing risk, or managing digital assets.
Temporary Forks (Chain Splits)
Before discussing protocol forks, it is important to understand that temporary forks occur naturally in the normal operation of a blockchain. When two block producers create valid blocks at approximately the same time, different parts of the network may temporarily see different "tips" of the chain. This is not a crisis—it is expected behavior.
The network resolves these temporary forks through its fork-choice rule:
- Bitcoin: The "longest chain" (most cumulative proof-of-work) wins.
- Ethereum (PoS): The LMD-GHOST algorithm selects the canonical chain based on validator attestations.
Once one branch accumulates more weight (work or attestations), the other is abandoned. Transactions in the abandoned branch return to the mempool and are typically included in the next block on the winning chain.
Soft Forks
A soft fork is a backward-compatible change to the protocol's rules. It tightens the rules: blocks that are valid under the new rules are also valid under the old rules, but some blocks that were valid under the old rules become invalid under the new rules.
Characteristics
- Backward compatible: Nodes that have not upgraded will still accept blocks produced by upgraded nodes.
- Forward incompatible: Non-upgraded nodes may produce blocks that upgraded nodes reject.
- Requires majority consensus: If a majority of the network's hash power or stake adopts the new rules, the old rules become economically irrelevant because non-upgraded block producers will find their blocks orphaned.
- No chain split (if successful): Because the old and new rules are compatible in one direction, a successful soft fork results in a single chain.
Examples
- Bitcoin SegWit (BIP-141, 2017): Segregated Witness changed how transaction data is structured, moving signature data into a separate "witness" section. Non-upgraded nodes could still validate transactions but could not fully understand the new structure.
- Bitcoin P2SH (BIP-16, 2012): Pay-to-Script-Hash changed how complex script conditions were evaluated, but non-upgraded nodes treated P2SH outputs as anyone-can-spend (which they accepted as valid).
Hard Forks
A hard fork is a backward-incompatible change to the protocol's rules. It loosens or alters the rules: blocks valid under the new rules may be invalid under the old rules. After a hard fork, nodes running the old software and nodes running the new software will diverge into separate chains unless one side is abandoned.
Characteristics
- Not backward compatible: Non-upgraded nodes will reject blocks produced under the new rules.
- Requires universal adoption (for unity): If any significant group of participants refuses to upgrade, the chain permanently splits into two independent networks.
- Creates a new chain (if contentious): A contentious hard fork results in two separate blockchains with a shared history up to the fork block and divergent histories afterward.
| Property | Soft Fork | Hard Fork |
|---|---|---|
| Compatibility | Backward compatible | Not backward compatible |
| Rule change | Tightens existing rules | Changes or loosens rules |
| Node upgrade | Optional (but recommended) | Required to follow new chain |
| Chain split risk | Low (if majority adopts) | High (if contentious) |
| Historical data | Shared (single chain) | Shared up to fork block, then divergent |
Planned vs. Contentious Forks
Planned Hard Forks
Most hard forks are planned, non-contentious upgrades coordinated by the protocol's core development team and agreed upon by the community. These are analogous to software version upgrades. Everyone upgrades their node software, and the old chain is abandoned with no minority chain persisting.
Ethereum has executed numerous planned hard forks, including:
- Homestead (2016): Early protocol improvements.
- Byzantium (2017): Privacy and performance enhancements.
- London (2021): EIP-1559 fee market reform.
- The Merge (2022): Transition from proof-of-work to proof-of-stake.
- Dencun (2024): EIP-4844 proto-danksharding for Layer 2 cost reduction.
These forks proceeded smoothly because the community reached consensus before the upgrade was activated.
Contentious Hard Forks
A contentious hard fork occurs when a significant portion of the community disagrees on a proposed change. This results in a permanent chain split, creating two independent networks with a shared history.
Historical Examples
Ethereum / Ethereum Classic (2016)
In June 2016, a vulnerability in "The DAO" (a decentralized investment fund) was exploited, draining approximately 3.6 million ETH ($60 million at the time). The Ethereum community faced a choice: accept the loss or execute a hard fork to reverse the exploit and return the funds.
The majority chose to fork, creating what we now know as Ethereum (ETH)—the chain that reversed the exploit. A minority, arguing that "code is law" and that blockchains should never reverse transactions regardless of the circumstances, continued mining the original chain, which became Ethereum Classic (ETC).
Key outcomes:
- Every ETH holder at the fork block received an equal amount of ETC on the legacy chain.
- ETH went on to become the dominant smart contract platform; ETC retained a niche following.
- The event established a precedent (and ongoing debate) about immutability versus community governance.
Bitcoin / Bitcoin Cash (2017)
A years-long debate over Bitcoin's block size limit culminated in a contentious hard fork on August 1, 2017. One faction (represented by Bitcoin Core developers) favored keeping the 1 MB block size and scaling through second-layer solutions (Lightning Network). Another faction argued for increasing the block size to accommodate more transactions directly on-chain.
The result:
- Bitcoin (BTC) maintained the 1 MB limit and adopted SegWit (a soft fork).
- Bitcoin Cash (BCH) forked with an increased 8 MB block size (later raised to 32 MB).
- Bitcoin Cash itself subsequently forked into BCH and Bitcoin SV (BSV) in 2018, when Craig Wright's faction pushed for 128 MB blocks.
Implications of Forks
Forks carry significant implications for participants:
- Asset duplication: In a contentious hard fork, holders of the original asset receive an equal balance on both chains. This creates a temporary windfall but also introduces complexity in managing two sets of assets.
- Replay attacks: Immediately after a fork, transactions on one chain may be "replayed" on the other (since the transaction format and history are identical up to the fork point). Replay protection (unique chain IDs) must be implemented to prevent this.
- Market confusion: Contentious forks create uncertainty about which chain will retain the most value, developer activity, and user adoption. Markets typically resolve this within weeks to months.
- Smart contract state: On smart contract platforms, a fork duplicates every contract's state. This can create issues with oracles, bridges, and protocols that reference off-chain data, as the off-chain world does not fork.
Key Takeaways
- Soft forks tighten protocol rules and are backward compatible; hard forks change rules in ways that require all participants to upgrade.
- Most hard forks are planned, non-contentious upgrades. Contentious forks result in permanent chain splits and the creation of new assets.
- The ETH/ETC and BTC/BCH forks are the defining historical examples of contentious splits, each originating from fundamental disagreements about protocol governance.
- Forks carry operational implications including asset duplication, replay risk, and smart contract state divergence that must be actively managed.