Timechain Wiki

Block Size Wars - History

19 min read

The Block Size Wars were the 2015-2017 governance dispute over Bitcoin's 1MB block-capacity limit, pitting small-blockers (most Bitcoin Core developers and the layered-scaling track) against big-blockers (Andresen, Hearn, Ver, Jihan Wu and Bitmain, and various commercial businesses). Small-blockers argued capacity must remain bounded so commodity hardware can validate the chain, with scaling solved at higher layers; big-blockers argued capacity must scale via larger blocks to support everyday payments. The conflict escalated through BIP 101, Bitcoin XT/Classic/Unlimited, the broken Hong Kong Agreement, the SegWit2x New York Agreement, the August 1 2017 UASF that forced SegWit activation, and the Bitcoin Cash fork the same day. The small-blocker position prevailed; SegWit2x was canceled before activation. The governance lesson — that economic-node consensus, not miner or developer consensus, ultimately governs Bitcoin — is the conflict's most consequential output. The canonical chronicle is Jonathan Bier's The Blocksize War (The Blocksize War (book) - Jonathan Bier); this note synthesizes the governance lessons rather than retelling the chronicle.

Why this note matters

The Block Size Wars are the most consequential governance event in Bitcoin’s history, mattering for three reasons.

First, the conflict established the operational mechanism for Bitcoin governance. Satoshi’s withdrawal had left the project without formal decision-making authority, and 2014-2015 ran on untested informal-consensus norms. The wars stress-tested that framework and produced the operative rule: economic-node consensus is the binding constituency, miners merely extend the chain economic nodes accept, and developers merely propose changes economic nodes choose to run.

Second, the conflict resolved Bitcoin’s scaling architecture. The small-blocker outcome — bounded on-chain capacity plus layered scaling via Lightning, sidechains, and Taproot — has been the operational path since 2017.

Third, the conflict demonstrated protocol resilience to coordinated attack. The big-blocker coalition included majority hashrate at multiple points (Bitmain and adjacent Chinese mining infrastructure), major commercial businesses (Coinbase, BitPay), and prominent post-Satoshi figures (Andresen, Hearn). That the small-blocker position prevailed despite the coalition’s apparent strength is empirical evidence that economic-node consensus is hard to capture even by well-resourced coalitions.

The detailed chronicle lives in The Blocksize War (book) - Jonathan Bier; this note synthesizes the governance lessons.

The substantive dispute

The Block Size Wars dispute was substantive, not merely tribal. Both sides had coherent positions; reading the dispute as a tribal conflict misses the actual content.

The small-blocker position. Bitcoin’s decentralization rests on the ability of ordinary users to run full validation nodes on commodity hardware. A full node validates every transaction and every block; the validation requirement determines what hardware is needed. If the on-chain throughput is bounded such that ordinary commodity hardware can validate the chain in real-time, validation is decentralized; if throughput is unbounded such that validation requires specialized infrastructure, validation migrates to a small set of professional operators and the protocol’s effective governance migrates to those operators. The small-blocker position holds that this hardware-bound decentralization is constitutive of Bitcoin’s security model and cannot be compromised without changing what Bitcoin is. Scaling must therefore happen at higher layers — Lightning Network, sidechains, statechains, federations — where the security model can be different from base-layer Bitcoin’s. The base layer is for settlement; the higher layers are for payments.

The small-blocker position drew on a substantial intellectual tradition: the cypherpunk emphasis on individual sovereignty and verification (treated in Cypherpunk movement), the Mengerian-monetary-theory emphasis on hard-money properties (treated in Hard money vs fiat money), and the engineering-conservative tradition of preserving working systems against speculative changes. The position was articulated by Bitcoin Core developers (Gregory Maxwell, Pieter Wuille, Adam Back, Eric Lombrozo, others) and substantively endorsed by the broader cypherpunk-internal community.

The big-blocker position. Bitcoin was designed as electronic cash for everyday transactions; the 1MB block size limit was a temporary anti-spam measure Satoshi had introduced in 2010 and was always intended to be raised. Limiting on-chain capacity defeats Bitcoin’s payment-infrastructure value proposition and pushes users toward off-chain settlement that doesn’t preserve Bitcoin’s core properties. Lightning Network and layer-2 solutions are speculative; the proven path is to scale on-chain. Specialized full-node hardware is a reasonable trade-off given that ordinary users can use SPV clients (treated in section 8 of the whitepaper) for verification; the validation-decentralization concern is overstated.

