digest
Short Summary
Main recommendation: Vitalik Buterin says Bitcoin's block size debate is a trade-off between making the chain easy to read (verify) and easy to write to (send transactions), and that both must stay accessible, so neither extreme (too large or too small blocks) is healthy. He describes himself as a "medium blocker" who favored the big-block side throughout the debate. The discussion traces the history of Bitcoin's block size limit and the disputes over it.
Key Points
- Buterin frames decentralization as requiring that both reading (running a node and verifying the chain) and writing (sending transactions) remain accessible, and calls them about equally important.
- If reading becomes too expensive, users must trust a few people to verify for them, who could change the rules without others' permission.
- If writing becomes too expensive, users move to highly centralized second-layer systems, which reduces decentralization and self-sovereignty.
- Bitcoin had no intended block size at first; its effective limit was 32 MB, set by the peer-to-peer message size. Satoshi lowered the limit to one megabyte in 2010, out of concern that larger blocks would be too hard to process.
- Compromise proposals (a 20 MB block proposal and the "2X" proposal) failed, and small blockers then rejected further increases.
- The small-block side mainly valued readability of the chain and maintaining the norm of never hard forking; Buterin states he completely disagrees, arguing soft forks are actually more coercive since they force disagreeing users to go along by default.
Details Worth Noting
- Concrete instructions: No step-by-step instructions, purchasing advice, or setup steps are given in this transcript. The only actionable position is Buterin's stated view that the chain must balance read and write accessibility, that hard forks are inherently risky, and that soft forks, in his view, are actually more coercive than commonly believed.
- A soft fork means any block valid under the new rules is still valid under the old rules, so old clients can still accept the chain. A hard fork requires updating code to stay on the chain.
- Segregated Witness, described as a soft fork, moves transaction signatures into a separate extension block, letting a block-size increase of roughly two megabytes pass without a hard fork. Buterin calls it a "devious trick" that is more of a hack than a clean solution.
- Positions within the big-block camp also varied, with proposals ranging from 4 MB to 8 MB up to 20 MB.
- Buterin acknowledges the main argument against big blocks: fewer people can run a node that verifies the chain, which increases centralization.
Bottom Line
The block size debate is, in Buterin's view, a balancing act between verifiability and usability, and the key disagreement was over whether increases should happen via soft forks, hard forks, or not at all.
