# Forks & Chain Divergence
Publisher: Bitcoin Library (KK siiiiiixth) — https://bitcoin.ne.jp

## Forks & Chain Divergence

URL: https://bitcoin.ne.jp/en/learn/forks
URL role: Self-canonical for this English representation
Japanese counterpart URL: https://bitcoin.ne.jp/learn/forks
Slug: forks
Language: en
First published: 2025-12-01
Last updated: 2026-10-20
Last verified: 2026-10-09
Description: Bitcoin Cash, Bitcoin SV, and soft forks: the major schisms in Bitcoin's history and the philosophical battles over "immutability."

Forks come in two forms: backward-compatible soft forks and chain-splitting hard forks. The 2015–2017 Block Size War produced major hard forks such as Bitcoin Cash and Bitcoin SV, and that history showed that a majority of miners alone cannot change the rules.

Reuse terms: https://bitcoin.ne.jp/licenses#content-reuse
Third-party sources retain their own rights. Cite the canonical HTML URL or its section fragment.
Sources below are article-level references; they do not establish support for every sentence. Check the original source and its date before quoting time-sensitive claims.
This is educational material, not investment or legal advice. Dates describe the editorial text; this representation excludes browser tools and live market/network values.

### A 30-second entry

A network that shared one history yesterday may choose different rulebooks today. A fork is a story of coordination as much as code.

