Skip to content
← Corpus

Claim

Small block position was vindicated

CONTESTEDmedium confidencenode policy

Verified as of 2026-07-22. Not re-checked since.

History has vindicated the small-block position in the block size war: keeping blocks small and node costs low was the correct call.

For (strongest version as argued): The technical core of the small-block case — that propagation friction does not self-limit block size and that validation cost is the decentralization budget — held up under formal analysis and fifteen years of operation. The big-block roadmap's predictions failed concretely: the forks that raised block size lost essentially all economic weight, the feared fee-driven exodus never materialized, and layered scaling (the small-block prescription) shipped and works. Bitcoin retained a globally distributed full-node base precisely because the resource bar stayed low.

Against (strongest version as argued): Vindication is being claimed on a test that was never run: the big-block chains failed amid hostile market and social dynamics, which does not prove moderate on-chain scaling would have failed on Bitcoin itself. Meanwhile the small-block equilibrium produced its own unresolved costs — fee unpredictability, custodial concentration as ordinary users price off-chain, an L2 stack that remains harder to use self-sovereignly than promised — and the current data-embedding fights show "keep validation cheap" did not settle what blocks are for. Selective scorekeeping also flatters the winners: small-block-era claims about imminent fee-market maturity look no better than big-block claims about propagation.

Nuance: Separable sub-claims get bundled: (1) the incentive analysis against unbounded blocks — strongly supported; (2) the governance verdict that contentious hard forks fail — supported by the observed outcomes; (3) the economic verdict that the low-throughput path maximized Bitcoin's value and decentralization — a counterfactual nobody can test. Debaters citing the war as precedent for today's filtering disputes should be pressed on which sub-claim they mean; notably, both sides of the current data debate claim the war's mantle.

Common misstatements: "Big blocks were technically impossible" (they were technically possible; the dispute was about incentive and centralization consequences). "SegWit didn't increase capacity" (it did — effective block weight roughly doubled potential throughput). "The war ended debate about block space" (the OP_RETURN and data-embedding disputes are recognizably the same argument in new form, as the source events themselves observe).

Sources (3)

  1. 1.Satoshi Unmasked The Peter Todd Live Interview with RizzoArchived recording, transcript held in-house (not published)

    The vindication claim asserted flatly ("we nailed this... absolutely correct") alongside the concession that pool centralization, a core small-block concern, remains unsolved

  2. 2.The OP_RETURN Saga Continues Live at PubKey NYC Main speakers Arbedout Thomas Pacchia and Andrew NewmanArchived recording, transcript held in-house (not published)

    The block size war invoked as precedent by both filtering camps - each claiming to be its true heir

  3. 3.the-blocksize-wars-book-notesIn-house research notes (not published)

    The Blocksize War (Bier) — corroborates only the governance sub-claim (sub-claim 2 in the Nuance) via the wipeout asymmetry and activation-design record showing why contentious loosening forks fail, and adds one concession to the Against side ("large blockers have been shown to be mostly correct" that 2015 on-chain merchant adoption exceeded lightning adoption as of the book's writing); the notes stop at February 2016, before the war's outcome, and carry nothing on the economic-counterfactual sub-claim — gap flagged

Related entries