Bitcoin BIP 110 Fork Deadline Nears as Miner Support Falls to Zero

What to Know

• BIP 110, formally called the Reduced Data Temporary Soft Fork, would temporarily restrict non-financial data on the Bitcoin blockchain for one year.
• The proposal would tighten limits on OP_RETURN and other data-carrying methods, including restrictions on arbitrary data chunks above 256 bytes.
• Miner signaling has never risen above about 1% in any period and stands at zero in the current one.
• No major mining pool is currently backing the proposal.
• Node adoption remains in the low single digits and is largely associated with Bitcoin Knots rather than the dominant Bitcoin Core software.
• The current signaling period runs from block 957,600 to 959,615, with a voluntary lock-in deadline at block 961,542 in the following period.
• The deadline is expected in early August, while activation is projected near September if participating nodes proceed.
• Michael Saylor and Adam Back have publicly opposed the proposal, warning that a dispute over spam should not become a consensus-level fight.
• With miner and node support limited, market participants increasingly view BIP 110 as likely to create a small minority chain rather than a network-wide change.

Bitcoin Faces a High-Stakes Data Debate

Bitcoin is approaching a contentious governance moment as BIP 110, a proposal designed to restrict arbitrary data on the network, moves toward a hard deadline in early August. The proposal has generated intense discussion because it touches one of Bitcoin’s most sensitive questions: what should block space be used for, and who gets to decide which transactions are acceptable?

BIP 110 is formally titled the Reduced Data Temporary Soft Fork. In practical terms, it would narrow the ways users can insert non-financial data into Bitcoin transactions for one year. Supporters frame the measure as a temporary response to rising use of Bitcoin as a data layer, arguing that the network should remain focused on payments and monetary settlement. Critics counter that the proposal would introduce a dangerous precedent by invalidating transactions that are currently valid, fee-paying, and accepted under existing consensus rules.

The controversy has grown as support indicators remain extremely weak. Miner signaling has never risen above about 1% in any period and stands at zero in the current one. No major mining pool has moved behind the proposal. Among nodes that store and relay the chain, adoption is also in the low single digits, with support largely carried by Bitcoin Knots, an alternative implementation to the dominant Bitcoin Core software.

What BIP 110 Would Change

Bitcoin transactions can move value, but they can also include additional data. One of the best-known methods is OP_RETURN, often described as a small note field inside a transaction. Other approaches include data pushes, where users place larger pieces of raw data inside Bitcoin script or witness data. These mechanisms have been used by Ordinals, inscriptions, and some token schemes to place images, text, or token metadata onchain.

BIP 110 would tighten those routes temporarily. It would cap OP_RETURN at the old small size, block most arbitrary data chunks above 256 bytes, and restrict some script formats used mainly for data storage. Supporters say that would reduce the burden on nodes and help steer Bitcoin back toward its role as money rather than a general-purpose database.

Opponents do not necessarily deny that non-financial data can create concerns. The dispute is over whether a consensus rule is the right response. In Bitcoin, policy preferences and consensus rules are very different things. A policy dispute can influence how certain nodes relay transactions, how users price fees, or how wallets behave. A consensus change, by contrast, affects what blocks are considered valid. That makes BIP 110 far more serious than a simple debate over taste or network etiquette.

Saylor and Back Warn Against a Precedent

Several prominent Bitcoin figures have spoken out against the proposal. Strategy founder Michael Saylor argued that there are “110 things more dangerous to Bitcoin than spam,” saying BIP 110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions. His central concern is not merely the specific data being targeted, but the precedent such a change could establish.

Adam Back, the Blockstream co-founder whose hashcash design is cited in the Bitcoin white paper, also opposed the plan. Addressing newer supporters of the proposal, he argued that Bitcoin would not follow their preferred direction if the broader network did not agree. He suggested that those who remain unconvinced can group together and fork away, but that Bitcoin itself would not be joining such a move.

The objections from Saylor and Back matter because they reflect a broader strain of Bitcoin thinking: the network’s neutrality comes from its reluctance to judge transaction intent. Once valid, fee-paying transactions become subject to rejection because a group dislikes their content or use case, critics argue, the neutrality of Bitcoin block space may become harder to defend in future disputes.

Miner Support Is Missing at a Critical Moment

The most important market signal is not social media noise but actual adoption. On that front, BIP 110 is struggling. The proposal does not rely on the usual path of overwhelming miner approval. Instead, it uses a user-activated soft fork mechanism in which nodes enforce a new rule whether or not miners agree. The design is set around a 55% miner-signaling threshold rather than the traditional 95% threshold.

