ShopBitcoin has no central authority that can force anyone to run different software or accept different rules. Changes to the protocol require voluntary adoption among a global network of independent peers. When a proposed change is adopted, the way it is adopted determines whether the network transitions smoothly or splits into two incompatible chains. This process is known as a "fork."
Not all forks are the same. A "soft fork" is a backward-compatible upgrade, whereas a "hard fork" introduces incompatible rule changes that can permanently divide the network. Understanding the difference matters for anyone who holds bitcoin and has an interest in its future.
What is a Fork?
A fork is a divergence point in Bitcoin's blockchain. It arises when a change to the consensus rules is introduced and not all nodes adopt it simultaneously. When nodes enforce different rules, they may begin accepting different blocks and building on separate chains.
Bitcoin's consensus rules form the shared protocol that every node enforces independently. These rules define what makes transactions and blocks valid or invalid, including foundational constraints like the 21 million supply cap and the requirement for a valid digital signature to authorize any spend. As long as all nodes enforce compatible rules, the network reaches consensus and produces a single shared chain of transaction history.
The term "fork" captures the potential branching of that chain at the point where rules diverge. Whether a fork causes a permanent split, or resolves without one, depends on backward compatibility.
A backward-compatible change can be adopted gradually without forcing every participant to upgrade simultaneously. A change that breaks backward compatibility forces every participant to choose which rule set to follow, and can permanently divide the chain if that choice is not unanimous.
What is a Soft Fork?
A soft fork introduces new rules that are stricter than before but remain compatible with what existing nodes already accept as valid. Nodes that have not adopted the new rules still see the new blocks as valid, even though they do not enforce the new rules themselves. This is why soft forks do not require every participant to upgrade simultaneously.
Nodes that have not upgraded still process the new blocks without rejecting them, so the network remains unified.
There is no single activation mechanism for all soft forks. Earlier upgrades used a miner signaling threshold called BIP9, where miners include a version bit in mined blocks and the fork locks in once a defined percentage of blocks signal readiness within a given window.
Taproot used a variant called Speedy Trial, requiring 90% of blocks in a 2,016-block window to signal within a fixed timeframe. SegWit's activation was more contentious. Miner adoption stalled under BIP9, and a parallel movement called UASF (User Activated Soft Fork, BIP148) saw economic nodes commit to enforcing the new rules regardless of miner signaling, ultimately breaking the deadlock. The history of SegWit activation is the clearest demonstration that miners do not unilaterally control whether a soft fork is adopted.
Examples of Bitcoin soft forks:
-
SegWit (2017, block 481,824). SegWit separated signature (witness) data from the main transaction body and introduced new address formats. It also fixed transaction malleability, which paved the way for the Lightning Network. Nodes that did not upgrade still processed SegWit transactions as valid.
-
Taproot (2021, block 709,632). Taproot introduced Schnorr signatures (BIP340), P2TR addresses (BIP341), and Tapscript (BIP342). Key path spends in Taproot look identical on-chain regardless of the underlying spending policy, improving privacy. Older nodes still accepted Taproot transactions as valid.
What is a Hard Fork?
A hard fork is a non-backward-compatible change to Bitcoin's consensus rules. After a hard fork, blocks produced under the new rules are rejected as invalid by nodes still running the old rules. The two sets of nodes are no longer in agreement, and the chain splits into two independent histories from the fork point forward.
After a hard fork, every node must make a choice about which rule set to follow. Nodes that upgrade follow the chain running the new rules. Nodes that do not upgrade remain on the chain running the old rules. If a significant group stays on the old chain, the result is two chains running simultaneously with incompatible rules, each producing blocks on its own separate history. These chains share all transactions and blocks prior to the fork height but diverge entirely after it.
This is the key difference from a soft fork. A soft fork is backward-compatible, while a hard fork is not. In a hard fork, nodes on each side of the split reject the other's blocks as invalid, so once the chains diverge, they cannot be reconciled. They are separate networks running separate coins.
Examples of Bitcoin hard forks:
-
Bitcoin Cash (BCH, August 2017). A group of miners and businesses forked Bitcoin to increase the block size limit from 1 MB to 8 MB. Legacy Bitcoin nodes rejected any block exceeding 1 MB as invalid, while BCH nodes accepted the larger blocks. The two sets of nodes could no longer agree on a valid chain, making the split permanent. Bitcoin Cash has since continued as a separate network with its own development, coin, and market price.
-
Bitcoin SV (BSV, November 2018). Bitcoin SV was a subsequent fork of Bitcoin Cash that increased the block size further and reversed some of its protocol changes. It is a separate chain with no technical connection to Bitcoin after its fork height.
Neither Bitcoin Cash nor Bitcoin SV represent upgrades to Bitcoin. They are separate networks with separate assets produced by groups who chose incompatible rules. Bitcoin continued as its own chain, unchanged by either event.
What the Block Size Wars Proved
The BCH hard fork in 2017 was the most significant stress test Bitcoin's social consensus had faced. A well-funded group with significant miner support attempted to change Bitcoin's rules by increasing the block size. The majority of economic nodes, users, developers, and exchanges stayed with the original chain. Bitcoin Cash launched with considerable resources and vocal support, but without the economic consensus of the original network, it could not establish itself as Bitcoin and has since declined steadily in relevance and value relative to BTC.
The market's verdict has been consistent. Bitcoin Cash peaked at roughly $4,000 in December 2017 and has since lost more than 95% of its value relative to BTC. Bitcoin SV fared worse. Every contentious hard fork attempt has produced the same outcome. The resulting coin gets assigned progressively less value by the market over time.
For many in the Bitcoin community, this history is the strongest argument for ossification. If a well-resourced group with significant miner support could not change Bitcoin's rules, it suggests that Bitcoin's social consensus is more durable than any technical attack. The lesson the community drew was direct. Hard forks do not change Bitcoin. They produce a group that left Bitcoin. Bitcoin's rules are enforced not by any technical lock, but by the collective refusal of its users to follow unwanted changes.
Every failed fork attempt raises the cost of the next one, and reinforces the argument that the base layer should be left alone.
Which Chain is Bitcoin?
When Bitcoin Cash forked from Bitcoin, both chains shared an identical history up to block 478,558. Both had the same genesis block, the same early transactions, the same accumulated proof of work. On paper, the question of which chain was the real Bitcoin might seem genuinely ambiguous.
In practice, there was no ambiguity. Bitcoin is defined not just by its transaction history but by its social consensus. That consensus is the collective agreement of its users, developers, businesses, and node operators about which chain to treat as Bitcoin. It stayed with the original chain by an overwhelming margin. Major exchanges, core developers, wallet software, and the majority of economic activity all continued on BTC.
The BCH camp argued they were preserving Satoshi's original vision. The BSV camp made an even more explicit claim to legitimacy. The market rejected both conclusively. A currency that no one accepts as Bitcoin is not Bitcoin, regardless of what its creators call it.
The deeper point is that the question contains a false premise. Bitcoin did not split into two Bitcoins. A group that wanted different rules forked away from Bitcoin and created a new coin. Bitcoin continued on its original chain, with its original rules, unchanged. The fork did not divide Bitcoin. It demonstrated that Bitcoin's rules are not up for negotiation, and that attempting to change them produces only a new altcoin, not a new Bitcoin.
What Happens to Your Bitcoin in a Fork?
The fork type and how you hold your bitcoin determine the practical outcome.
-
In a soft fork: Your bitcoin is unaffected. Soft forks are backward-compatible by definition, so wallets that do not upgrade continue to work normally. New features become available for those who choose to use them, but nothing changes for those who do not.
-
In a hard fork, if you hold your own keys: At the moment of the chain split, both chains share an identical UTXO set. Every address that held bitcoin before the fork now holds coins on both chains. The same private key that controlled bitcoin before the fork can now spend on both versions of the chain. You can transact on either chain independently, including selling the forked coin on an exchange that lists it.
-
In a hard fork, if your bitcoin is on an exchange: With exchange custody, the exchange controls the private keys. Whether you receive coin credit from the forked version depends entirely on the exchange's policy. Some credit fork coins promptly, some credit them after a delay, and some never credit them at all. There is no standard or guarantee. This is one more reason self-custody matters. It preserves your options across any future network event.
A note on replay protection. When two chains share an identical UTXO set and private keys, a transaction broadcast on one chain can sometimes be rebroadcast (replayed) on the other, moving coins you did not intend to move. Hard forks can implement replay protection, a modification to the transaction format that makes transactions on each chain invalid on the other. Bitcoin Cash implemented replay protection at the time of its fork. Without replay protection in place, spending fork coins can inadvertently affect your bitcoin balance on the other chain.
Related articles
What are Bitcoin Improvement Proposals?
How protocol changes are proposed, debated, and coordinated — and where forks fit in the BIP process.
Running a Bitcoin Node
How running your own node gives you sovereignty over which rules you enforce on the network.
What is a Bitcoin Seed Phrase?
The backup that gives you access to your coins across any chain that recognizes your addresses.
The Most Important BIPs
The specific BIPs behind SegWit, Taproot, and the wallet standards in common use today.