The big-blocker position drew on a different reading of Bitcoin’s purpose: Bitcoin-as-payment-infrastructure rather than Bitcoin-as-monetary-asset. The position was articulated by Gavin Andresen (the post-Satoshi-handoff lead developer), Mike Hearn (Bitcoin Foundation board member and early-era developer), Roger Ver (early Bitcoin businessman and the most-prominent commercial advocate), Jihan Wu (Bitmain founder, with substantial mining-pool influence), and various commercial Bitcoin businesses (Coinbase, BitPay, the early-2010s consumer-Bitcoin layer).

The genuine substantive content. Both positions had legitimate technical content; neither was simply wrong. The big-blocker concern about user-experience and payment-throughput was real; the small-blocker concern about validation-decentralization was real. The fundamental disagreement was about which property of Bitcoin was non-negotiable: payment-utility or decentralization-of-validation. The small-blocker position held that decentralization was non-negotiable and payment-utility could be solved at higher layers; the big-blocker position held that payment-utility was non-negotiable and decentralization could be partially compromised to preserve it.

The historical-empirical resolution: the small-blocker position prevailed. The pro-Bitcoin reading of why is that the small-blocker concern was load-bearing for Bitcoin’s distinctive value proposition (sound money requires decentralized validation; without decentralized validation, Bitcoin’s properties degrade toward conventional digital payment systems) and the big-blocker concern was solvable by alternative means (Lightning has substantially delivered on the payment-throughput requirement). The big-blocker position read Bitcoin as a payment infrastructure that needed to compete with Visa; the small-blocker position read Bitcoin as monetary infrastructure that needed to compete with central banking. The latter framing has been substantively vindicated.

The chronicle, compressed

A compressed timeline; the detailed chronicle is in The Blocksize War (book) - Jonathan Bier.

2015 — opening positions. Gavin Andresen proposed BIP 101 (June 2015), specifying a block-size increase from 1MB to 8MB followed by a doubling every two years. The proposal did not gain consensus; it became the basis for Bitcoin XT (released August 2015), the first alternative-implementation forking attempt. Bitcoin XT did not achieve activation; the threshold (75% miner signaling) was never met. The 2015 Scaling Bitcoin conferences (in Montreal and Hong Kong) attempted technical-community resolution; the conferences clarified positions but did not produce consensus.

Early 2016 — escalation. Bitcoin Classic (released January 2016) proposed a more-modest 2MB block-size increase. The proposal had broader commercial support than Bitcoin XT but still did not achieve consensus-activation. Mike Hearn declared Bitcoin “failed” in a January 2016 medium post and departed for Google’s R3 blockchain consortium; the departure was a substantial Bitcoin-community event at the time but in retrospect was the first clean break of a big-blocker from the project rather than a meaningful structural blow. Bitcoin Unlimited (February 2016) proposed making block size a variable rather than a constant, with miners signaling preferred limits. Each successive proposal moved further from technical consensus.

February 2016 — the Hong Kong Agreement. A meeting between Bitcoin Core developers and major Chinese mining-pool operators in Hong Kong produced an agreement: the developers would deliver SegWit (a soft-fork capacity increase) and would commit to working on a subsequent 2MB hard-fork; the miners would refrain from running alternative implementations and would support SegWit activation. The agreement was substantially broken: the miners did not support SegWit activation when it became available; the developers’ position on the subsequent hard-fork commitment became contested. The Hong Kong Agreement’s failure-to-implement is one of the most-cited specific moments in the broader conflict.

Mid-2016 to early 2017 — SegWit deadlock. SegWit (Segregated Witness, BIP 141) was a technically-sophisticated soft-fork capacity-increase developed by Bitcoin Core that increased effective block capacity to roughly 2-4MB while introducing transaction-malleability fixes and enabling subsequent Lightning Network deployment. SegWit was activation-ready by late 2016 but required miner-signal threshold (95%) to activate. Mining-pool operators substantially declined to signal SegWit, with the dispute increasingly framed as a small-blocker-vs-big-blocker proxy fight rather than a technical-merits matter.

