BIP-110 in Bitcoin has almost no miner support

BIP-110 in Bitcoin is approaching its deadline in early August 2026, while miner support remains below 1%. This matters for miners, network nodes, and those following Ordinals and on-chain data.

The Reduced Data Temporary Soft Fork proposal aims to restrict the publication of arbitrary data on the Bitcoin network for 1 year. According to signaling monitoring data, as of July 12, 2026 at 15:23 UTC, the counter showed tip 957,719, in the current period No. 475 there were 0 out of 120 blocks signaling, and 3,913 blocks remained until the voluntary deadline at block 961,632, which is about 27.2 days at a pace of 10 minutes per block.

Why did BIP-110 trigger such resistance?

The idea is simple. BIP-110 wants to tighten the rules for OP_RETURN and most data inserts above 256 bytes for 1 year. The proposal also affects certain script formats used to store images, text, and metadata, including in Ordinals and related protocols.

Supporters say this will refocus the network on money transfers and reduce the load on nodes. Opponents see a different picture: in their view, this is no longer just a debate about spam, but a change to consensus rules. And that is where the main conflict begins, because in Bitcoin any attempt to rewrite the boundaries of what is allowed triggers a very sharp reaction from the community.

Another nuance is that the current debate is taking place against the backdrop of changes in OP_RETURN policy. After those changes, there has been more non-financial data on the network, so the dispute over what counts as normal use of block space has only intensified. From here on, people are looking not only at the technical side, but also at network policy.

Market reaction

Here the numbers speak for themselves. According to BIP-110 monitoring, support among mining pools remained below 1% throughout the period, and is now 0%. In the previous full period No. 474, there were 20 signaling blocks out of 2,016, or 0.99%. Before that there were also completely empty periods: Nos. 469-470 came in at 0.00%, No. 471 showed 0.35%, No. 472, 0.79%, and No. 473, 0.45%.

Against this backdrop, Michael Saylor and Adam Back publicly opposed the initiative. Saylor wrote that BIP-110 turns a spam dispute into a consensus change that would invalidate some transactions that are currently valid and pay fees. Back also said it plainly: if you disagree with the rules, you can create your own fork, but Bitcoin will not join it.

“Bitcoin is politely saying ‘no’ to what you want,” Adam Back said, commenting on the attempt to change the rules without broad consensus.

There is another practical detail. Under the specification, the hard signaling window is tied to blocks 961,632-963,647, lock-in must occur no later than 963,648, and activation, if it happens at all, is scheduled for 965,664. That means time is short. And that is exactly why the market is watching not loud statements, but real signals in the blocks.

• BIP-110 concerns limiting non-financial data in Bitcoin.

• Miner support is now 0%, and the entire period has stayed below 1%.

• In the previous full period, there were 20 signaling blocks out of 2,016, or 0.99%.

• The voluntary deadline is tied to block 961,632, and activation, if it happens, to 965,664.

• Saylor and Back publicly opposed changing the consensus rules.

• If support does not increase, the network will not upgrade and risks ending up with a separate minority chain.

What does this story mean for investors?

For long-term Bitcoin holders, the main takeaway is simple: this does not look like an upgrade that is already almost ready to launch. When miners show 0% signaling and the deadline is roughly 27.2 days away, the chances of smooth approval look weak. That is why the scenario of a separate minority chain looks more realistic than mass activation.

For traders, not only price matters, but also technical risks. If some participants begin to interpret BIP-110 as an attempt to change the rules without sufficient support, it could add nervousness in the short term. And for those who work with BTC in hryvnia, such stories often become a reason to pay closer attention to liquidity and exchange speed, especially when they need to sell Bitcoin on Monobank.

There is also a broader lesson. In Bitcoin, technical changes happen not because someone likes them, but when the network truly agrees. That is not visible here yet. And that is why the dispute over BIP-110 looks more like a test of the limits of influence than a routine code update.

Frequently asked questions

What is BIP-110 in simple terms?

It is a proposal to temporarily restrict the publication of arbitrary data in Bitcoin for 1 year. It affects OP_RETURN, inserts above 256 bytes, and part of the formats used for Ordinals and similar protocols.

Can BIP-110 activate without support from the majority of miners?

Practically no. Signaling is currently at 0%, and even in the previous full period it was only 0.99%, so the chance of broad activation is very small.

What happens if some nodes support BIP-110 and others do not?

Then the network may move into a separate minority branch rather than a single Bitcoin upgrade. That is the main risk of such disputes, because without consensus the rules do not work the same for everyone.

For now, BIP-110 looks like a test of the limits of what is allowed in Bitcoin, not like an upgrade that is almost ready.

This material is not financial advice. Cryptocurrency trading involves significant risks. Part of this text was prepared with the help of artificial intelligence based on public sources and reviewed by our editorial team.