Banning fork advocacy created a consensus catch 22

The moderation policy on Bitcoin's main discussion forums — barring promotion of incompatible clients absent prior consensus — created a catch-22 that made consensus formation impossible: if you cannot campaign for a change until consensus exists, consensus for change can never form.

For (strongest version as argued): The argument proved compelling at the time, and the source says so. The main subreddit was the community's principal forum, and lobbying for change there was exactly how the large blockers envisioned change happening; banning promotion of their client did not end the campaign, it exiled it. The composition of the community made the wound deeper: these were people who had come to Bitcoin because their voice was ignored elsewhere — "this time it's our money... this time our voice will count" — so having their voices silenced inside Bitcoin produced fury out of proportion to a forum rule. And the exile had measurable structural costs: the migration to an alternative subreddit and friendlier forums produced confirmation-bias echo chambers on both sides, polarizing each until, as the source puts it, people could barely believe anyone could legitimately hold the opposing view — opponents had to be stupid, corrupt, or nefarious. On this account the moderation policy did not protect consensus; it manufactured the war's toxicity.

Against (strongest version as argued): The same source's retrospective cuts the other way: rereading the moderation post, it contained nuances not widely appreciated at the time, and "in many ways he was shown to be correct." The policy left two coherent paths open — create an avowedly separate coin, which requires nobody's agreement, or lobby for consensus before encouraging people to run an incompatible client. What it barred was the middle path: promoting software that would split the network while calling the result Bitcoin. Under the forum's reasonably clear rule that an incompatible client would create a new coin, that is an on-topic restriction, not viewpoint suppression — block size as a topic was not banned; a specific activation campaign was. The source also notes the large blockers themselves were muddled about which path they were on, unsure whether they wanted everyone's agreement or not. The catch-22 dissolves once advocacy and activation are separated: you can argue for a change anywhere and at any length; what you cannot do is bootstrap a contested rule change into effect through the venue serving the existing network.

Nuance: Two different indictments get merged: that the policy was illegitimate (contested — privately moderated venues set rules, and the rival forum applied its own) and that it was counterproductive (better evidenced in this source — the exile, radicalization, and polarization dynamics are documented consequences). The counterfactual is untestable: whether unrestricted promotion would have produced consensus or just a faster escalation is unknowable. And the framing assumes forum consensus is network consensus; the rest of the war suggests consensus was actually formed — and broken — in what software people ran and what the economy accepted, not in threads. See community-owned-governance-outlasts-founder-led-spaces for the adjacent question of who moderates the moderators.

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 source is unusually balanced on this point, recording both the argument's contemporary force and the author's later reassessment, but it remains one author's account and was not cross-checked against the primary record this session.

Common misstatements: "The main subreddit banned discussing bigger blocks" (the recorded ban was on promoting incompatible clients; how broadly it was enforced is part of the dispute, but the rule as stated was narrower). "Censorship is why big blocks lost" (a single-cause claim; the same source catalogs the camp's self-inflicted activation-design blunders in the same period). "Open forums owed the campaign neutrality" (both sides' venues were privately moderated with viewpoint effects; the disagreement is over which restrictions were legitimate). "The moderator opposed all change" (the recorded position was that hardforks require widespread agreement first — a sequencing rule, not a substantive veto).