Censorship Resistance Why this is the load-bearing property Censorship resistance isn't one feature among many in Bitcoin — it's the property that makes every other property meaningful. Scarcity means nothing if a transaction can be blocked. Self-custody means nothing if your transaction never confirms. It's upstream of everything. The question is: does BIP-110 actually threaten it, and how severely? The direct threat: protocol-level transaction discrimination For the first time in Bitcoin's history, BIP-110 would encode into consensus rules a distinction between transaction types based on their content. Not their fee, not their size, not their validity — their content. This is a qualitative shift, not a quantitative one. Bitcoin has always been content-neutral at the protocol layer. A node doesn't care if you're sending value to a dissident journalist in Belarus or buying coffee. BIP-110 breaks that neutrality. Once broken, the question isn't whether content discrimination is acceptable — that question has been answered yes — the question becomes who decides what content is acceptable, and when. That's a fundamentally different Bitcoin than the one that exists today. The regulatory capture vector — the most underappreciated risk This is where it gets serious for a sovereignty-oriented holder. Consider the sequence: BIP-110 passes, establishing that protocol rules can discriminate by content Governments observe that a relatively small group of developers and miners can change what Bitcoin accepts A regulator — FinCEN, ECB, any Financial Intelligence Unit — issues guidance that "mixing transactions" or "privacy-enhanced outputs" constitute money laundering facilitation They pressure exchanges, custodians, and large mining pools to only run nodes that enforce the new rule A new BIP gets proposed — not by cypherpunks, but by compliance-driven actors — restricting CoinJoin, Wasabi wallet outputs, or Lightning channel opens that obscure amounts This isn't hypothetical. It's the exact playbook used against Tornado Cash on Ethereum. The critical difference today is that Ethereum's community had already normalized protocol-level intervention. Bitcoin hasn't — yet. BIP-110 would be the first normalization event. The soft fork framing makes it worse, not better BIP-110 proponents argue it's "just a soft fork" — backward compatible, less disruptive than a hard fork. But the soft fork framing is precisely what makes the censorship risk more insidious: A hard fork requires the entire network to consciously choose a new chain. It's visible, contested, and self-limiting — the community can reject it. A soft fork tightens rules without breaking old nodes. Old nodes see BIP-110 blocks as valid. The change slips in with less friction, less debate, and less visibility to ordinary users. For a rule change that introduces content discrimination, lower friction is a feature for bad actors, not a safety property. The 55% activation threshold compounds everything Standard Bitcoin soft forks have historically required 95% miner signaling — a near-unanimity threshold designed to ensure changes have overwhelming consensus before activating. BIP-110 proposes 55%. That means a coordinated group controlling just over half the hashrate — potentially two or three large mining pools acting together — could permanently alter Bitcoin's content neutrality. Those pools are geographically concentrated, subject to national jurisdiction, and in some cases already operating under regulatory frameworks. A government that controls or pressures enough hashrate doesn't need to 51% attack Bitcoin to steal funds — it just needs to push a "compliance fork" through at 55%.