Bitcoin Block Size Wars: The Scaling Debate Explained

The Fight That Defined Bitcoin

In the summer of 2017, Bitcoin almost became two different things, and in a way, it did. A years-long dispute over a technical parameter (how big each Bitcoin block should be) escalated into a full political crisis involving developers, miners, exchanges, businesses, and hundreds of thousands of ordinary users. The outcome shaped the Bitcoin protocol used today, gave rise to Bitcoin Cash, and settled, for now, a foundational question about how Bitcoin governs itself.

This is not just a piece of trivia. Understanding the block size wars teaches you something no whitepaper can: how Bitcoin actually works as a human institution, who holds power, and why the protocol has proven so resistant to change.

Background: What Is a Block, and Why Does Its Size Matter?

Bitcoin's blockchain is a chain of blocks. Each block contains a batch of transactions and is added to the chain roughly every ten minutes. Satoshi Nakamoto set the maximum block size at 1 megabyte (1 MB) in 2010, primarily as a temporary anti-spam measure to prevent someone from flooding the network with enormous blocks and overwhelming nodes.

At Bitcoin's earliest usage levels, 1 MB was enormous: blocks were mostly empty. But by 2015, as Bitcoin's user base grew, blocks began filling up. When a block is full, transactions have to wait in the mempool (the queue of unconfirmed transactions). Users who want faster confirmation must pay higher fees to incentivize miners to prioritize their transaction.

This created a real problem: Bitcoin was becoming slow and expensive for small transactions at moments of high demand. Critics argued that at this rate, Bitcoin could never serve as a global payment system.

The Core Tension

Two camps formed around fundamentally different visions for Bitcoin:

The Big Block Camp argued:

The 1 MB limit was always a temporary measure, not a sacred parameter
Increasing the block size was a straightforward technical fix
Low fees and high throughput were essential for Bitcoin to succeed as "peer-to-peer electronic cash"
Miners and businesses were the core stakeholders who should drive this decision

The Small Block Camp argued:

Larger blocks make running a full node more expensive, which centralizes the network
Centralization is a greater threat to Bitcoin than high fees
Layer 2 solutions (like the Lightning Network) were the correct scaling path
Soft forks (backwards-compatible upgrades) were safer than hard forks
No single constituency should be able to force a protocol change on users

What began as a technical debate turned into a war over Bitcoin's soul.

The Key Players

Understanding the block size wars requires knowing who was at the table, and who was not.

Core Developers (Bitcoin Core)

Bitcoin Core is the primary open-source software implementation for Bitcoin nodes. Its developers, including Greg Maxwell, Pieter Wuille, Luke Dashjr, and others, became the primary architects of the small block position. They proposed Segregated Witness (SegWit) as a soft-fork solution that would effectively increase block capacity without a hard fork.

The Big Block Advocates

