The Ghost of BIP-110: Bitcoin’s Mandatory Signaling Experiment and the 3% Miner Rebellion

When a Bitcoin Improvement Proposal enters mandatory signaling with less than 3% miner support, the network is not moving forward — it is holding its breath. I have seen this pattern before, in the quiet hours of a protocol audit where a single line of code could either unify or fracture a ledger. The numbers are stark: 3% of the hashrate signaling compliance. The rest, silent. This is not a vote of confidence. It is a governance stress test conducted in the open, and the results are already written in the blockchain’s cold data. BIP-110, proposed during the heated block size debates of 2015-2017, was never intended to be a mainstream activation mechanism. It was a weapon — a technical tool for node operators to enforce protocol changes without miner consent. The mechanism is simple: after a certain block height, nodes running BIP-110-compliant software will reject any block that does not contain a specific version bit. This is mandatory signaling, a form of User-Activated Soft Fork (UASF). Unlike BIP-9, which requires 95% miner signaling over a difficulty period, BIP-110 bypasses the need for miner majority. It is a declaration of node sovereignty. And now, years later, it has been activated in a test environment — or perhaps on mainnet, the details remain murky — with miner support barely registering. The context is crucial: this is not a proposal seeking adoption; it is a historical artifact being dusted off for study. The 3% figure is not a failure of marketing; it is a reflection of the economic reality that miners see no incentive in this upgrade. They have not upgraded their software. They have not signaled. They have simply ignored the mandate. Tracing the static in the protocol’s genesis block, I recall my own 2017 experience auditing a crowdsale contract that had a reentrancy vulnerability. That vulnerability was a hidden flaw in the logic, much like the hidden flaw in BIP-110’s assumption: that code-enforced rules can override economic incentives. The core of this analysis lies in the technical asymmetry between node-enforced rules and miner execution. In a proof-of-work chain, miners produce blocks. Nodes validate them. When a node enforces a rule that miners do not follow, the network enters a state of disagreement. If enough nodes enforce the rule, the miners who do not comply will see their blocks orphaned by the enforcing nodes. This creates a split — two chains, one with the new rule, one without. The 3% support means that only a tiny fraction of miners are willing to play along. The rest are either unaware, indifferent, or actively opposed. Based on my experience auditing smart contract infrastructure during the 2017 ICO boom, I have learned that protocol-level conflicts rarely resolve through technical force alone. The human element — the miners, the node operators, the exchanges — determines the outcome. In this case, the mandatory signaling phase is a test of whether a small group of nodes can impose their will on the majority. The data suggests not. The risk of a chain split is real, but the probability is low because the enforcing nodes are likely few. The hard fork rollback plan mentioned in the discussion is a safety valve: if the split becomes too disruptive, the developers can deploy a patch to revert to the previous consensus. This is a recognition that the experiment may fail. The narrative here is not about technical innovation but about governance power. The 'mandatory' in mandatory signaling is a promise that the code will enforce itself, but the code is only as strong as the nodes that run it. And the nodes are few. Every bug is a story the system tried to hide, and BIP-110’s story is one of governance tension. Let me take you deeper into the technical architecture. BIP-110 uses a version bit in the block header to signal readiness. The mandatory signaling phase means that after a certain threshold date, nodes will reject blocks that do not include this bit. This is a form of soft fork enforced by the full node network, not by the miners. The 3% miner support indicates that only a tiny fraction of the network’s hashrate is sending blocks with that bit. In a typical BIP-9 activation, the threshold is 95% over a 2016-block retarget period. Here, the threshold is not a percentage of hashrate; it is a timestamp. This is the key difference: BIP-110 is a time-based enforcement, not a consensus-based one. It is a unilateral declaration. The contrast with BIP-9 is stark: BIP-9 was designed to be miner-friendly, requiring broad support before activation. BIP-110 was designed to be node-friendly, bypassing miner consent entirely. The historical context matters. During the block size wars, the Core development team was accused of being too centralized. BIP-110 was a response — a way to give node operators a voice. But the 3% support shows that even node operators are not rallying behind this mechanism. The silence is deafening. Now, the contrarian angle: The low miner support is not a sign of rejection but of irrelevance. The 3% may represent the only miners who bothered to update their software, perhaps during a routine maintenance window. The 97% silence could be apathy, not opposition. In the early days of Bitcoin, many protocol changes were adopted with minimal miner coordination because the economic stakes were lower. Today, the stakes are enormous, and miners are carefully selective. BIP-110 is not a proposal that threatens their revenue; it is a proposal that offers no benefit. Why would they signal? The mandatory signaling is a test of a mechanism, not a real attempt to change the network. The developers may be using this as a pressure test for future, more critical upgrades. The hard fork rollback plan is an admission of the possibility of failure, but it also gives the developers an exit strategy. The real story is not that miners are rebelling; it is that the developers are conducting a controlled experiment to understand the limits of node enforcement. This is a learning exercise, not a civil war. From a market perspective, such technical experiments often fly under the radar. The average trader does not care about BIP-110. But for those who manage institutional funds, like myself, this is a signal. It tells us that the governance layer is still fragile. In my 2020 report on DeFi yield stabilization, I wrote that 'Yields do not vanish; they merely change form.' Here, governance conflicts do not disappear; they shift from the code to the social layer. The market impact of a potential split is non-trivial. If a real chain split were to occur, exchanges would have to list new coins, and custody providers would need to make decisions. That would be a regulatory minefield. But given the test nature, the probability is low. The emotional tone in the community is one of indifference, not fear. That is the most telling sign. Stability is the quiet architecture of trust. The legacy of BIP-110 will not be a successful upgrade but a lesson in Bitcoin governance. It teaches us that the network’s stability depends on the quiet architecture of trust between nodes and miners. When that trust is broken, even a 3% signal can create enough static to disrupt the signal. The next time you see a protocol with mandatory enforcement, ask yourself: who is really in control? The code, or the community that runs it? Stability is a silent promise kept between nodes, and that promise is only as strong as the willingness to keep it. As I wrote in my 2020 report on DeFi yield stabilization, 'Yields do not vanish; they merely change form.' Similarly, governance conflicts do not disappear; they shift from the code to the social layer. BIP-110 is a ghost of Bitcoin’s past, but its lesson is eternal. The question remains: will the next generation of Bitcoin upgrades learn from this ghost, or will they repeat the same mistake of enforcing without consent? The 3% signal is a whisper, but it carries the weight of the entire network’s history.