What Is a Hard Fork in Blockchain Terms?
Blockchain networks occasionally need to change their underlying rules, and one of the more significant ways that happens is through what’s called a hard fork. Understanding what actually splits when this occurs helps make sense of news stories about a network “forking.”
The short answer
A hard fork is a change to a blockchain’s underlying rules that is not backward-compatible, meaning software still running the old rules can no longer validate or follow the new chain. This creates a permanent split: the network effectively divides into two separate chains, one following the old rules and one following the new ones, unless every participant upgrades together.
Why hard forks happen
Blockchain networks are maintained by decentralized groups of participants running software that all needs to agree on the same set of rules to stay in sync. Developers sometimes propose changes to improve security, add functionality, adjust how transactions are processed, or fix a flaw discovered in the existing rules. When a proposed change is significant enough that it can’t be layered on top of the existing rules without breaking compatibility, it requires a hard fork rather than a smaller, backward-compatible adjustment.
How a hard fork actually splits a chain
- Rule incompatibility. Nodes still running the old software reject blocks created under the new rules, and vice versa, because each considers the other invalid according to its own rule set.
- Chain divergence. From the point of the fork onward, the two versions of the blockchain record separate transaction histories, even though they share identical history up to the fork.
- Community and network split. Because both chains can continue to operate independently, whether one becomes dominant or both persist depends on which one participants, developers, and infrastructure providers choose to support going forward.
- Requirement for coordinated upgrade. Avoiding a permanent split requires essentially all participants to upgrade to the new software at the same time; if adoption is incomplete, the split becomes lasting. Developers often trial major rule changes on a testnet before deploying to the mainnet to catch problems before they affect real value.
Hard fork versus soft fork
A hard fork is often contrasted with a soft fork, which is a backward-compatible rule change — old software can still recognize new blocks as valid, even if it doesn’t take advantage of the new rules. Because a soft fork doesn’t require universal upgrading to avoid a split, it’s generally considered a less disruptive way to implement a change, though it’s not suited to every type of rule modification a network might need.
Notable examples and why they matter
Bitcoin and Ethereum have each experienced hard forks over their histories, sometimes resulting in entirely separate cryptocurrencies that continued to exist independently after the split. These events illustrate that a hard fork isn’t purely a technical footnote — it can create two distinct assets with separate values, separate communities, and separate ongoing development, which is part of why they tend to generate significant attention when they occur.
This tension between backward compatibility and meaningful change is part of the same broader set of tradeoffs described by the blockchain trilemma, where altering one property of a network often has ripple effects on the others.
What to weigh as a holder
Anyone holding an asset on a chain that undergoes a hard fork should understand that the two resulting chains may behave very differently afterward in terms of security, adoption, and long-term viability. Tax treatment of assets received through a fork can also be a genuinely complex question, and because rules in this area change and depend on individual circumstances, consulting a tax professional about a specific situation is generally the safest approach.
The takeaway
A hard fork is fundamentally a rule change so significant that old and new software can no longer agree on what counts as a valid transaction, permanently splitting a blockchain’s history in the process. Recognizing this mechanism helps explain why some forks fade quickly while others result in lasting, independent networks.