Bitcoin Forks Explained: Bitcoin Cash (BCH) vs Bitcoin SV (BSV)

By · Updated

BCH and BSV are incompatible descendants of Bitcoin created by disagreements over scaling and protocol governance. BCH favors larger on-chain payment capacity than BTC; BSV pushed that strategy much further and concentrated its ecosystem around enterprise-scale nodes. Compare validation cost, wallet and exchange support, reorganization risk, and actual payment requirements—not claims to be the one "true" Bitcoin.

How the block-size dispute produced BCH

Bitcoin's history is marked by ideological disagreements about how the network should scale, and these disagreements have produced two major forks: Bitcoin Cash (BCH) in 2017 and Bitcoin SV (BSV) in 2018. Understanding the technical and philosophical differences between these forks and the original Bitcoin (BTC) sheds light on one of the most contentious debates in cryptocurrency history.

Before SegWit, Bitcoin enforced a one-megabyte serialized block-size limit. SegWit, activated on BTC in 2017, replaced that simple measure with four million weight units and discounted witness data. During the 2016–2017 congestion debate, one camp wanted larger base-layer blocks while another combined constrained base-layer validation with SegWit and payment channels.

On August 1, 2017, the big-block faction executed a hard fork, creating Bitcoin Cash (BCH). Bitcoin Cash launched with an 8 MB block size limit, later increased to 32 MB, allowing significantly more transactions per block. The goal was to make Bitcoin Cash function more like digital cash for everyday payments, with low fees and fast confirmations. Proponents argued this was closer to Satoshi's original vision of a peer-to-peer electronic cash system.

Meanwhile, Bitcoin (BTC) activated SegWit and continued developing the Lightning Network, a layer-2 payment channel system that enables near-instant, low-fee transactions off-chain. The BTC camp argued that keeping the base layer small and adding scaling layers on top would better preserve decentralization, since larger blocks require more storage, bandwidth, and processing power from node operators.

Why BSV split from BCH

The Bitcoin Cash community itself was not united for long. In November 2018, a second fork occurred within BCH, producing Bitcoin SV (BSV). The split was driven by Craig Wright, an Australian computer scientist who controversially claimed to be Satoshi Nakamoto, and Calvin Ayre, a billionaire entrepreneur. Their faction, backed by the company nChain, advocated for dramatically larger blocks and a return to what they called "the original Bitcoin protocol." The opposing faction, led by developer Amaury Sechet and supported by Bitmain co-founder Jihan Wu, continued with Bitcoin Cash under the Bitcoin ABC implementation.

Bitcoin SV, which stands for "Satoshi Vision," pursued an aggressive block size strategy. The BSV network eventually removed the block size cap entirely, allowing blocks of theoretically unlimited size. Proponents argued this would enable massive throughput and allow the blockchain to serve as a global data ledger for applications far beyond simple payments. Critics countered that this approach sacrifices decentralization, as only well-funded data centers can operate nodes that process and store such large blocks.

The networks now have separate consensus rules, address conventions, infrastructure, and market support. A 2024 High Court judgment in the United Kingdom found that Craig Wright was not the author of the Bitcoin white paper, did not operate as Satoshi Nakamoto, and did not create Bitcoin. That finding removes a central factual premise from BSV's founder-led narrative, but it does not itself evaluate the protocol's code.

Technical trade-offs and a practical test

The fork wars illustrate a fundamental tension in blockchain design: the tradeoff between throughput, decentralization, and security. Increasing block size improves throughput but raises the hardware requirements for running a full node, potentially concentrating network power among fewer operators. Off-chain solutions preserve decentralization at the base layer but add complexity and introduce their own trust assumptions. At its core, the debate reflects a deeper question about who should control the infrastructure of money -- whether power should rest with well-funded mining operations and corporate entities, or remain distributed among ordinary participants who can run their own nodes.

For a payment deployment, benchmark the complete path: confirmation policy, reorganization handling, fee estimation, refund support, custody, accounting, and conversion to the currency in which liabilities are paid. Run a validating node on representative hardware before claiming that a design is decentralized. BTC, BCH, and BSV make different trade-offs; none turns an irreversible payment rail into consumer-protected settlement by itself.

Primary references

BitCoin, BCH, BSV, Forks

Published · Updated