Even with that lower bar, backing has not materialized. Miner signaling stands at zero in the current period and has not exceeded about 1% in any period. That absence of support leaves BIP 110 facing a severe legitimacy problem. In Bitcoin, miners do not unilaterally govern the protocol, but their behavior matters because they produce blocks. If almost no hash power follows a rule enforced by only a small number of nodes, the most likely result is not a network-wide upgrade but a split into a minority chain.

The current signaling period runs from block 957,600 to 959,615. A voluntary lock-in deadline falls at block 961,542 in the following period, expected in early August. Nodes running BIP 110 software would then begin rejecting blocks that do not signal support, with activation projected near September. If participation remains low, technical traders and node operators are likely to treat the outcome as a limited fork event rather than a meaningful Bitcoin-wide rule change.

Why the Spam Concern Still Resonates

The debate has not emerged from nowhere. Blocks have carried more non-financial data since the October change, and many Bitcoin users view that as a meaningful shift. For them, the issue is not only technical efficiency but monetary identity. Bitcoin was built to serve as decentralized money, and some users fear that its settlement layer is being repurposed into a permanent storage layer for images, inscriptions, and metadata.

That concern has appeal among users who prioritize low operational burden, long-term node accessibility, and a narrow definition of Bitcoin’s purpose. If blocks are filled with data that many users consider unrelated to money, they may see the trend as an erosion of Bitcoin’s core mission. From that perspective, BIP 110 is an attempt to keep Bitcoin aligned with payments and settlement.

Yet Bitcoin’s architecture makes unilateral cleanups difficult. The network changes only when enough independent participants choose to run the same rules. There is no central committee that can declare a transaction type unacceptable simply because it is unpopular. That is one reason consensus battles can become so consequential: they test not only code but the social agreement behind the code.

A Minority Chain Looks More Likely Than a Broad Upgrade

Given the current indicators, BIP 110 appears unlikely to become a network-wide rule. With miner backing at zero in the current period and node adoption in the low single digits, the proposal lacks the broad alignment normally associated with a durable Bitcoin change. If a small group of nodes rejects blocks that the rest of the network accepts, the likely result is separation rather than adoption.

That outcome would be consistent with Bitcoin’s history of slow, cautious change. The network’s resistance to rapid protocol shifts is not written in one governing document. It emerges from thousands of independent operators, miners, businesses, developers, and users choosing what software to run. Consensus is not merely a slogan; it is the practical result of distributed refusal to follow changes that lack sufficient buy-in.

For Bitcoin markets, the immediate question is not whether non-financial data is good or bad, but whether the dispute becomes disruptive. So far, the weak support profile suggests limited systemic risk to the main Bitcoin chain. However, the debate itself is important because it reveals continued tension over Bitcoin’s identity, neutrality, and acceptable use of scarce block space.

As the early August deadline approaches, BIP 110 is becoming less a likely upgrade and more a stress test of Bitcoin governance norms. Supporters see an attempt to defend Bitcoin’s monetary focus. Critics see an attempt to censor valid transactions through a consensus rule. The network, at least for now, appears to be giving its answer through non-adoption.

Frequently Asked Questions (FAQs)

What is BIP 110?

BIP 110 is a Bitcoin proposal formally called the Reduced Data Temporary Soft Fork. It would temporarily restrict certain forms of non-financial data on the Bitcoin blockchain for one year.

What would BIP 110 restrict?

It would tighten limits on OP_RETURN, block most arbitrary data chunks above 256 bytes, and restrict some script formats that are mainly used for data storage.

Why do supporters want BIP 110?

Supporters argue that Bitcoin should remain focused on payments and settlement rather than becoming a broader data-storage system. They also say tighter data limits could reduce node burden.

Why do critics oppose BIP 110?

Critics argue that the proposal would turn a spam dispute into a consensus rule and invalidate some currently valid, fee-paying transactions. They see that precedent as more dangerous than the spam concern itself.

How much miner support does BIP 110 have?

Miner signaling has never risen above about 1% in any period and stands at zero in the current one. No major mining pool is currently backing the proposal.

What role do nodes play in BIP 110?

BIP 110 uses a user-activated soft fork model, meaning participating nodes would enforce the rule even without miner agreement. Current node adoption remains in the low single digits.

When is the BIP 110 deadline?

The current signaling period runs from block 957,600 to 959,615, and a voluntary lock-in deadline falls at block 961,542 in the following period, expected in early August.

Could BIP 110 split Bitcoin?

If only a small share of nodes and almost no miners enforce the new rule, it would be unlikely to change Bitcoin for everyone. Instead, it could create a small minority chain.

What is the broader importance of this debate?

The debate highlights a fundamental question about Bitcoin: whether block space should remain neutral for all valid, fee-paying transactions or whether certain forms of non-financial data should be restricted at the consensus level.

Photo by Beto Gonsalvo on Pexels