BIP-110: Anatomy of a Dead Soft Fork

Support rate: 2.64%. Activation threshold: 95%. The math is terminal. BIP-110's mandatory signal window inches closer—a deadline without consensus. This is not a protocol upgrade. It is a governance grenade. Context. BIP-110, formally "Reduced Data Temporary Softfork," limits OP_RETURN output size and witness data in Bitcoin transactions. Target: Ordinals inscriptions. Proponents call it spam reduction. Opponents call it censorship. The technical change is trivial—a parameter adjustment. The activation mechanism is not. The proposal uses a variant of BIP-8: if 95% of blocks signal readiness within a window, the fork activates. If not, at a predetermined height, upgraded nodes begin rejecting any block that does not include a version bit signal. This is enforcement before consensus. A binary ultimatum. Core. Let me walk through the mechanics. Current signaling: 2.64%. Source: independent node monitoring. Only a handful of small miners signal. Ocean, a pool with ideological roots in "pure Bitcoin," is among them. Major pools—Foundry, Antpool, F2Pool—remain silent. Foundry's voting is delegated: each customer's average hash rate determines the pool's aggregate signal. A customer who opposes limits cancels out one who supports. The result is a stalemate. This is a structural failure. A 2.64% support rate means the fork cannot activate. But the mandatory window will still open. At the predetermined height, upgraded nodes will enforce the new rules: reject any block lacking the version bit signal. This creates a schism. The main chain continues under old rules with nearly 100% hash rate. The minority chain—blocks that do signal and are accepted by upgraded nodes—will have negligible power. It will orphan quickly. But the gesture remains. I have seen this pattern before. In 2017, I submitted a gas optimization PR to 0x Protocol. The core team rejected it as "premature optimization." The same label applies here. BIP-110 optimizes for a problem the network does not recognize as urgent. The cure is worse than the disease. s heart. Now, the technical assessment. BIP-110 is a micro-innovation—a parameter change. It addresses a transient condition: fee spikes from inscriptions. Compare to SegWit or Taproot, which enabled new functionality. BIP-110 only restricts. It is backward-looking. Its security assumption relies on miner honesty during the signaling window. But when some miners refuse to signal, the mandatory window creates a credibility crisis. The network is asked to choose between two rulesets without clear majority. Risk analysis: low probability, medium impact. If the mandatory window triggers enforcement, we see a minority chain for a few hours. Exchanges may temporarily halt BTC deposits. The market won't care. Price impact: near zero. This is an inside-baseball event. But the governance precedent is dangerous. Mandatory windows were designed for widely supported forks. Here, they are being used to force a contentious change. That is not consensus. It is coercion. In 2022, I modeled Terra's algorithmic stability and predicted the de-peg three weeks before the collapse. The feedback loop was clear. BIP-110's mandatory window introduces a similar feedback loop: it forces a binary choice that the network is not ready to make. The result: paralysis, not progress. Contrarian. The bulls—those supporting BIP-110—have a point. Large inscriptions degrade user experience. Block space is a public resource; unchecked data growth increases costs for everyone. The market itself cannot always correct externalities. Ordinary users are priced out during inscription booms. A technical limit may be the only way to restore balance. They are also correct that mandatory windows are not new. BIP-8 was used for Taproot activation. But Taproot had overwhelming community support before the window. BIP-110 does not. The difference is consensus—real, organic consensus versus manufactured ultimatums. Where the bulls err is in ignoring the slippery slope. Once you allow a soft fork to restrict data based on content type, next it becomes transaction patterns, then script versions. The line between spam and expression is arbitrary. The precedent is dangerous. The bulls got the problem right but the solution wrong. s heart. Takeaway. BIP-110 will not activate. The math is too far off. Focus on the signal rate: if it rises above 5% in the next two weeks, something shifted—likely a major pool flipping. If it stays below 2%, the proposal is dead. The real signal is not the fork; it is the governance failure. This failure reveals a deeper inertia. Bitcoin's soft fork mechanism resists change even when change is needed. For the Ordinals debate, this is round one. Expect more BIPs. Expect the same stalemate. The network's greatest strength—conservatism—is also its greatest weakness. Based on my experience auditing contract architectures, I know that premature optimization is the enemy of robust systems. BIP-110 is premature. The network will reject it, quietly and permanently. s heart.