Bitcoin's BIP-110 Deadline Hits as Miner Support Stays Below 3%

BIP-110 heads into mandatory signaling with weak miner backing

BIP-110 has 2.01% signaling with only 1,371 blocks remaining until mandatory signaling begins. That leaves little room for a last-minute rally toward the 55% signaling threshold. Still, one of the most controversial Bitcoin proposals of 2026 is no longer just an abstract debate: the schedule is now the story.

Mandatory signaling starts at block 961,632, lock-in is no later than block 963,648, and activation is currently projected for early September. For markets, that turns BIP-110 into a schedule-driven risk event. Low support makes a clean pass unlikely, but not so unlikely that traders can ignore confusion, late coordination, or a sudden shift in miner behavior.

BIP-110 is not a typical miner-led soft fork. Its design is user-activated, so miner signaling is important but not the only pressure point. Even with weak hash-rate support, the proposal can still matter if users and operators choose to run its rules.

That makes the real watchpoint broader than pool statistics. Traders should watch which wallets, nodes, and exchange deposit pipelines prepare for BIP-110-style restrictions, because operator behavior matters as much as block-version signaling.

The first friction would show up in data-heavy transactions

If BIP-110-active rules gain traction, the first impact would fall on non-monetary transaction traffic rather than on standard payments. The proposal would restrict the use of block space for non-financial data and specifically target Ordinals, BRC-20, and Runes. At the same time, standard monetary uses remain compatible and the rules would grandfather UTXOs created before activation.

In practice, that means inscriptions, BRC-20 transfers, Runes operations, and other large-data transactions could face more friction if a meaningful share of operators adopt the new rules. Weak miner backing makes full activation less likely, but it does not erase the underlying risk map.

The fault line is about invalid blocks, not jargon

The emotional flashpoint is straightforward: miners must set versionbit 4, and blocks without it would be invalid to BIP-110 nodes. The BIP-110 author also told users it is not recommended to run Bitcoin Core. Bears see a failed upgrade chasing a fight. Bulls see a grassroots push for stricter rules. The practical risk is that Bitcoin does not need universal support to feel functionally different; it only needs enough operators to enforce a different standard.

How to read BIP-110 over the next month

Treat the next 30 days as a monitoring window, not a belief test. The signal is still weak at 2.01% signaling, but it is no longer zero. Daily updates should remain highly visible because signaling is still nearly absent in practical terms, so even small changes matter.

Base case: low support, unresolved risk

The base case remains that miner support is too thin for a clean pass, yet the proposal is still user-activated. That combination does not automatically mean activation. It does mean Bitcoin can still move on coordination fear while the community sorts out who is preparing for what.

What would strengthen the fork-risk case

The setup gets more serious if three conditions line up:

• miner signaling moves decisively higher from today's weak level
• operators, wallets, or exchanges begin adapting to BIP-110-style rules
• data-heavy activity starts showing practical friction rather than just debate

If that happens, traders will stop treating BIP-110 as a niche argument and start pricing a real split in Bitcoin transaction flow.

What would weaken the setup

The watch window fails if signaling stalls for long stretches and the narrative fades into noise. It also weakens if adoption stays purely rhetorical and no real friction appears in inscriptions, BRC-20 transfers, Runes, or similar large-data transactions. If miner support remains near 2.01% signaling, BIP-110 is more likely to stay a governance volatility event than a new consensus regime.