BIP-110's Mandatory Signaling: A Governance Test with a Pre-Written Failure Script
Bitcoin's BIP-110 mandatory signaling phase has officially begun, but the numbers are damning: miner support sits below 3%. This is not a soft fork activation; it is a governance test with a pre-written failure script. The test phase, as described in the protocol's documentation, includes a hard fork fallback plan—a retreat mechanism that acknowledges the high probability of failure. Hype evaporates; receipts remain. The receipt here is a ledger of miner indifference: 97% of hashrate is not signaling for the change. For a mechanism that claims to enforce consensus through node coercion, this is a catastrophic start.
BIP-110, proposed years ago, is a relic of the block size debate era. It is a mandatory signaling mechanism for soft fork activation: after a certain timeout, nodes reject blocks that do not include a specific version bit. This is the antithesis of the later BIP-9, which requires 95% miner hashrate to signal support before activation. BIP-110 is a node-centric, UASF-style approach—code as command, not code as persuasion. The current phase is a test on a small scale, likely on a testnet or a limited subset of mainnet nodes, but the implications are structural. The developers are testing whether they can force a rule change without miner consent. The answer, so far, is a resounding no.
In my seven years auditing protocol activation mechanisms, I have seen this pattern repeat. The party that controls the nodes can enforce a rule, but without the party that controls the hashrate, the rule is unenforceable in practice. The result is either a fork or a retreat. BIP-110's test is no different. The data shows a fundamental contradiction: nodes are programmed to reject non-signaling blocks, but miners are rejecting the signal. If the test were to escalate to full enforcement, the network would split into two views—one that accepts only signaling blocks, and one that accepts all. The fallback plan is a retreat valve, but it also reveals the premeditated nature of the failure. The developers knew they would likely fail, so they built a way out. This is not a stress test; it is a rehearsal.
The technical details are stark. The mechanism requires miners to set a version bit. With support below 3%, the overwhelming majority of blocks are non-compliant. If the mandatory phase were to trigger on mainnet, the chain would experience a temporary fork. The signaling nodes would reject most blocks, leading to a chain split. However, because the signaling nodes are a minority of the network's economic weight, the non-signaling chain would likely prevail. The hard fork fallback plan would then be executed, effectively rolling back the mandatory requirement. This is a scripted retreat, not a genuine attempt to change the protocol.
Ledger balances do not lie; they only wait. The miner support numbers are a ledger of trust. Miners are not convinced that BIP-110 is necessary or beneficial. The 3% support is likely from a few small pools or individual miners testing the software. The silence from the major pools is deafening. This is not a debate; it is a boycott. The governance signal is clear: miners do not want mandatory signaling.
Volatility is not risk; opacity is. The real risk here is not price volatility—the market has barely reacted—but the opacity of the governance process. The developers are testing a mechanism that could have caused a contentious fork if implemented on a larger scale. The fact that it is a test does not absolve the process of its lack of transparency. The community outside the core developer circle is largely unaware of this test. The risk is that such experiments, if conducted without broad communication, can erode trust in the protocol's stability.
Compare this to BIP-9, which became the standard for soft fork activation. BIP-9 requires 95% miner hashrate to signal over a difficulty adjustment period. This forces developers to seek miner consensus, which is why BIP-9 was used for SegWit and Taproot. BIP-110's failure is a lesson for future upgrades: coercion does not work in a decentralized system. The only way to change the protocol is to align incentives, not to force compliance.
Contrarian view: some proponents argue that the test is valuable regardless of outcome. It demonstrates the ability to enforce user-activated soft forks. It tests the resilience of the network under a governance stress scenario. The low support is because miners are conservative, not because they oppose the change. The test generates data that can inform future mechanisms. The market has not panicked, which suggests that the test is seen as a non-event. This is a healthy stress test that reveals the boundaries of consensus.
But I counter: a stress test that fails without consequence is not a test; it is a rehearsal. Without real economic consequences, the lesson is not learned. The miners are not participating because they see no economic incentive to do so. The test does not change their behavior. The data generated is already known: mandatory signaling is unpopular. The real value of the test is to prove that the mechanism is unworkable, which could have been known from the design alone. The bulls are right that the test is harmless, but they are wrong to call it a success. It is a catalog of failure.
The takeaway is forward-looking. BIP-110 will likely be abandoned. The Bitcoin network will learn from this that mandatory signaling without miner support is a dead end. The narrative will shift to BIP-9 and similar miner-friendly mechanisms. The real lesson: decentralized governance requires alignment of incentives, not force. The question remains: will the next major upgrade, like BIP-119 or CTV, face similar resistance? The receipts are on chain. The numbers do not forgive. The 3% miner support is a clear signal to developers: build consensus, not coercion.