May 2017 — the New York Agreement / SegWit2x. A meeting in New York between major Bitcoin businesses (Coinbase, BitPay, Bitmain, Digital Currency Group, and others) produced the SegWit2x agreement: SegWit activation in August 2017 followed by a 2MB hard fork in November 2017. The agreement was negotiated without substantive Bitcoin Core developer participation; the Core community substantially rejected the agreement’s legitimacy. SegWit2x became a signaling-vehicle independent of either of the underlying technical changes; it was used as a coordination mechanism more than as a technical roadmap.

August 1, 2017 — UASF and the BCH fork. Two simultaneous events. First, BIP 148 (the User-Activated Soft Fork) activated, forcing SegWit activation through economic-node coordination rather than miner signaling: nodes running BIP 148 would reject blocks that did not signal SegWit support after August 1, creating a coordination point that miners had to either accept (signaling SegWit) or refuse (forking off the network). The mining-pool operators substantively accepted the forcing function and SegWit signaled-activated. Second, the big-blocker coalition (Roger Ver, Jihan Wu, others) executed a hard fork creating Bitcoin Cash (BCH) at block 478,558, with an 8MB block size limit and the explicit positioning as the “real Bitcoin” continuing the big-blocker design philosophy. The BCH fork is treated in Bitcoin forks - History.

November 2017 — SegWit2x canceled. The remaining SegWit2x agreement (the 2MB hard-fork scheduled for November 2017) lost commercial-coalition support over the second half of 2017 as it became clear the fork would not have user-base consensus. The 2x hard fork was canceled on November 8, 2017, days before its scheduled activation. The cancellation was the formal endpoint of the Block Size Wars; the small-blocker position had won.

The UASF as historical event (August 1, 2017)

The User-Activated Soft Fork — BIP 148, deployed by economic nodes refusing to accept blocks that did not signal SegWit support after August 1, 2017 — was the decisive moment that resolved the conflict. Faced with the economic-node coordination, miners signaled SegWit and activation followed. The empirical demonstration that economic nodes could overrule miner reluctance was the conflict’s most consequential single historical fact, and it remains the canonical reference event when later governance questions arise.

For the conceptual treatment of how Bitcoin protocol upgrades happen — the role of economic-node consensus, soft-fork activation mechanics, the BIP process, rough-consensus norms, and the broader governance theory the UASF illustrated — see How upgrades happen.

What the conflict resolved, historically

Three empirical outcomes that shaped subsequent Bitcoin history:

  • SegWit activated and Bitcoin’s small-blocker design philosophy held. The conflict’s substantive technical question was resolved in favor of bounded on-chain capacity plus layer-2 scaling (Lightning, Taproot enabling more-efficient on-chain transactions). The 2024-era Bitcoin operational landscape is downstream of this resolution.
  • The big-blocker coalition departed to Bitcoin Cash on August 1, 2017. The dissenters were able to maintain their preferred protocol design on a separate chain. The BCH chain has continued to operate as a separate experiment since 2017; its market trajectory and the broader fork-history pattern are treated in Bitcoin forks - History.
  • Economic gravity and brand identity stayed with the original chain. Across BCH, BSV, and successor forks, market capitalization, developer mindshare, and user adoption substantially remained with Bitcoin. As of 2026, Bitcoin holds ~95%+ of cumulative-Bitcoin-derivative market capitalization; the empirical pattern is treated analytically in Bitcoin forks - History.

The roles and trajectories of key figures

Several figures from the Block Size Wars era have had subsequent trajectories worth tracking.

Gavin Andresen. The post-Satoshi-handoff lead developer. Andresen’s big-blocker position during the Wars was substantive; his subsequent 2016 endorsement of Craig Wright as Satoshi (treated in Satoshi Nakamoto) was a separate episode that substantially damaged his standing in the community. Andresen has been largely inactive in Bitcoin development since 2017; his historical role as the Satoshi-handoff figure is preserved but his contemporary engagement is minimal.

Mike Hearn. The Bitcoin Foundation board member and early-period developer. Hearn declared Bitcoin “failed” in his January 2016 medium post and departed for Google’s R3 blockchain consortium. The departure was treated by big-blockers as evidence of structural failure; the small-blocker reading was that Hearn’s exit was just one prominent figure choosing to disengage. The post-2017 outcome has substantially validated the small-blocker reading: Bitcoin has thrived since Hearn’s departure, demonstrating that the project did not depend on Hearn’s continued participation.