Mental model: Imagine two hiking parties with the same map choosing different routes at a junction, each keeping the trail they walked together up to that point.
Where the analogy stops: Soft and hard forks differ in compatibility, and not every software update creates a new coin. Names, market value, and legitimacy are not determined by code alone.
Reading journey: [Rule changes and compatibility](https://bitcoin.ne.jp/en/learn/forks#hard-vs-soft) → [Historical splits](https://bitcoin.ne.jp/en/learn/forks#blocksize-war) → [Coordination and legitimacy](https://bitcoin.ne.jp/en/learn/forks#what-is-bitcoin)
What you will understand: Beyond “code is law,” you will see how software, miners, nodes, markets, and people coordinate around rules.

### Hard fork vs. soft fork

Section URL: https://bitcoin.ne.jp/en/learn/forks#hard-vs-soft

[Figure: fork-types — A soft fork narrows the set of valid blocks, making it possible for upgraded and old nodes to remain on one history. A hard fork expands validity beyond the old rules, so disagreement can split history.]

A fork is a protocol change: the existing network branches onto new rules.

Soft fork: the new validity rules are a subset of the existing ones. Nodes that do not implement them stay compatible with nodes that do, so the change is backward-compatible.

Hard fork: the new validity rules are incompatible with the existing ones, and nodes on each side recognize different chains. There is no backward compatibility, so as long as nodes and hash power supporting the old rules remain, the result is two chains (if the old side disappears entirely no split persists, but in practice a split is assumed).

Soft forks are asymmetric. Because the new rules must be a subset of the old ones, changes can only tighten, making previously valid things invalid. Loosening changes, such as raising the 21 million supply cap or the block limit, are necessarily hard forks. This asymmetry is the technical basis for saying Bitcoin's rules are hard to change.

Bitcoin conservatively prefers soft forks. SegWit (2017) and Taproot (2021) were both soft forks. Hard forks split chains easily, so they are avoided unless the whole community agrees.

A UASF (User Activated Soft Fork), as practiced during SegWit in 2017, activates on the will of node operators, meaning users, rather than on miner signaling.

### The block size war (2015–2017)

Section URL: https://bitcoin.ne.jp/en/learn/forks#blocksize-war

The fiercest internal debate in Bitcoin's history. How to deal with the 1MB block size limit split the community in two.

"Big Blockers": simply raise the block size, in a hard fork. The main advocates were Roger Ver and Jihan Wu (Bitmain), and several expansion proposals appeared: BIP 100/101/102/109 (BIP 148, discussed below, was not an expansion proposal but a tool of the small-block side).

"Small Blockers": scale through SegWit, the Lightning Network, and similar work. This was the mainstream view among Core developers, and BIP 141 SegWit was the camp's central proposal.

The New York Agreement (May 2017) was a compromise signed by major companies and miners: "SegWit + 2MB hard fork." The 2MB portion was later abandoned, and only SegWit activated.

August 1, 2017: BIP 148 (UASF) came into force. BIP 91, which had locked in ahead of it on July 21, brought miner signaling into line, and SegWit locked in on August 9 (block 479,808) and activated on August 24 (block 481,824). On that same August 1, the big blockers split off Bitcoin Cash (BCH) in a hard fork.

### Bitcoin Cash (BCH, August 1, 2017)

Section URL: https://bitcoin.ne.jp/en/learn/forks#bitcoin-cash

Bitcoin's first major hard fork. It raised the block size to 8MB, later 32MB, and stressed the practicality of on-chain payments.

Roger Ver ("Bitcoin Jesus") marketed it aggressively, and for a while BCH drew real support in the US and Asia as "the true Bitcoin successor."

November 2018: BCH further split internally. Craig Wright (self-proclaimed Satoshi Nakamoto) and Calvin Ayre's Bitcoin SV (BSV) branched off from Bitcoin Cash ABC.

November 15, 2020: another chain branched off BCH, initially named Bitcoin Cash ABC (BCHA). It was renamed eCash (XEC) in July 2021, with a re-denomination splitting one token into 1,000,000 XEC.

As of August 2026, published market-cap trackers put BCH below 1% of Bitcoin's (figures vary by tracker).

### Bitcoin SV (BSV, November 2018)

Section URL: https://bitcoin.ne.jp/en/learn/forks#bitcoin-sv

Craig Wright forked from BCH under the "Satoshi Vision" banner, claiming Satoshi's original vision, and removed the block size limit entirely.

Wright's persistent claim to be Satoshi Nakamoto fueled fierce controversy. In 2024 the UK High Court ruled that he is not Satoshi.

Major exchanges dropped it: in 2019 Binance, Kraken, ShapeShift, and others delisted BSV in response to Wright's legal threats against individuals.

2021: BSV suffered 51% attacks, with multiple block reorganizations that exposed its security weaknesses.

These events show that creating a fork does not guarantee exchange listings or user support.

### A history of the major soft forks

Section URL: https://bitcoin.ne.jp/en/learn/forks#soft-forks

BIP 16 P2SH (2012): "Pay to Script Hash." It lets a script, a multisig for example, hide behind an ordinary address.

BIP 66 Strict DER (2015): a strict signature format, which tightened the cryptography.

BIP 68/112/113 CSV (2016): relative timelocks, activated July 4, 2016 (block 419,328). They are the basis for Lightning Network's time-locking.

BIP 141 SegWit (2017): Segregated Witness. It fixed transaction malleability and made the Lightning Network possible.

BIP 340/341/342 Taproot (2021): Schnorr signatures, MAST, and Tapscript. Privacy improvements, and the basis on which Ordinals was later built.

### "What is Bitcoin?": governance philosophy

Section URL: https://bitcoin.ne.jp/en/learn/forks#what-is-bitcoin

The Block Size War crystallized the fundamental question: "who governs Bitcoin?"

The candidates: developers (Core contributors), miners, exchanges, large holders, ordinary users running nodes, and corporations. Which of them actually decides?

What the war showed is that a majority of miners alone cannot change the rules. No matter how many miners agree, if full nodes reject their blocks, the result is merely a split-off chain.

But it does not follow that node operators alone decide. Nodes decide which blocks to accept; which chain carries economic value as "Bitcoin" is decided by exchange tickers, market price formation, and user choice, that is, by the economic majority. A node veto is a necessary condition, not a sufficient one.

This aligns with Bitcoin's core principles of "permissionless" and "censorship-resistant" operation.

The UASF (User Activated Soft Fork) idea is the practical form of "users are the network's guardians."

### Future fork outlook

Section URL: https://bitcoin.ne.jp/en/learn/forks#forks-outlook

Soft fork candidates (all figures below are as of August 2026): OP_CAT has reached "Complete" specification status as BIP-347, but no mainnet activation parameters are set. OP_CHECKTEMPLATEVERIFY (CTV, BIP-119, Draft) entered a signaling window on March 30, 2026 via an independent activation client, yet miner signaling has stayed at 0% (the configured activation threshold is 90%). OP_CHECKSIGFROMSTACK (CSFS, BIP-348, Draft) is discussed as a companion to CTV. Inclusion in the BIPs repository is not a decision to activate.

Quantum migration: draft BIP-360 (Pay-to-Merkle-Root) proposes an output type that mitigates long public-key exposure, but it is not itself a post-quantum signature and does not solve short exposure after a spend reaches the mempool. Draft BIP-361 discusses migration and legacy signatures. Neither has an activation schedule or an adopted replacement signature.

For hard forks, changing rules and creating a separate chain is distinct from gaining support among users and exchanges. The histories of Bitcoin Cash and Bitcoin SV illustrate that distinction.

"Bitcoin is Bitcoin": a simple point, engraved into the community after a decade of debate, and a demonstration of how strong network effects can be.

### Primary Sources

- BIP-148 — UASF (Mandatory SegWit Activation): https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki
- BIP-141 — Segregated Witness (SegWit): https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki
- Bitcoin BIPs Repository: https://github.com/bitcoin/bips
- Bitcoin Core — CSV soft fork activation notice (July 4, 2016, block 419,328): https://bitcoincore.org/en/2016/06/21/csv-softfork-instructions/
- BIP-360 — Pay-to-Merkle-Root (Draft mitigating long public-key exposure): https://github.com/bitcoin/bips/blob/master/bip-0360.mediawiki
- BIP-361 — Post Quantum Migration and Legacy Signature Sunset (Draft): https://github.com/bitcoin/bips/blob/master/bip-0361.mediawiki
- UK High Court Judgment — COPA v Wright [2024] EWHC 1198 (Ch) (May 20, 2024, Mellor J): https://www.judiciary.uk/wp-content/uploads/2024/05/COPA-v-Wright-Judgment.pdf
- Kraken - BSV delisting announcement (April 16, 2019): https://blog.kraken.com/product/kraken-is-delisting-bsv

### Revision history

- 2026-10-20: Limited market assessments to dated observations and specific events.
- 2026-08-23: Corrected wording that implied BIP 360 was already a post-quantum signature output: it is a Draft mitigating long public-key exposure, while short exposure and post-quantum signatures remain unresolved.
- 2026-08-18: Added a bilingual comparison diagram showing soft-fork compatibility and hard-fork chain divergence.
- 2026-08-16: Corrected SegWit activation to August 24, 2017 (block 481,824), reclassified BIP-148 and fixed the CSV activation year, softened the governance claim to include the economic majority, updated covenant and quantum-resistance proposals to their August 2026 status, and replaced the COPA citation with [2024] EWHC 1198 (Ch)
