How a hard fork actually splits a chain
The software changes for everyone. Whether the chain splits into two depends on who upgrades.
At a glance
- A hard fork changes the rules in a way that is not backward-compatible with nodes running the old software.
- The chain splits only if some participants upgrade and others don't — unanimous adoption means one chain, unchanged.
- Holders of the original asset typically end up holding a balance on both resulting chains after a split.
Blockchain software has rules for what counts as a valid block, and every full node enforces them independently. A hard fork changes those rules in a way that is not backward-compatible: a block valid under the new rules is invalid under the old ones, and vice versa.
If every node upgrades to the new software at the same activation point, there is no split — the chain simply continues under new rules, and this is how most planned upgrades work. A split only happens when some portion of the network refuses to upgrade and keeps validating blocks under the old rules while everyone else moves on.
From that activation block onward there are, functionally, two separate ledgers that share an identical history up to the split and diverge afterward. Anyone who held a balance on the original chain before the split holds that same balance on both resulting chains, since both started from the same historical state.
What determines whether a fork happens is not a vote in any formal sense — it's whichever chain miners or validators, and the exchanges and wallets that support them, actually choose to keep building on. A fork with no meaningful support from either group is a chain that exists on paper and nowhere else.
| Soft fork | Hard fork | |
|---|---|---|
| Compatible with old software? | Yes | No |
| Needs every node to upgrade? | No | Yes — or the chain splits |
| Can create two chains? | No | Yes, if adoption is not unanimous |
| Typical use | Tightening existing rules | Adding rules incompatible with the old ones |
Key terms
- Hard fork
- A rule change incompatible with the previous software, capable of splitting the chain if adoption is not unanimous.
- Soft fork
- A rule change that remains compatible with old software, tightening rules without forcing a split.
- Chain split
- The point at which two groups of nodes stop agreeing on a single valid history and each continue their own.
Frequently asked
Do I need to do anything if a chain I hold forks?
Usually you automatically hold a balance on both resulting chains if you controlled your own keys before the split; claiming the new asset often requires a wallet that explicitly supports it.
Can a hard fork be reversed?
Not really — once both chains have blocks built on top of the split point and are independently secured, reunifying them would mean abandoning one chain's entire subsequent history.
Is a fork the same as a chain being ‘hacked’?
No. A fork is a disagreement over software rules among legitimate participants; a hack exploits a flaw regardless of which rules are in force.