Roger Ver. The most-prominent commercial big-block advocate. Ver led the post-fork Bitcoin Cash community advocacy and has remained substantively committed to the big-blocker position through 2025. Ver’s relationship with the Bitcoin community is essentially adversarial as of 2025; his role in BCH advocacy and various adjacent controversies has cemented his position as outside the Bitcoin community proper.

Jihan Wu and Bitmain. The Chinese mining-pool operator whose pool-coordination authority was the central mining-side leverage of the big-block coalition. Bitmain’s post-2017 trajectory has been substantial: the company remains a major ASIC manufacturer; the Chinese mining-ban of May 2021 disrupted its operations but did not destroy it; the company’s contemporary positioning is substantially less politically-loaded than its 2015-2017 positioning was. The 2021 mining-geography shift to North America and other jurisdictions has reduced any single mining operator’s coordination authority below the levels that would replicate the 2015-2017 Bitmain influence.

Gregory Maxwell, Pieter Wuille, Adam Back, Eric Lombrozo. Bitcoin Core developers who articulated the small-blocker technical position. Maxwell, Wuille, and Back remain centrally involved in Bitcoin development through 2025; Lombrozo has reduced engagement but the broader developer-community position has held. The post-2017 development trajectory — Taproot in 2021, the various Lightning Network and adjacent protocol enhancements, the ongoing protocol-development conservative-default — is substantially their legacy.

Bitcoin businesses (Coinbase, BitPay, Digital Currency Group). The commercial-businesses coalition initially aligned with the big-block position substantially repositioned by late 2017. Coinbase, in particular, transitioned from SegWit2x signatory to small-blocker-aligned as the November 2017 fork timeline approached and as the user-base consensus became clear. The post-2017 commercial-business posture has been substantially aligned with the small-blocker resolution; the New York Agreement’s commercial signatories have largely either repositioned or exited the relevant decision-making roles.

Counter-arguments and tensions

The “small-blockers were ideological purists who ignored user needs” critique

A version of the big-blocker retrospective: the small-blockers were ideological purists who privileged decentralization-of-validation over user-experience, with the result that ordinary users were pushed toward custodial alternatives (exchanges, ETFs, layer-2 services that re-introduce some trust assumptions) that defeat Bitcoin’s original value proposition.

Response: Partially correct as a tension but ultimately misframes the resolution. The decentralization-of-validation property is genuinely load-bearing for Bitcoin’s monetary properties; without it, Bitcoin becomes structurally similar to other digital-payment systems and loses its distinctive monetary value. The custodial-alternatives concern is real but mitigable: users who want self-custody can self-custody (with the post-2017 hardware-wallet infrastructure substantially better than the 2015-era options); users who choose convenience can use custodial services with the understanding that this re-introduces counterparty risk (the lesson Mt. Gox taught). The user-experience concern is solvable by improved layer-2 tooling (Lightning has substantially delivered on this) and improved self-custody tooling. The decentralization-of-validation concern, by contrast, is not solvable by alternative means — it must be preserved at the base layer or it is lost.

The “the conflict was driven by personal-and-financial interests, not principles” reading

Some retrospective treatments have framed the Block Size Wars as primarily a conflict of personal-and-financial interests dressed up in technical-philosophical clothing. The big-blocker coalition included substantial financial interests (mining-pool operators with capital invested in larger-block infrastructure; Bitcoin businesses with consumer-payment-throughput dependencies); the small-blocker coalition included intellectual-prestige investments and developer-employment interests.

Response: The interests-reading has some force, but it understates the substantive technical content of both positions. The technical arguments were substantive on both sides; the interest-alignments shaped which side individuals took, but the technical content was not merely a rationalization. The honest framing is that the conflict had both substantive-technical content and interest-driven coalition dynamics, and that the substantive-technical content drove the eventual resolution (the small-blocker position was technically right about which property of Bitcoin was load-bearing) more than the interest-coalition strength did.

The “the conflict damaged Bitcoin’s political-economy permanently” concern

A skeptical reading: the Block Size Wars produced lasting damage to Bitcoin’s political-economy — the loss of Gavin Andresen as a continuing figure, the alienation of substantial commercial-business coalition, the persistent BCH-and-successor-chain ecosystem operating as a continuing critique-and-confusion vector, the slowing of subsequent protocol-development as the community absorbed the conservative-default lessons of the conflict.

