Bitcoin Blocks Keep Skipping BIP-110 Signal as Mandatory Window Opens

Bitcoin’s BIP-110 Window Has 11 Non-Signaling Blocks

The narrow, verified point is about the chain data, not a verdict on Bitcoin governance. BIP-110 assigns bit 4 to a proposed reduced_data deployment and says mandatory signaling runs from block 961,632 through 963,647.

The specification states that the bit is included in vbrequired during that period. Its stated rule would treat blocks without the signal as invalid, yet the observed main chain continued with all 11 reviewed version fields lacking bit 4.

BIP-110 is a document in the Bitcoin BIPs repository, even though its listed status is Complete. A published BIP does not by itself place new validation rules on Bitcoin nodes, and the first 11 non-signaling blocks are evidence that its mandatory rule was not visibly enforced across the live chain at the time checked.

The proposal describes itself as a Reduced Data Temporary Softfork. It would limit several data-carrying formats for new transactions, including certain output scripts, data pushes and Taproot constructions, if it reached its specified activation stage.

Missing Bit 4 Does Not Confirm a Bitcoin Fork

The distinction matters because block-version data can show what miners placed in blocks, but it cannot by itself measure every node operator’s software choice or establish broad economic support. The chain data in this report does not show that BIP-110 is active, and it does not establish a fork.

No public evidence reviewed for this update showed an interruption to ordinary Bitcoin transfers, a competing main-chain tip, or an activation notice from Bitcoin Core. Holders therefore do not have a public, chain-level instruction to move standard balances on the basis of these 11 blocks.

The BIP says that UTXOs created before activation would be grandfathered. Its discussion of potential edge cases is limited to certain pre-signed Taproot constructions, rather than a general problem with existing Bitcoin holdings.

Miner indications remain one piece of a broader process. Foundry’s earlier hashrate-weighted client vote illustrated the separate question of how a pool plans to signal, while node operators ultimately decide which rules they validate.

The latest data also raises the bar for claims that the proposed mandatory stage is already operating in practice. As each additional non-signaling block remains on the main chain, the observable gap between BIP-110’s written rule and live-chain behavior becomes less a countdown and more an ongoing adoption test.

Block 963,648 Is the Next BIP-110 Deadline

BIP-110 sets a 55% threshold, or 1,109 blocks in a 2,016-block period, and says the deployment would be locked in no later than height 963,648. It then places the proposed ACTIVE state at height 965,664 and says the restrictions would last 52,416 blocks, about one year.

Those heights are schedule parameters, not a confirmation that the network will take the stated transitions. The 11 blocks reviewed here sit only at the beginning of the mandatory range, so miner notices, node-software releases and continued block-level evidence are more informative than a calendar estimate.

The controversy is separate from Bitcoin’s other upgrade and security discussions, including the quantum-readiness work that drew a $15 million consortium. BIP-110 instead concerns arbitrary data and the conditions under which a temporary consensus restriction could gain effect.

The Crypto Fear and Greed Index was at 30, or Fear. The next concrete checks are whether blocks nearer 963,648 begin carrying bit 4, whether any deployed client enforces a matching rule, and whether claims of lock-in can be confirmed from the chain rather than inferred from the BIP timetable.