Block size war
The 2015–2017 fight over Bitcoin's 1 MB limit that produced the first durable chain split.
Fork Wars is the long-form version of this article, with a dated timeline, a stance board for every major actor and the two books side by side. The wiki entry is the short version that the terminal can quote.[2][4]
Summary
For roughly two years, from 2015 to the summer of 2017, Bitcoin users argued over the 1 MB block size limit. One side wanted it raised so that on-chain payments stayed cheap; the other wanted it kept and capacity added through Segregated Witness and second layers such as Lightning[1]. The full dated history, with podcast quotes and listen links, is on Fork Wars[2].
Big-block proposals
Bitcoin XT (BIP101, Gavin Andresen and Mike Hearn) proposed 8 MB blocks doubling every two years until 2036; Bitcoin Classic settled on 2 MB; Bitcoin Unlimited dropped fixed numbers for "emergent consensus". None reached activation[1].
Resolution
In June 2017 Bitcoin ABC, led by Amaury Séchet, published a user-activated hard fork specification as a counter to BIP148[1]. Bitcoin Cash split on 1 August 2017; SegWit locked in on Bitcoin on 9 August and activated at block 481,824 on 24 August 2017[3]. Jonathan Bier, author of The Blocksize War, discussed the period on Bitcoin Takeover S16 E60[4].
Heard on Bitcoin Takeover
On S17 E35 (August 2026), Vinny Lingham argued: “We have the crypto ecosystem because the block sizes on Bitcoin was constrained.”[5]
References
- btkBitcoin Cash: The Big Block Breakaway (BTCTKVR: Forks!) [archived]
- btkFork Wars: the block size war timeline (Bitcoin Takeover) [archived]
- btkBitcoin: All the Hard Forks and Soft Forks (BTCTKVR: Forks!) [archived]
- episodeS16 E60: Jonathan Bier on Bitcoin Civil Wars & BitMEX Research▶ listen at 2:13:25timestamp transcript-derived, pending a listen [archived]
- episodeS17 E35: Vinny Lingham on what the block size limit produced▶ listen at 9:05timestamp transcript-derived, pending a listen [archived]
- primaryBitcoin commit a30b56e, 15 Jul 2010 (adds MAX_BLOCK_SIZE = 1000000) [archived]