Bitcoin BIP 110 is nearing an early August fork deadline with miner support at zero in the current signaling period, turning a fight over spam into a live test of Bitcoin’s tolerance for contentious consensus changes.
XOOMAR Intelligence
Analyst Take
The proposal, formally known as BIP-110 or the Reduced Data Temporary Soft Fork, would restrict arbitrary data on Bitcoin for one year, according to CoinDesk. Backers say it would push Bitcoin back toward payments. Critics, including Michael Saylor and Adam Back, say the cure could be riskier than the spam.
Why could Bitcoin BIP 110’s spam fix become a chain split risk?
The immediate problem is simple: some Bitcoin users want less non-financial data in blocks, but the proposed fix would change what counts as a valid block for nodes that enforce it.
That’s why Bitcoin BIP 110 is more than an argument about fees, Ordinals, or inscriptions. It asks who gets to decide which fee-paying transactions belong on Bitcoin. If enough of the network agrees, a stricter rule can become Bitcoin’s rule. If only a small minority agrees, the rule can fracture off into a minority chain.
CoinDesk reported that miner signaling has never climbed above about 1% in any period and stands at zero in the current one. Node adoption is also in the low single digits, mostly through Bitcoin Knots, an alternative to Bitcoin Core.
That matters because Bitcoin has no CEO to settle the dispute. Coordination is the governance system. When coordination fails, a proposal does not simply “lose a vote.” It can still create operational noise if a committed minority tries to enforce rules the rest of the network rejects.
For readers tracking Bitcoin risk across different fronts, this governance dispute is separate from price structure questions like Bitcoin Consolidation Traps Bulls in 307-Day Range, public-finance debates such as the New Hampshire Bitcoin bond, or balance-sheet decisions such as Empery Digital Dumps Half Its Bitcoin for AI Data Centers. BIP 110 is about the rulebook itself.
What would BIP 110 change about arbitrary data on Bitcoin?
BIP-110 would temporarily tighten the ways users place non-payment data into Bitcoin transactions.
Bitcoin transactions can carry value and extra data. The most visible route is OP_RETURN, which functions like a small note field. Other methods use data pushes inside script or witness data. Those paths can carry inscriptions, text, images, token metadata, and other payloads.
CoinDesk says BIP-110 would:
- Cap OP_RETURN at the old small size.
- Block most arbitrary data chunks above 256 bytes.
- Restrict some script formats mainly used for data storage.
- Expire after one year, rather than remain permanent.
The temporary design is meant to make the proposal less threatening. But temporary consensus changes still matter. Once a network decides it can invalidate currently valid transactions because a group dislikes their use case, the political precedent does not automatically expire after one year.
Here is the core split:
| Camp | Main claim | Risk they emphasize |
|---|---|---|
| BIP 110 supporters | Bitcoin block space should focus on payments, not arbitrary data storage. | Higher node burden, fee pressure, and drift away from monetary use. |
| BIP 110 critics | Valid, fee-paying transactions should not be censored by consensus rule. | Chain split risk and a precedent for banning disliked activity. |
The distinction is crucial. Miners and nodes can already choose relay or mining policies. A consensus rule goes further. It changes what enforcing nodes treat as valid Bitcoin.
How did Bitcoin’s data spam dispute turn into a miner signaling test?
Fork proposals usually need broad agreement from miners, node operators, developers, exchanges, wallets, and other economic actors. Miner signaling is one visible part of that process. It shows whether miners are ready to enforce or coordinate around a rule change.
BIP-110 uses a user-activated soft fork design with a 55% miner-signaling threshold, rather than the traditional 95% threshold cited by CoinDesk. Even at that lower bar, the proposal is nowhere close.
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. If the BIP-110 path proceeds, nodes running enforcing software would begin rejecting blocks that do not signal support, with activation projected near September.
That is where the stress begins. A few percent of nodes and almost no miners cannot realistically impose a network-wide rule. They can, however, create a minority chain if they reject blocks the rest of Bitcoin accepts.
Bitcoin’s resistance to fast change is not a slogan. It is a coordination requirement spread across thousands of independent operators. BIP 110 is testing that requirement in public.
Why are Michael Saylor, Adam Back and other Bitcoin voices warning against BIP 110?
Critics are not necessarily defending spam. Their argument is narrower and sharper: spam is bad, but making it a consensus fight is worse.
Saylor framed the danger as precedent:
"there are 110 things more dangerous to Bitcoin than spam"
He also wrote that the proposal:
"turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions."
Adam Back made a similar point to BIP-110 supporters, saying:
"Bitcoin respectfully says no to what you want,"
He added that if supporters remain unconvinced, they can fork away, but:
"bitcoin won't be joining it."
The pro-BIP 110 case still has force. Blocks have carried more non-financial data since the October change, according to CoinDesk, and supporters see that as a shift from Bitcoin as money toward Bitcoin as a database. If arbitrary payloads consume block space, payment users can face more competition for inclusion.
The dispute is not whether block space is scarce. It is whether scarcity should be managed by fees and policy choices, or by a new consensus rule that declares some existing transaction patterns invalid.
How would BIP 110 affect a real Bitcoin transaction during a data-heavy fee spike?
Consider a user trying to send Bitcoin while data-heavy transactions are filling blocks.
In the pro-BIP 110 version, the temporary cap reduces large non-payment payloads. That could leave more room for ordinary transfers and make block space less exposed to inscription-style bursts. Supporters would call that a narrow guardrail, not a redesign.
In the anti-BIP 110 version, the user faces a different problem. If enforcing nodes split from legacy nodes, the question becomes less “How high is the fee?” and more “Which chain will my exchange, wallet, or counterparty recognize?”
That is the trade-off. Fee pressure is annoying and sometimes expensive. A chain split threatens the shared settlement context that makes Bitcoin useful in the first place.
The concrete numbers show why critics think the second risk dominates. BIP-110’s threshold is 55%, or a majority-like signal inside a difficulty period. CoinDesk says current miner support is zero in the current period, with no major mining pool behind it. If enforcement begins anyway, the likely result is not cleaner Bitcoin. It is a small minority chain.
If miners stay at zero, BIP 110 becomes a warning, not an upgrade
If miner support remains at zero before the early August deadline, BIP 110 probably fails to become a network-wide Bitcoin change through its current path.
Supporters still have options. They can revise the proposal, push non-consensus policy filters, lobby mining pools, or move the argument into wallet and relay behavior. The spam debate will not vanish. Inscriptions, token metadata, fees, and block-space norms will keep returning because Bitcoin’s base layer is scarce by design.
The practical watch item is not just the deadline. Watch whether any major pool starts signaling, whether node adoption moves beyond low single digits, and whether exchanges or wallets publish chain-risk procedures before activation dates approach.
Bitcoin’s conservatism frustrates people who want quick fixes. BIP 110 shows why that conservatism exists. A messy fee market is painful. A rushed consensus split is worse.
Disclaimer: This XOOMAR analysis is for informational and educational purposes only. It is not financial, investment, legal, tax, or professional advice. It does not provide buy, sell, hold, price-target, portfolio, or personalized recommendations. Verify information independently and consult qualified professionals before making decisions.
Impact Analysis
- BIP-110 tests how Bitcoin handles contentious consensus changes without central leadership.
- With miner support at zero, enforcement by a minority could create chain-split risk.
- The dispute highlights a deeper fight over whether Bitcoin should prioritize payments or allow broader data usage.
BIP-110 Debate
| Side | Position | Key Concern |
|---|---|---|
| Backers | Restrict arbitrary data on Bitcoin for one year | Push Bitcoin back toward payments |
| Critics | Oppose the proposed spam fix | A contentious soft fork could be riskier than the spam problem |
Reported Bitcoin BIP-110 Miner Signaling
Primary Sources & Disclosures
Disclaimer: Content on XOOMAR is produced using AI-assisted research, drafting, and verification workflows and is intended for informational and educational purposes only. It does not constitute financial, investment, legal, tax, medical, or professional advice of any kind. All analysis reflects available information at the time of publication and may not be current. Verify information independently and consult qualified professionals before making decisions. Editorial policy
Written by
XOOMAR Insights Team
Research and Editorial Desk
The XOOMAR Insights Team pairs automated research with human editorial judgment. We track hundreds of sources across technology, fintech, trading, SaaS, and cybersecurity, cross-check the facts, and explain what happened, why it matters, and what to watch next. We do not just rewrite headlines. Every article is fact-checked and scored for reliability before it goes live, and we link back to the original sources so you can verify anything yourself.