Gavin Andresen (Satoshi's original successor as lead developer) and Mike Hearn championed larger blocks. In 2015, they released Bitcoin XT, an alternative Bitcoin client that would automatically increase block sizes to 8 MB if 75% of miners signaled support. It gained significant attention but failed to reach adoption thresholds. Hearn famously declared Bitcoin "a failed experiment" in a 2016 blog post and left the space.

Roger Ver, a prominent early Bitcoin investor and entrepreneur, became the most public face of the big block movement. Jihan Wu, co-founder of Bitmain (then the world's largest Bitcoin mining hardware manufacturer), also backed large blocks. His company's ASIC miners dominated the hash rate.

Miners

Miners produce blocks and were critical swing votes. A significant portion of global hash rate was concentrated in Chinese mining pools, many of which were aligned with Bitmain. This gave the big block side substantial leverage, or so it seemed.

Businesses and Exchanges

Coinbase, BitPay, and other Bitcoin businesses generally favored capacity increases, since high fees hurt their payment-processing use cases. The New York Agreement (NYA) of May 2017, a private meeting between exchanges, miners, and companies, produced a proposal called SegWit2x that would activate SegWit and later double the block size to 2 MB.

Node Operators and Ordinary Users

This is where the story gets interesting. Ordinary users running full nodes, wallets, hobbyists, individual holders, had no formal representation at the table. But they held a power that would prove decisive.

The Competing Proposals

Bitcoin XT (2015)

The first major attempt to increase block sizes via a hard fork. Would have raised the limit to 8 MB, then doubled it every two years. It failed to gain enough miner support and faded by 2016.

Bitcoin Classic (2016)

A more modest proposal to raise blocks to 2 MB. Again, failed to achieve sufficient adoption among miners and node operators.

Bitcoin Unlimited (2016 to 2017)

A more radical approach: remove the block size limit entirely and let miners and nodes negotiate the size through market forces. It gained significant miner support (at one point representing over 40% of hash rate) but suffered from software bugs and failed to launch.

Segregated Witness (SegWit)

Proposed by Pieter Wuille in late 2015, SegWit was a soft fork (backwards-compatible) that restructured how transaction data is stored in a block. By separating ("segregating") signature data (the "witness") from transaction data, SegWit:

Effectively increased block capacity to about 1.7 to 2 MB in practice (using a new "weight" unit)
Fixed a long-standing bug called transaction malleability, which was a prerequisite for the Lightning Network
Did not require all nodes to upgrade (soft fork)

SegWit required 95% miner signaling to activate under the original BIP 141 proposal, which miners (especially those aligned with Bitmain) blocked for over a year.

UASF: Users Take the Power

By mid-2017, the stalemate seemed unbreakable. Miners were blocking SegWit. Businesses wanted SegWit + a block size increase. Developers were holding the line on the soft fork. Then something unusual happened.

On March 12, 2017, a pseudonymous developer posted BIP 148, User Activated Soft Fork (UASF). The proposal was simple and radical: starting August 1, 2017, nodes running BIP 148 software would reject any block that did not signal SegWit support. No miner permission required.

The UASF concept revealed a truth that had been obscured throughout the debate: miners do not actually control Bitcoin's rules. Nodes do. Miners produce blocks, but nodes validate them. If enough economic nodes (exchanges, wallets, businesses) ran software that rejected non-SegWit blocks, miners who refused to signal would have their blocks orphaned: wasted work with no reward.

The UASF movement grew rapidly. The "UASF" hat became a symbol. Exchanges quietly signaled they would support SegWit on August 1. Miners realized their bluff had been called.

"The block size war was ultimately a test of whether Bitcoin's governance was miner-driven or node-driven. The UASF answered that question definitively." Jonathan Bier, The Blocksize War (2021)

The New York Agreement and SegWit2x

Facing the UASF deadline, a group of major Bitcoin businesses and miners convened in New York on May 23, 2017. The resulting SegWit2x agreement (also called "NYA") committed signatories to:

Activate SegWit immediately (via BIP 91, a miner-activated soft fork)
Hard fork to 2 MB blocks within six months

SegWit was activated on August 24, 2017, at block 481,824. The first part of the agreement succeeded.

The second part, the 2 MB hard fork known as "2x", was scheduled for November 2017. But opposition from node operators and developers was fierce. Critics argued:

A hard fork imposed by businesses and miners without broad community consent violated Bitcoin's social contract
The process lacked transparency and had bypassed normal Bitcoin development governance
No amount of corporate agreement could force node operators to upgrade

In early November 2017, the SegWit2x hard fork was called off when several key signatories withdrew support. The coalition had overestimated its power to direct Bitcoin's future. Node operators, not miners, not venture-backed companies, held the deciding vote.

The Bitcoin Cash Fork

Not everyone accepted this outcome quietly. On August 1, 2017, the same day BIP 148 activated, the big block faction executed a hard fork and launched Bitcoin Cash (BCH), with an 8 MB block limit.

Roger Ver became the most prominent advocate for Bitcoin Cash, at times controversially promoting it as "the real Bitcoin." BCH later forked again in 2018 into Bitcoin Cash and Bitcoin SV (Satoshi Vision, championed by Craig Wright, who claimed to be Satoshi Nakamoto).

Bitcoin Cash has continued to exist as a separate cryptocurrency. As of this writing, it trades at a fraction of Bitcoin's value and has a small fraction of Bitcoin's network security (hash rate). The market rendered its verdict on which chain users and investors preferred.

What SegWit Actually Enabled

SegWit was not just about capacity. By fixing transaction malleability, it unlocked a wave of protocol development:

The Lightning Network, which requires the malleability fix to function safely, became deployable. Today, the Lightning Network processes millions of transactions.
Schnorr signatures and Taproot (activated in November 2021) were built on the SegWit framework, adding privacy and smart contract flexibility.
Batching became more efficient, allowing exchanges and services to consolidate multiple payments into single transactions.

The small block path was not just about keeping blocks small. It was a deliberate bet that off-chain scaling (layers) would prove more powerful and more decentralized than simply inflating the base block size. That bet has largely played out as proponents argued.

The Governance Lesson

The block size wars produced no constitution, no formal governance structure, and no clear rulebook. What they revealed was Bitcoin's implicit power structure:

Node operators set the rules. Economic nodes, particularly exchanges and wallets that handle real funds, determine which version of the protocol the network actually follows. Miners can only produce blocks; nodes decide which blocks to accept.
Developers propose, they don't impose. Bitcoin Core developers have significant influence through their proposals and implementations, but they cannot force changes on anyone. Multiple competing implementations exist.
Consensus is slow and conservative by design. Bitcoin's high bar for change, requiring near-universal agreement across diverse, competing interests, is not a bug. It is why Bitcoin's rules are trustworthy. No single actor can unilaterally alter them.
Hard forks are exits, not coups. Any group can fork Bitcoin and create a new coin. But they cannot take Bitcoin with them. Bitcoin is defined by the network that chooses to follow it.
Corporate agreements cannot override users. The New York Agreement's collapse demonstrated that business coalitions, however well-funded, cannot commit node operators to a protocol change. The distributed nature of the network is its defense.

Why This History Still Matters

The block size wars are over, but their lessons are permanent:

On Bitcoin's properties: The episode confirmed Bitcoin's extraordinary resistance to change. This is either its greatest strength (no one can inflate the supply, change the rules, or capture the network) or its greatest weakness (it adapts slowly to new requirements), depending on your view. Bitcoin's consistent answer has been: the properties of hard money are worth the tradeoff.

On block space and fees: As Bitcoin adoption grows, block space remains deliberately scarce. Transaction fees are not a flaw. They are the long-run security model for miners once the block subsidy approaches zero. High fees during congestion are a feature, not a bug. Users who want lower fees can use the Lightning Network.

On altcoins: Dozens of Bitcoin competitors launched during the wars claiming to solve Bitcoin's scaling problem. Most have failed, been abandoned, or achieved minimal adoption. The coins that survived, including Bitcoin Cash, have not meaningfully displaced Bitcoin. High-throughput blockchains typically achieve their speed by sacrificing decentralization or security.

On governance more broadly: Bitcoin's governance model, messy, slow, resistant to capture, may be a feature that traditional institutions would do well to study. No CEO, no board, no government agency controls Bitcoin's monetary policy. The rules are enforced by a global network of individual nodes running open-source software.

Key Dates at a Glance

Date	Event
2010	Satoshi sets 1 MB block limit as anti-spam measure
Aug 2015	Bitcoin XT released, first major big block proposal
Dec 2015	SegWit proposed by Pieter Wuille at Scaling Bitcoin conference
Feb 2016	Bitcoin Classic released (2 MB proposal)
Mar 2017	BIP 148 UASF published
May 2017	New York Agreement, SegWit2x deal struck
Aug 1, 2017	Bitcoin Cash hard fork launches
Aug 24, 2017	SegWit activates on Bitcoin mainnet (block 481,824)
Nov 2017	SegWit2x (2 MB hard fork) called off
Nov 2021	Taproot activates, built on SegWit foundations

The Bitcoin Block Size Wars: How a Scaling Debate Shaped Bitcoin Forever