The Bitcoin Cash Fork: History and What Caused the Split

Bitcoin Cash was created in August 2017 through a contentious hard fork of the Bitcoin blockchain, born out of a multi-year disagreement over how to scale transaction capacity as Bitcoin's popularity grew. One camp wanted to increase the block size limit directly to allow more transactions per block; the other favored off-chain scaling solutions that kept blocks small. When consensus couldn't be reached, the block-size camp split off to create a new chain with its own rules.

This event remains one of the clearest real-world examples of how a hard fork plays out when a community can't agree on a proposed rule change.

The roots of the disagreement

Bitcoin's original block size limit was capped at 1 megabyte, a constraint introduced years earlier as an anti-spam measure. As adoption grew through 2015 and 2016, blocks began filling up regularly, leading to slower confirmation times and rising transaction fees during periods of congestion.

Two broad camps formed around how to address this. One group argued for simply raising the block size limit, allowing more transaction data into each block and directly increasing throughput. The other group worried that significantly larger blocks would make running a full node more resource-intensive, potentially concentrating validation among fewer, wealthier participants, and instead favored solutions like Segregated Witness and off-chain, second-layer scaling.

This disagreement, often called the block size wars, played out over years of technical proposals, community debate, and industry negotiations. Our dedicated article on the block size wars traces that broader multi-year conflict in full.

The activation of SegWit and the breaking point

In mid-2017, Segregated Witness activated on the Bitcoin network as a soft fork, restructuring transaction data to effectively increase capacity without directly raising the base block size limit. For the big-block camp, this fell short of what they believed was necessary, and rather than continuing to push for a compromise on the existing chain, a portion of that community moved to implement their own client with a significantly larger block size limit, set initially at 8 megabytes.

On August 1, 2017, this new client activated, and at a predetermined block height, the chains diverged. Bitcoin Cash was born, sharing the identical transaction history with Bitcoin up to that block, but following its own separate rules going forward.

Bitcoin and Bitcoin Cash after the split

Aspect	Bitcoin (BTC)	Bitcoin Cash (BCH)
Block size approach	Kept small, scales via layers	Increased directly on-chain
Scaling philosophy	Off-chain/Layer 2 first	On-chain capacity first
SegWit adopted?	Yes	No
Community size post-fork	Retained majority of users, developers, market value	Smaller, dedicated community

What happened to holders

Anyone holding Bitcoin at the moment of the fork automatically held an equivalent balance of Bitcoin Cash as well, since both chains shared identical history up to the split point. What differed afterward was market and infrastructure support: exchanges had to decide whether and how to list the new asset, and the broader market had to determine what value, if any, to assign it independently of Bitcoin.

This pattern, a shared history followed by diverging value based on ongoing community and market support, is common to most contentious hard forks, not unique to this one.

Why Bitcoin Cash didn't converge back

Because block size defines a fundamentally different validation and scaling approach, there was no simple way to reconcile the two chains after the split. Nodes running the original small-block software would reject blocks larger than 1 megabyte as invalid, while Bitcoin Cash nodes required exactly the opposite. Once a hard fork like this activates and each side has meaningful, independent economic and social support, reunification effectively never happens.

Bitcoin Cash itself later underwent its own internal disagreements and further splits, illustrating that the underlying tension between differing visions for scaling and governance didn't disappear after the initial fork, it simply continued to express itself in new splits within the newer chain's community as well.

The broader lesson

The Bitcoin Cash fork demonstrated that Bitcoin's governance isn't top-down, no single company or foundation could force a unified decision on block size. Instead, the outcome was determined by which chain the economic majority, exchanges, merchants, developers, and users, chose to continue treating as valuable and worth building on. This decentralized, sometimes messy resolution process is a direct consequence of Bitcoin having no central authority, a tradeoff that's core to its design philosophy as explored in our overview of what Bitcoin is.

Bottom line

The Bitcoin Cash fork was the culmination of a long-running disagreement about how Bitcoin should scale, resolved not through a vote or a company decision but through a hard fork that let each side pursue its own vision on a separate chain. It remains the most prominent real-world case study of what happens when a blockchain community can't reach consensus on a fundamental protocol parameter, and it illustrates why block size, seemingly a narrow technical detail, became one of the most consequential debates in Bitcoin's history.