Bitcoin Core vs Bitcoin Cash: What the Fork Actually Settled

The “Bitcoin vs Bitcoin Cash” confusion persists because both share the same origin — the same genesis block, the same transaction history up to a single point, and to varying degrees the same name. Both chains descended from block 478,558 of the original Bitcoin blockchain on August 1, 2017. After that block, they share nothing.

The split is usually explained as a technical dispute about block size. Block size was the mechanism, but that framing understates the disagreement. The underlying question was: what is Bitcoin actually for — a settlement layer for high-value transactions secured above all else, or a peer-to-peer cash system capable of everyday low-cost payments? Those two goals produce genuinely different architectures when you follow the logic through. The block size limit was where that philosophical fork became a chain fork.

How Each Architecture Works

Bitcoin’s 1MB block size limit became a binding constraint as transaction volumes grew. By 2015–2017, the Bitcoin mempool was backlogging regularly, driving fees higher during congestion. Two scaling philosophies crystallized.

The small-block position — which became Bitcoin Core (BTC):

Keep blocks small to minimize node operation costs, preserving the ability of ordinary users to run full nodes and resist centralization. Scale above the base layer via the Lightning Network — a payment channel system where the vast majority of transactions settle off-chain, with the base layer functioning as a high-security final settlement rail.

SegWit (Segregated Witness), activated on Bitcoin in August 2017, restructured how transaction data was stored, moving signature (witness) data outside the base block structure. This effectively increased usable block capacity to roughly 1.7–2MB equivalents while also fixing transaction malleability, a prerequisite for reliable Lightning channels.

The big-block position — which became Bitcoin Cash (BCH):

Increase the block size limit directly, allowing more transactions per block without requiring users to interact with secondary layers. On-chain scaling maintains the peer-to-peer payment model without introducing Lightning’s liquidity management requirements or routing complexity.

Bitcoin Cash launched on August 1, 2017 with an 8MB block limit. That limit is currently 32MB. BCH has since hard-forked again: Bitcoin SV (BSV) split from BCH in November 2018 over another disagreement about block sizes and protocol direction, leaving three distinct chains with the same pre-2017 history.

How the fork mechanics worked:

At block 478,558, Bitcoin Cash introduced replay protection and new consensus rules that Bitcoin Core nodes rejected. Any Bitcoin held before the split automatically existed on both chains — the same addresses, the same private keys, different chains from that point. There was no single moment of failure; the split was clean and immediate upon the first BCH-compatible block.

Where Constraints Live

Bitcoin Core’s binding constraints are architectural and largely by design:

• Base layer throughput: approximately 7 transactions per second on-chain; fees spike predictably during demand surges
• Layer 2 complexity: Lightning requires channel liquidity management, consistent node availability to receive payments, and routing reliability — not universally accessible without custodial intermediaries
• Block size conservatism: increasing the limit requires social consensus across a decentralized developer and miner base; the governance structure makes this deliberately difficult

Bitcoin Cash’s binding constraints are different in kind:

• Security: BCH operates with roughly 3–5% of Bitcoin’s hashrate. Lower hashrate means lower cost to mount a 51% attack. BCH has experienced reorganization events; the attack cost is orders of magnitude lower than BTC
• Adoption asymmetry: Despite technically higher block capacity, BCH processes fewer daily transactions than BTC. The throughput ceiling is largely unused
• Node centralization pressure: Larger blocks require more storage and bandwidth to run a full node. At sustained high volume, this concentrates node operation among well-resourced participants

The block size debate is partially a political economy problem — both positions accepted genuine tradeoffs and disagreed about which were acceptable given Bitcoin’s primary use case.

What’s Changing

Bitcoin Core: Taproot (activated November 2021) added Schnorr signatures and MAST (Merkelized Abstract Syntax Trees), improving multi-party transaction privacy and enabling more expressive scripting. Ordinals and BRC-20 inscriptions — introduced in early 2023 — created new on-chain demand for block space by embedding data directly in Bitcoin transactions. Fee spikes during peak inscription activity renewed debate about block space prioritization and whether low-value transactions can remain economically viable on the base layer. Lightning Network capacity continues to grow; routing reliability and inbound liquidity management remain friction points for non-custodial users.

Bitcoin Cash: The CashTokens upgrade (May 2023) added native token and NFT functionality to the BCH base layer without a separate smart contract language — tokens are first-class protocol objects. SmartBCH, an EVM-compatible BCH sidechain, was paused following custody and bridge security issues in 2022. Current development focus is on base-layer improvements and CashTokens ecosystem growth.

The network effect gap between BTC and BCH — measured by hashrate, daily transaction volume, institutional access, and liquidity depth — has widened since 2017, not narrowed.

Confirmation Signals

For Bitcoin Core’s layer-2 scaling thesis: Lightning routing reliability improving toward low single-digit failure rates at meaningful payment sizes; non-custodial Lightning adoption growing through improved wallet UX; Bitcoin covenant proposals (OP_VAULT, CTV) reaching developer consensus and activation.

For Bitcoin Cash’s on-chain payment thesis: CashTokens adoption driving meaningful transaction volume growth; BCH fee advantage translating to measurable merchant or remittance adoption in fee-sensitive markets.

What Would Invalidate Each

Bitcoin Core: Lightning routing failures at scale, concentrating practical payment use in custodial intermediaries and undermining the self-custody payment model. Sustained high fees pricing out low-value transactions with no viable non-custodial alternative. A successful deep chain reorganization would be catastrophic — though the cost barrier is extremely high.

Bitcoin Cash: A successful 51% attack exploiting the hashrate gap — this would directly undermine BCH’s payment use case and has partial precedent in earlier BCH reorganization events. Continued failure of CashTokens adoption to produce organic transaction volume growth would leave the upgrade without a demonstrated demand signal.

Timing Perspective

Now: For most capital allocation and infrastructure decisions, the BTC/BCH question is settled. BTC dominates on hashrate, liquidity, institutional access, and regulatory familiarity. BCH is a functional payment-focused network with lower fees and different security tradeoffs — not negligible, but occupying a distinct niche.

Next: Lightning Network UX and routing reliability are Bitcoin Core’s active development frontier for everyday payment use. CashTokens ecosystem growth is the equivalent active question for BCH. Both are 12–24 month windows worth monitoring.

Later: Whether Bitcoin’s base-layer fee market becomes structurally incompatible with low-value transactions — particularly if inscription demand recurs at scale — remains an open question. If that dynamic accelerates, the small-block tradeoff re-enters active debate with new empirical data.

What This Post Doesn’t Cover

This post covers the mechanism behind the 2017 split and the architectural tradeoffs that followed. It does not constitute a recommendation regarding either asset. Both chains are consequential inputs to any analysis of Bitcoin’s role in the financial system — each represents a different answer to the same question, and the evidence for which answer is correct continues to accumulate.

The fork happened. The architectural choices were made. The question of which tradeoffs matter most depends on what Bitcoin is for — and that depends on what actually gets built on top of each chain over the next several years.