- Published on
Bitcoin’s BIP-110 enters mandatory signaling with miner support below 3%
- Authors
- Name
- DeepHorus
Bitcoin’s BIP-110 entered its mandatory-signaling phase at block 961,632 on Saturday, but miner support remains minimal. According to the BIP-110 monitor, miners signaled support in just 51 of the preceding 2,016 blocks, or 2.53%, far below the 55% threshold required for early activation. Starting at that block, nodes enforcing BIP-110 began rejecting blocks that did not set version bit 4, while ordinary Bitcoin nodes continued accepting both signaling and non-signaling blocks. A minority BIP-110 branch subsequently emerged, but quickly fell behind the dominant chain.
BIP-110, written by pseudonymous developer Dathon Ohm, proposes temporary consensus restrictions lasting roughly one year. It would limit most new output scripts to 34 bytes, cap OP_RETURN outputs at 83 bytes, restrict certain data pushes and witness elements to 256 bytes, and temporarily limit several Taproot features. Unspent transaction outputs created before activation would be exempt. Supporters argue the restrictions would discourage inscriptions and other non-monetary data that increase storage and bandwidth costs for node operators.
The low signaling rate makes a sustained rival chain unlikely without substantially greater miner participation. With relatively little mining support, a BIP-110 branch could advance slowly or stop producing blocks altogether. The milestone tests whether supporters can advance a contentious consensus change without broad miner backing, potentially separating enforcing nodes from the dominant chain and escalating a dispute over how Bitcoin’s block space should be used.
The proposal’s critics, including Strategy Executive Chairman Michael Saylor and Blockstream CEO Adam Back, have argued that it could divide Bitcoin and cause nodes to reject transactions permitted under the network’s existing rules. The deployment schedule sets blocks 961,632 through 963,647 as a mandatory-signaling window, during which enforcing nodes reject blocks without the signal. The specification defines block 963,648 as the beginning of its locked-in state and block 965,664 as the point when transaction restrictions take effect.
BIP-110 proponents have also discussed a more extensive fallback. On Aug. 1, Bitcoin developer Chris Guida rebased preliminary code for a proof-of-work change originally written by Bitcoin Knots maintainer Luke Dashjr. Guida described the code as a contingency if miners opposed BIP-110, but said no activation date had been set. The coming weeks will reveal whether mandatory signaling can pressure miners or if the proposal will stall without sufficient network support.
