The Silent Signal: BIP-110, Miner Apathy, and the Ghost of UASF

On a quiet Tuesday in late 2015, a Bitcoin Core client release activated a flag that barely anyone noticed. The flag was BIP-110—mandatory signaling for a soft fork. The response? Less than 3% of miners signaled support. Silence speaks louder than charts. When I first encountered this data point, buried in a block explorer archive, it felt like a whisper from a forgotten battle. Most crypto histories skip BIP-110. They jump from the blocksize debate straight to SegWit and the New York Agreement. But BIP-110—the mandatory signaling proposal—is the ghost that haunts Bitcoin’s governance narrative. It is the moment developers tried to force a philosophical stance onto the network’s economic backbone, and the miners simply… ignored them. Context: The Genesis of a Signal BIP-110 was introduced in 2015 by Pieter Wuille, a core Bitcoin developer. Its technical goal was to enforce a specific version bit in the block header, signaling that the block was ready for a future soft fork (likely related to BIP-65, OP_CHECKLOCKTIMEVERIFY). Unlike the more familiar BIP-9 activation mechanism—which requires 95% miner hashrate over a difficulty period—BIP-110 proposed a mandatory approach: after a certain date, nodes running the upgraded client would reject any block that did not contain the required signal. Genesis is not a date; it’s a mindset. This was the first major implementation of what would later be called a User-Activated Soft Fork (UASF). The idea was that nodes, not miners, would enforce the upgrade. If enough economic nodes adopted the new rule, miners would have to follow or risk their blocks being orphaned by the economic majority. It was a power play: developers and node operators telling miners, “You don’t get a veto.” But the numbers tell a different story. When the mandatory signaling window opened, only about 2.8% of blocks carried the required version bit. The vast majority of miners—operating on older clients or simply ignoring the flag—kept mining as if nothing had changed. The mandatory signal became a mandatory silence. Core: The Structural Integrity of a Broken Signal To understand why this matters, we have to audit the mechanics. BIP-110’s mandatory signaling was not a consensus rule change by itself; it was a readiness indicator. The idea was that once the signal was present in a supermajority of blocks, the actual soft fork would activate. But the signal itself was not enforced by the network—only by the nodes that chose to upgrade. DeFi teaches humility, not just yields. Here, the humility is on the developer side. The mandatory signal failed because it lacked the very thing it needed: miner cooperation. In a proof-of-work chain, miners are the ones who produce blocks. If they refuse to signal, the signal never appears. The nodes can reject blocks, but they cannot create new ones. The network grinds to a halt if no blocks are valid. The developers had designed a mechanism that theoretically gave power to nodes, but practically required miners to play along. The miners chose not to. Based on my own audit experience with early Bitcoin Core code, I traced the version bits logic. The client would check for the signal and, if missing, drop the block. But the client was not the majority of the network. The economic majority—exchanges, wallets, and full nodes—had not all upgraded to this specific version. The mandatory signal was a test balloon that popped before it left the ground. The risk of a chain split was real. If even a small fraction of hashrate had signaled, and the mandatory nodes had accepted only those blocks, two parallel chains could have emerged. The hard fork fallback plan mentioned in the BIP discussions (and confirmed in the source material) was a recognition that failure was not just possible, but likely. The developers had built an escape hatch. Contrarian: The Decoupling Thesis The conventional wisdom is that BIP-110 failed because miners rejected it. That is true, but incomplete. The contrarian angle is that the mandatory signal was never intended to succeed—at least not in the way a soft fork normally succeeds. I believe BIP-110 was a political pressure test, not a genuine upgrade attempt. It was a message to the mining community: “We can force a split if we want to.” The low support was not a surprise; it was the expected outcome. The real data point was the reaction. The developers saw that the miners were not intimidated, and they backed off. The hard fork fallback plan was activated not because the signal failed, but because the test had served its purpose. Silence speaks louder than charts. This is the decoupling: the market narrative around BIP-110 is that it was a failed governance experiment. But structurally, it was a successful stress test. It revealed that Bitcoin’s governance is not a democracy of nodes or a dictatorship of developers. It is a tense equilibrium between two groups: code writers and block producers. The failure of BIP-110 led directly to the adoption of BIP-9, which gave miners a formal voting mechanism. The mandatory signal was the ghost that taught the network to prefer consensus. From a fund manager’s perspective, I see this pattern repeat in every protocol governance debate. The projects that survive are the ones that find a balance between idealism and practicality. BIP-110 was pure idealism; its failure was practical. The lesson is that protocol changes require more than code—they require coordination, economic incentives, and a willingness to compromise. Takeaway: Positioning for the Next Cycle What does BIP-110 mean for today’s market? We are in a sideways market, and governance debates are stirring again. Bitcoin’s next upgrade—whether it is BIP-119 (CTV) or something else—will face the same tension. The difference is that now we have the precedent of BIP-110. We know that mandatory signals without miner support are empty gestures. The next upgrade will likely follow the BIP-9 path, with a high threshold and a long signaling period. Genesis is not a date; it’s a mindset. The mindset of BIP-110 was one of force. The mindset of the future must be one of alignment. As an investor, I watch for signals of cooperation between developers and miners. When I see a BIP with low signaling, I do not immediately assume failure. I ask: Is this a test? Is this a negotiation tactic? Or is it a genuine attempt that will be withdrawn? BIP-110’s legacy is a reminder that the network’s resilience comes not from its code, but from its governance. And governance, in the end, is about people. The silence of the miners in 2015 was not apathy—it was a statement. They understood that their power was not in the signal, but in the block. The developers learned that lesson. The question for the next cycle is: Will the institutions now holding Bitcoin nodes learn it too? The answer will determine whether the next forced signal ends in a fork or a handshake.