Response: The concern has some force as a descriptive matter — the conflict did produce political-economy costs. But the alternative — capitulating to the big-blocker position to preserve the political-economy of the broader coalition — would have produced a different and likely worse outcome: a Bitcoin with compromised decentralization-of-validation, a structurally-altered monetary asset that would have been substantially less distinct from competing digital-payment systems. The political-economy costs of the conflict were real; they were also the necessary price of preserving the protocol’s distinctive properties. The contemporary 2024-2026 Bitcoin political-economy is substantially stronger than it would have been with the big-blocker resolution; the costs paid were worth paying.

The “the lesson generalizes to all future contentious changes” framing

Bitcoin-community participants sometimes generalize from the Block Size Wars to a broader principle: that contentious protocol changes should be rejected by-default and that the protocol’s conservatism should be increased over time. The framing is sometimes applied to subsequent governance questions (the various proposed soft forks, the BIP-300/Drivechains discussion, the broader pace of protocol-development).

Response: The generalization is partially load-bearing but should be held with care. The Block Size Wars lesson is specifically that changes that compromise decentralization-of-validation should be rejected; the lesson does not generalize to all-conservative-defaults across all decisions. The Taproot upgrade (2021) demonstrated that the community can still ship substantial protocol improvements when the broad consensus is present; the lesson is not “ship nothing” but “ship things that preserve the load-bearing properties.” Generalizing the lesson too far risks producing genuine technical stagnation. The honest position is that the lesson is specific to the decentralization-of-validation question and should be applied to other questions with appropriate care.

Open questions for further development

  • Was the New York Agreement’s failure a victory or a missed opportunity? Reasonable observers disagree. The small-blocker reading is that the NYA was a coalition-coup attempt that the broader community correctly rejected; the big-blocker reading is that the NYA was a workable compromise that ideological-purists scuttled.
  • How robust is the economic-node-consensus governance mechanism to genuinely-coordinated attack? The UASF demonstrated robustness against a coalition that was strong-but-not-fully-coordinated; whether the mechanism would survive a more-coordinated attack remains structurally untested. The open question of whether Wall Street accumulation eventually exerts governance influence (see Wall Street capture of Bitcoin) is conceptually downstream of this concern.
  • Should subsequent governance questions be evaluated using the same UASF-style mechanism? The 2021 Taproot activation used a different mechanism (Speedy Trial); the 2024-onward governance discussions have not produced a uniform pattern. The mechanism question remains partly unresolved.
  • What is the appropriate Bitcoin-community-cultural posture toward Bitcoin Cash and other big-blocker successor chains? The dismissive-and-adversarial posture has been the operational norm; a more-equanimous posture (acknowledging BCH as a coherent experiment that the market has rejected) might serve the project’s broader political-economy better.

Canonical sources for this note

Primary source

Primary documents from the conflict

  • The Bitcoin Improvement Proposals (BIPs) corresponding to the various proposed changes: BIP 101 (Andresen 8MB proposal), BIP 109 (Bitcoin Classic 2MB proposal), BIP 141 (SegWit), BIP 148 (UASF), BIP 91 (the SegWit2x activation-coordination mechanism), and adjacent BIPs.
  • The Hong Kong Agreement and the New York Agreement original-text documents — preserved in various Bitcoin-community archives.
  • Bitcoin Core repository commit history (2015-2017) — the technical-development primary source.
  • The various Scaling Bitcoin conference proceedings (Montreal 2015, Hong Kong 2015, Milan 2016, Stanford 2017) — preserved in conference archives.
  • Mike Hearn, “The resolution of the Bitcoin experiment” (Medium, January 14, 2016) — the canonical big-blocker exit declaration.
  • The BitcoinTalk forum archives across 2015-2017 — substantial community-discussion primary source.
  • The r/Bitcoin and r/btc subreddit archives across 2015-2017 — the platform-based community discussion (with the explicit political-content moderation differences between the two communities being itself part of the historical record).

Secondary and historical treatments

  • Saifedean Ammous, The Bitcoin Standard (2018) — engages the Block Size Wars in Chapter 8 and adjacent discussion.
  • Nathaniel Popper, Digital Gold (2015) — pre-dates the resolution but engages the early dispute.
  • Pete Rizzo’s Bitcoin Magazine historical pieces — substantial post-resolution retrospective treatment.
  • Various technical-developer retrospectives — Gregory Maxwell, Pieter Wuille, Eric Lombrozo, and others have written substantive retrospective material.

Graph View

Backlinks