Compatibility asymmetry favors the tighter ruleset

In a contested rule change, the side whose rules are a strict subset holds a structural advantage: tighter-rules nodes reject the looser chain outright, while looser-rules nodes still accept the tighter chain — so if the tighter chain ever takes the proof-of-work lead, the looser chain can be reorganized out of existence.

For (strongest version as argued): The mechanics, as recorded from the Bitcoin Classic fight: larger-block nodes considered the smaller-block chain valid, while smaller-block nodes considered the larger-block chain invalid. If the smaller-block chain ever led on cumulative work, the larger-block chain could vanish — a wipeout — because the looser-rules nodes themselves would reorganize onto it. That one-way risk is tradeable: speculators could back the coin on the tighter-rules side and short the looser one, accelerating exactly the imbalance that triggers the wipeout. The activation designs of the era compounded the disadvantage: a 75 percent rolling-window threshold meant that at the moment the first oversized block appeared, roughly a quarter of the hashrate was still mining the tighter chain — so the tighter side never started from zero, and, in the source's judgment, regardless of the numbers on either side the likely outcome was a victory for the smaller blockers. The asymmetry was also asymmetrically understood: one small blocker's recorded counsel was to keep the issue quiet — never interrupt an enemy while they are making a mistake.

Against (strongest version as argued): The asymmetry is a consequence of chosen activation design, not a law of the system — and the source says so. The larger-block fork could have required its first post-activation block to exceed the old limit, making the split cleanly two-way and removing the wipeout exposure; the notes add that "the lesson was eventually learnt." The advantage also binds only in close contests: it matters when the tighter side retains meaningful hashrate and economic backing, and with genuinely overwhelming support for the looser rules the wipeout scenario never materializes — which is precisely what the large-block leadership believed about their own support at the time. So the mechanism decides close fights and punishes overconfidence; it does not by itself explain outcomes, and treating it as the war's cause competes with the social and design blunders the same source catalogs at length.

Nuance: This is the mechanism beneath Bitcoin's soft-fork-favoring upgrade culture (see soft-fork-vs-hard-fork): tightenings deploy compatibly, while loosenings must either clear the wipeout hurdle or engineer an explicit, permanent split — the path later persistent forks took with replay protection and independent difficulty rules (see bitcoin-cash-split, which the corpus records as a clean split for exactly those reasons). It also explains why headcount arguments kept misfiring during the war: the game is not symmetric majority rule, and a committed minority on the tighter side has outsized staying power. As a thesis about why the war ended as it did, it is one factor among several and the source's own coverage stops before the ending.

Sourcing: a single owner-research file — the owner's reading notes on The Blocksize War (Bier), a secondary account whose substantive coverage stops at February 2016 plus fragments — so INGEST_PLAYBOOK.md caps this at CONTESTED with confidence low. The mechanics described are checkable in principle against protocol behavior, but no primary or technical source was opened for this entry this session.

Common misstatements: "The fork with the majority just wins" (a looser-rules majority inherits one-way wipeout exposure; the mechanics are not majoritarian). "Soft forks cannot split the chain" (temporary splits happen when signaling outruns validation — see soft-fork-vs-hard-fork). "Bitcoin Cash disproves the wipeout risk" (it engineered a deliberately incompatible split with replay protection and its own difficulty adjustment precisely to escape the asymmetry — an exception that concedes the mechanism). "This was a secret weapon nobody understood" (the source records mitigations being discussed contemporaneously; the failure was on the activation designers' side).