BIP-110's Forced March: When 3% Miner Support Meets a 100% Node Mandate

Miner support for BIP-110's mandatory signaling phase sits below 3%. That is not a rounding error. It is a declaration of war between the two pillars of Bitcoin's consensus: the nodes that enforce the rules and the miners that produce the blocks. I have spent the better part of a decade auditing consensus-layer upgrades, and I have never seen a forced activation with such a tiny base of production-level buy-in. This is not a soft fork. It is a governance stress test with the network's integrity suspended in the balance. Let me set the stage. BIP-110, proposed years ago, introduces a mechanism where after a certain block height, nodes must reject any block that does not carry a specific version signal. In theory, this forces miners to upgrade if they want their blocks accepted. In practice, it creates a binary choice: either the miners comply, or the network splits into two competing views of the ledger. The proposal was never meant to be the final word on Bitcoin's activation protocol—BIP-9 later won the day with its 95% hash-rate threshold and miner-friendly signaling window. But BIP-110 has resurfaced now, entering its mandatory signaling phase with a staggering lack of miner endorsement. To understand why this matters, we need to decompose the architecture. Bitcoin's soft fork activation is a layered system. Miners signal readiness via version bits in coinbase transactions. Nodes then tally those signals over a difficulty period. Under BIP-9, the fork activates only when 95% of blocks carry the signal. Under BIP-110, the trigger is not a percentage but a deadline: after a fixed date, nodes simply refuse blocks without the signal, regardless of miner support. This is a nod to the User-Activated Soft Fork (UASF) philosophy—the belief that node operators, not miners, hold the ultimate authority to define protocol rules. The problem is that node operators are not the ones producing blocks. Miners are. And when 97% of the hash rate either ignores or opposes the signal, the network faces a fundamental misalignment between rule enforcement and rule execution. Here is the technical trade-off. BIP-110's forced signaling reduces the attack surface of miner collusion—if miners cannot block a fork by refusing to signal, the upgrade can proceed regardless. But the cost is a potential chain split. When the signaling deadline hits, a node running BIP-110 will orphan any block without the signal. If the majority of miners continue to produce non-signaling blocks, those blocks will be rejected by BIP-110 nodes, but accepted by nodes that do not enforce the rule. Two chains emerge. One chain, with the upgraded rules, stalls because it has only 3% of the hash rate, producing blocks very slowly. The other chain, with the old rules, continues normally. The result is not a clean fork but a lopsided one where the intended upgrade becomes a minority chain with extremely low security. This is not a hypothetical. I have analyzed similar forced-activation scenarios in my audits of other L1 networks, and the outcome is almost always a retreat to a fallback plan—or a prolonged period of confusion and value destruction. Now, the contrarian angle. The conventional narrative paints this as a failure: the developers overreached, the miners voted with their hash power, and the proposal is doomed. But that interpretation misses the forest for the trees. BIP-110's mandatory signaling, even with 3% miner support, is a deliberate test of the UASF thesis. It is a probe to see whether nodes can enforce a rule change without miner cooperation. The very existence of a fallback plan—a hard fork revert—confirms that the developers anticipated resistance. They are not trying to win; they are trying to gather data. The real insight is that Bitcoin's governance is not a democracy where miners hold all the cards. It is a system of overlapping authorities, and BIP-110 is the first real experiment in how far node-driven coercion can go. The risk is not the chain split itself. The risk is that if this experiment succeeds even partially, it sets a precedent for future upgrades to bypass miner consensus entirely. That would fundamentally alter the power dynamics of Bitcoin, making it a protocol where developers, not miners, control the activation of changes. For a system that prides itself on decentralization, that is a dangerous shift. Consider the financial engineering side. Bitcoin's entire value proposition as a store of value hinges on its immutability and predictable governance. When a BIP-110-style forced activation creates uncertainty, it undermines the confidence that makes Bitcoin the reserve asset of the crypto ecosystem. The money legos built on top—the custodial services, the derivatives, the lending markets—all rely on a single, consistent ledger. A chain split introduces a period of asset duplication, exchange pauses, and liquidity fragmentation. I have seen this play out during the 2017 Bitcoin Cash fork and the 2022 Terra collapse. The damage is not the fork itself; it is the erosion of trust in the protocol's stability. Institutional investors, who have only recently begun to allocate to Bitcoin via ETFs, do not tolerate governance experiments. They demand predictability. BIP-110, with its forced signaling, is the antithesis of predictability. Where does this leave us? The next 30 days are critical. If the miner support remains below 3% and the mandatory signaling deadline passes, the network will face a decision. The fallback plan—a hard fork revert—would effectively cancel the upgrade, restoring the status quo. That is the most likely outcome, given the overwhelming miner opposition. But the scars will remain. The debate over who gets to decide Bitcoin's future—nodes or miners—will resurface with every subsequent soft fork. BIP-110 is a relic of a bygone era, but its forced signaling phase is a reminder that Bitcoin's governance is not a solved problem. It is a puzzle that requires constant negotiation between code and capital. And when the negotiation breaks down, the network's greatest asset—its unity—becomes its greatest liability.