A Bitcoin Fork Deadline Is Coming. Miner Support Is Still Zero

Bitcoin is moving toward a protocol deadline with an unusual combination: a finished soft-fork proposal, a built-in path toward mandatory signaling, and essentially no visible miner support.

BIP 110 would temporarily reject several forms of large arbitrary data at the consensus layer. Its current miner-signaling rate is zero.

That gap turns a dispute over blockchain spam into a test of how Bitcoin changes its rules. The proposal can reach its activation window on paper, while the network’s miners, nodes, exchanges, and users remain free to reject it in practice.

The word “Complete” beside a Bitcoin Improvement Proposal describes the document’s status. It does not mean Bitcoin has adopted the rules.

BIP 110, formally titled Reduced Data Temporary Softfork, proposes additional consensus checks for about one year. Its stated goal is to curb large arbitrary-data storage and refocus block space on Bitcoin’s monetary use.

The rules would invalidate new output scripts longer than 34 bytes, apart from OP_RETURN outputs up to 83 bytes, and cap many pushed-data and witness items at 256 bytes. It would also restrict undefined witness versions, Taproot annexes, oversized Taproot control blocks, OP_SUCCESS opcodes, and OP_IF or OP_NOTIF execution in Tapscript.

Coins already sitting in UTXOs before activation would be grandfathered, preserving their existing spending paths during the temporary deployment. New UTXOs created after activation would have to obey the tighter rules until the deployment expires.

The proposal sets a 55% threshold, 1,109 signaling blocks out of a 2,016-block difficulty period, and a maximum activation height of 965,664. It also acknowledges costs: some advanced contracts such as BitVM could be constrained, and narrow pre-signed Taproot edge cases could face frozen or lost funds.

> 5. Can spammers find ways to spam Bitcoin that BIP-110 does nothing about?

Not really, due to second-order effects: proper maintenance of node software means spam filters will be kept up to date.

— Luke Dashjr (@LukeDashjr) July 12, 2026

Supporters see a mismatch in Bitcoin’s fee market. A miner receives the one-time fee for including data, while thousands of node operators inherit the continuing cost of downloading, storing, and serving it.

BIP 110 tries to move that boundary from relay policy into consensus. That is exactly why the fight has become more serious than another argument over mempool defaults.

Consensus rules decide which blocks a node accepts as Bitcoin. A transaction can pay a competitive fee and remain valid under today’s rules, yet become invalid for nodes enforcing BIP 110.

The activation design raises the temperature further. If the 55% threshold is never reached voluntarily, the BIP 110 implementation would require signaling during blocks 961,632 through 963,647, lock in by height 963,648, and activate one period later.

That mandatory window is not a command sent to every Bitcoin miner. Only nodes running the BIP 110 rules would reject blocks that fail to signal, while standard nodes would continue judging those blocks under their existing consensus rules.

If nearly the whole economy adopts the new rules, miners have a strong reason to follow. If only a small minority adopts them, the minority may reject the chain carrying most proof of work and either stall or continue on a separate chain.

CoinDesk reports that signaling was at zero in the current period and had never climbed above roughly 1%. No major mining pool had publicly committed hash power to the proposal.

Node adoption was also in the low single digits, concentrated mainly among Bitcoin Knots users. That matters because a user-activated soft fork ultimately depends on nodes and economic actors enforcing the new rule even when miners are reluctant.

The current signaling period spans blocks 957,600 through 959,615, leaving only several difficulty periods before the forced-signaling range in the specification. Michael Saylor and Adam Back have both opposed the change, focusing on currently valid fee-paying transactions and the precedent of turning a use-case dispute into consensus law.

With miner signaling near zero and node support sparse, a smooth network-wide transition has little evidence behind it today. The nearer risk is that a committed minority enforces BIP 110 while the wider network continues under the existing rules.

There are 110 things more dangerous to Bitcoin than spam.

BIP 110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions.

That precedent is the danger. We should save our energy for threats that really matter. $BTC https://t.co/LoSkl9XSo1

— Michael Saylor (@saylor) July 11, 2026

Miner signaling is an important readiness measure, though it is not a vote that owns Bitcoin. Full nodes choose their rules, miners assemble blocks, and exchanges, wallets, custodians, merchants, and holders decide which chain has economic weight.

That division of power is why zero signaling does not automatically kill a user-activated soft fork. It also explains why activation code cannot manufacture broad agreement from a tiny enforcement base.

The pro-BIP case begins with node costs and purpose. Bitcoin’s permanent ledger is scarce, arbitrary files can consume block space, and the node operators preserving those files do not receive the miner’s transaction fee.

Supporters also argue that rising data demand competes with payments and can push ordinary users toward custodial services. In that view, temporary limits defend decentralization and buy a year for a more precise long-term design.

The opposing case begins with predictability. Bitcoin has long allowed users to purchase block space by meeting consensus rules and paying the market fee, even when other users dislike the purpose of a transaction.

Changing consensus to reject a disfavored category creates a precedent that can outlive a temporary deployment. The next campaign may target a different transaction pattern, application, or use that another faction calls abuse.

The technical tradeoffs make that concern concrete. BIP 110 would narrow several Taproot capabilities, temporarily close upgrade hooks, and limit deep Taproot trees that experimental systems may need.

The proposal’s grandfathering protects UTXOs created before activation, and ordinary payment patterns are designed to remain available. Developers using complex Taproot constructions would still need to inspect their spending paths rather than assume every path survives unchanged.

For a normal Bitcoin holder, no rule has changed today. Sending and receiving BTC remains governed by the software and chain the holder’s wallet, service, and counterparties currently recognize.

The first signs of a real shift would be hard to miss: major pools signaling, large node operators upgrading, exchanges publishing fork policies, custodians naming supported chains, and wallet developers warning about transaction compatibility. None of those can be replaced by a countdown alone.

The next few difficulty periods will reveal whether the zero is temporary hesitation or a durable rejection. A late surge could move the proposal toward voluntary lock-in, while continued flat signaling would make the mandatory period a direct confrontation between the BIP’s enforcing minority and the existing network.

Bitcoin can survive loud arguments over what belongs in a block. The harder question is whether either side can persuade enough independent actors to run the same rules.

BIP 110 has a deadline. Consensus does not.

Join the conversation!

We have no tolerance for comments containing violence, racism, profanity, vulgarity, doxing, or discourteous behavior. If a comment is spam, instead of replying to it please click the icon below and to the right of that comment. Thank you for partnering with us to maintain fruitful conversation.