A hard fork is a protocol change that makes a blockchain’s new consensus rules incompatible with older rules. A node running old software may reject blocks produced under the new rules. What happens next depends on coordination: if participants broadly adopt the upgrade, one network may continue under the new rules; if groups keep supporting incompatible rule sets, separate chains can continue from a shared history. A hard fork does not automatically create a lasting split or a valuable second coin.
Planned upgrades and lasting splits
Protocol developers propose and implement a change, then node operators, miners or validators, applications, exchanges, and users decide which software and chain to support. A planned hard fork can activate at an agreed time or block, with most participants moving together. A contentious hard fork can leave two communities maintaining different rules. The split’s practical importance depends on continued network participation, security, software support, liquidity, and user adoption—not simply on the fact that the code changed.
Two historical examples show the difference. During Ethereum’s 2016 DAO response, the main community adopted a state change at a designated block, while some participants continued the pre-fork chain; that continuing network is now known as Ethereum Classic. In 2017, Bitcoin Cash separated from Bitcoin after disagreement about protocol changes, and both projects continued with a shared transaction history up to the split. These cases involved different decisions and should not be treated as a single template for every upgrade.
Replay protection and user precautions
After a chain split, a transaction signed for one network might also be valid on the other unless the transaction format or network rules prevent replay. Some protocols use chain-specific signing or other replay protections, but support varies. If a split is announced, users should check the relevant project’s official notices and their wallet or exchange’s policy before sending funds or trying to claim a forked asset. A hard fork does not guarantee that a second asset will be supported, valuable, or safe to access. Never share a recovery phrase with a site claiming it is needed to release forked coins.
Why hard forks are debated
Hard forks can let a network adopt changes that old software cannot accept, but coordination can be difficult. Disagreement may divide users, developers, validators or miners, and service providers; a lasting split can fragment security, liquidity, and network effects. Supporters of a change may consider it necessary to fix a problem or pursue a different design, while opponents may prefer continuity or worry about who has influence over the upgrade. Whether a change is beneficial depends on its technical effects and on which participants choose to support it.
Social Media Sentiment
An August 2023 r/CryptoCurrency discussion marking six years since the Bitcoin–Bitcoin Cash split showed disagreement about how to judge the fork: some commenters emphasized market adoption and price, while others pointed to fees, usability, or the value of having a competing design. Those replies reflect one self-selected discussion and are not a neutral measurement of either network’s performance.
Last updated: 2026-10
Related Terms
See Also
- Why DAO Governance Votes Often Fall Short — and Why Protocols Still Use Them
- Are Layer 2 Networks Actually Decentralized?
- Does Ethereum TPS Include Layer 2 Transactions?
- Trade crypto with ChangeNOW
Sources
- Ethereum.org — Glossary — Defines a hard fork as an incompatible protocol change that can leave non-upgraded nodes unable to validate newer blocks.
- Ethereum Foundation — Hard Fork Completed — Records the 2016 DAO-related Ethereum hard fork and the continued participation of users on the non-fork chain.
- Bitcoin Cash Node — Project Documentation — Describes Bitcoin Cash as a separate currency after the August 2017 split and documents its network upgrades.
- Ethereum Improvement Proposal 155 — Simple Replay Attack Protection — Specifies chain-ID transaction signing designed to prevent replay across networks.