BIP 110 Fork Looms With Zero Miner Support
As Bitcoin's BIP 110 fork deadline approaches, miner support remains at zero. The proposal would limit arbitrary data for one year, but experts like Michael Saylor and Adam Back warn that a consensus battle could pose greater risks than the spam it aims to fix.
Quick Take
BIP 110 would cap arbitrary data on Bitcoin for one year.
Miner support is at zero as the fork deadline nears.
Saylor and Back argue a consensus fight is riskier than spam.
Market Impact Analysis
BearishPotential contentious fork could increase uncertainty and negative sentiment, but low miner support reduces likelihood of material impact.
Speculation Analysis
Key Takeaways
- Zero miner support for the BIP 110 fork near its deadline makes a chain split extremely unlikely.
- The proposal would have capped arbitrary data, including Ordinals, for one year to filter spam.
- Influential figures like Michael Saylor and Adam Back argued a contentious fork poses greater systemic risk than spam.
What Happened
Bitcoin's BIP 110 proposal is set to expire as its fork deadline approaches with zero miner support. The upgrade aimed to cap arbitrary data—such as Ordinals inscriptions and BRC-20 tokens—for one year, responding to fears that spam was congesting the network. However, no mining pool signaled readiness to adopt the soft fork. Influential figures like Michael Saylor and Adam Back warned that a forced change without broad consensus could splinter the blockchain, posing greater dangers than the spam itself. With the deadline imminent and hash rate backing at nil, the fork is effectively dead, averting a contentious chain split.
The Numbers
The starkest data point is 0%—the proportion of Bitcoin’s hash rate supporting BIP 110’s activation. For context, safe protocol upgrades typically require 95% or more miner signaling over a defined period. The proposal’s one-year cap targeted a category of transactions often labeled “spam,” but no reliable volume estimates were put forward to justify the radical measure. The absence of even exploratory signaling underscores how far the proposal was from becoming a reality.
Why It Happened
Disagreement over arbitrary data lies at the heart of the stalemate. Critics decry data-heavy transactions as blockchain bloat that drives up fees and node costs, while advocates see them as legitimate, innovative uses of block space. A forced fork without near-unanimous agreement risked splitting Bitcoin into two chains, undermining its store-of-value narrative and trustless guarantees. The community’s paramount goal—preserving consensus—ultimately sidelined the proposal in favor of stability.
Broader Impact
The BIP 110 episode reinforces the conservative nature of Bitcoin’s governance. Contentious forks remain an off-limits tool, even when technical disagreements flare. This reluctance will likely steer future spam mitigation discussions toward non-fork approaches, such as node-level policy changes or fee market adjustments, which avoid fracturing the ecosystem.
What to Watch Next
- Whether BIP 110 is formally abandoned or repackaged with softer parameters.
- Proposals for spam reduction that don’t require a hard or soft fork, like changes to mempool policy.
- Developer and miner sentiment shifts that could indicate growing willingness to address arbitrary data in future upgrades.
This article is for informational purposes only and does not constitute financial advice.
Always late to trends?
Join for the latest news, insights & more.
Disclaimer: Bytewit is an independent media outlet that delivers news, research, and data.
© 2026 Bytewit. All Rights Reserved. This article is for informational purposes only.
