← Back to Webthreepedia
WEBTHREEPEDIA RESEARCH

[DEEP DIVE] BIP-110 Bitcoin Spam Fork Dies at 0% Miner Support

Zephyra|July 20, 2026|BPF
EXECUTIVE SUMMARY

BIP-110, formally titled the Reduced Data Temporary Softfork, is heading toward its August 2026 mandatory signaling window with miner support at 0.31% of total network hashrate — roughly 5 EH/s out of approximately 940 EH/s. The proposal, which would restrict non-monetary data in Bitcoin transact...

"BIP 110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions. That precedent is the danger." — Michael Saylor, Executive Chairman, Strategy (MicroStrategy)

Executive Summary

BIP-110, formally titled the Reduced Data Temporary Softfork, is heading toward its August 2026 mandatory signaling window with miner support at 0.31% of total network hashrate — roughly 5 EH/s out of approximately 940 EH/s. The proposal, which would restrict non-monetary data in Bitcoin transactions for one year, needs 55% miner signaling to activate. It has never exceeded 1%.

The proposal has drawn public opposition from Strategy founder Michael Saylor, Blockstream CEO Adam Back, and BIP editor Mark Erhardt, who called it "a misguided and unusually careless softfork proposal." Bitcoin Core has not endorsed it and no implementation has been merged into the reference client. Only Bitcoin Knots, a minority client maintained by developer Luke Dashjr, supports the rules with manual configuration.

What began as a technical dispute over Ordinals inscriptions and blockspace allocation has become a stress test of Bitcoin's governance model — one the proposal appears to have failed decisively, with implications for how future consensus changes are evaluated.

Table of Contents

  1. What BIP-110 Proposes
  2. The Activation Mechanism and Timeline
  3. Miner Signaling Data
  4. The Economic Case Against Filtering
  5. Opposition From Key Figures
  6. The Ordinals Context: Blockspace and Revenue
  7. Chain Split Risk Assessment
  8. Governance Implications
  9. Key Takeaways
  10. Conclusion

What BIP-110 Proposes

Published on December 5, 2025, under the pseudonym "Dathon Ohm" — with Bitcoin Core developer Luke Dashjr credited for the original draft and advisory role — BIP-110 introduces seven temporary consensus rules designed to restrict non-financial data on Bitcoin's base layer:

  • Output script cap: New outputs limited to 34 bytes
  • OP_RETURN restriction: Outputs capped at 83 bytes (reversing Bitcoin Core v30's October 2025 increase to 100,000 bytes)
  • Witness data limit: Data pushes capped at 256 bytes
  • Taproot restrictions: Limits on annexes, control blocks, and certain opcodes commonly used for inscriptions

All rules would expire after approximately 52,416 blocks — roughly one year. UTXOs created before activation are grandfathered. The stated purpose: preserve Bitcoin as a "sound money" network by excluding images, tokens, and arbitrary data embedded through Ordinals, BRC-20, and Runes protocols.

The Activation Mechanism and Timeline

BIP-110 uses a user-activated soft fork (UASF) mechanism with a modified signaling threshold:

| Parameter | BIP-110 | Traditional Soft Fork | |---|---|---| | Miner signaling threshold | 55% | 95% | | Signaling method | Version bit 4 | Version bits | | Early lock-in block | 961,542 | Varies | | Mandatory signaling start | ~Block 961,632 | N/A | | Projected activation | ~Block 965,664 (~Sept 1, 2026) | Varies | | Duration | ~52,416 blocks (~1 year) | Permanent |

The 55% threshold is substantially below the 95% convention used in prior Bitcoin soft forks such as SegWit. Proponents argue the lower bar reflects urgency. Critics say it invites network fragmentation.

The mandatory signaling window is expected to open between August 7-15, 2026. At that point, nodes running BIP-110-enforcing software (primarily Bitcoin Knots) would begin rejecting blocks that fail to signal.

Miner Signaling Data

As of mid-July 2026, BIP-110 has effectively no mining industry support:

  • Current hashrate support: 0.31% (~5 EH/s of ~940 EH/s total)
  • Peak support: Below 1% in every difficulty period since signaling opened
  • Node support: ~583 nodes out of ~24,481 (2-3%)
  • Pools signaling: Only Ocean, operated by Luke Dashjr, which mined the first signaling block in March 2026
  • Major pools signaling: None

According to BGeometrics tracking data, support has ranged between 0.1% and 0.7% across most measurement periods. The proposal requires 1,109 signaling blocks per 2,016-block difficulty period to achieve lock-in — approximately 110 per day for two weeks.

The Economic Case Against Filtering

The economic argument against BIP-110 centers on fee revenue. Data-bearing transactions pay fees like any other. Restricting them removes demand from fee markets at a time when Bitcoin's block subsidy is declining.

Key data points:

  • Post-halving fee share: Transaction fees fell from ~7% of miner revenue in 2024 to ~1% in 2025, an 82% decline according to The Block's 2026 mining outlook
  • Ordinals peak impact: BRC-20 transactions generated over 5,000 BTC in cumulative fees since the protocol launched
  • Runes fee contribution: Approximately 45% of mining fees in the months following Runes' April 2024 launch came from Runes transactions
  • Block size impact: Average block size rose from 1.18 MB to 1.74 MB after Ordinals launched — a 47% increase, driven primarily by witness data
  • Ordinals sales volume: March 2026 alone saw nearly $47 million in Ordinals secondary market sales

Saylor's position is explicit: suppressing fee-paying transactions weakens miner security incentives. With block subsidies halving every four years, inscription-based fee demand is one of the few demonstrated sources of organic transaction fee growth.

Opposition From Key Figures

Michael Saylor (Strategy, 843,775 BTC treasury): Published what he called "110 reasons" against BIP-110 on July 19, 2026. Central thesis: "The proposed cure is more dangerous than the condition. BIP 110 would use consensus to narrow valid activity, constrain future options, complicate deployment, and establish a precedent it cannot later erase." Saylor argues Bitcoin "cannot read intent" and that distinguishing between acceptable and unacceptable transaction types sets a precedent for future censorship of privacy tools, corporate applications, or any other disfavored use case. His proposed alternative: market-based fees and relay policies, not consensus changes.

Adam Back (Blockstream CEO): Described BIP-110 as a "literal downgrade" and called consensus-level content filtering antithetical to Bitcoin's design. Told BIP-110 proponents to "group together and fork away" if they want different rules.

Mark Erhardt (Bitcoin Core BIP editor): Called it "a misguided and unusually careless softfork proposal." Stressed that assigning the BIP number was procedural, not an endorsement.

Jameson Lopp (Casa co-founder): Opposed the proposal, emphasizing Bitcoin's value as a "dependable anchor for other systems" — a role undermined by subjective content filtering.

Peter Todd (Bitcoin developer): Demonstrated the proposal's limitations by embedding the full BIP-110 text into transactions that would comply with the new rules — illustrating that determined users can circumvent content restrictions.

The Ordinals Context: Blockspace and Revenue

The BIP-110 debate is a direct product of the Ordinals protocol, launched in January 2023. Ordinals enabled the inscription of arbitrary data — images, text, JSON — into individual satoshis using Taproot's script-path spending. This spawned BRC-20 tokens, Runes, and a broader ecosystem of non-monetary Bitcoin applications.

At peak activity in August 2023, daily inscriptions exceeded 400,000. Activity has since declined significantly. Proponents of BIP-110 argue this decline undermines the urgency for the proposal. Opponents argue it proves the market self-regulates without consensus intervention.

The maximum theoretical data capacity per block is 4 MB under current SegWit rules. At full utilization, this adds approximately 210 GB per year to the blockchain. Full nodes currently require approximately 600+ GB of storage for the complete chain history, making the incremental cost of inscription data a measurable but manageable burden for operators.

Chain Split Risk Assessment

The primary risk vector is not activation — which appears virtually impossible at current support levels — but the behavior of BIP-110-enforcing nodes during the mandatory signaling window.

If a small number of nodes running Bitcoin Knots with BIP-110 rules enabled begin rejecting non-signaling blocks after the mandatory window opens, those nodes would diverge from the main chain. The practical impact would be limited given the node count (~583), but it creates edge cases for users relying on those nodes for transaction validation.

Bitcoin Core developer warnings have been direct: users should verify which client software their nodes run before the August window opens. A Bitcoin Core developer has warned users to be cautious with BTC transfers as the deadline approaches.

The 55% activation threshold, rather than the standard 95%, amplifies governance concerns. Even if miner support hypothetically reached the threshold, 45% of hashrate would be producing blocks that a significant minority of nodes would reject — a recipe for chain fragmentation.

Governance Implications

BIP-110's failure carries three significant governance lessons:

1. The 95% threshold serves a purpose. Previous Bitcoin soft forks required near-universal miner agreement precisely to prevent the fragmentation risks BIP-110 introduced by lowering the bar to 55%. The market's rejection of the lower threshold suggests broad consensus that the high bar is a feature, not a bug.

2. Content-neutral consensus is valued. The unified opposition from figures spanning Bitcoin's ideological spectrum — from maximalist Saylor to cypherpunk Back to institutional-facing Lopp — indicates that subjective content filtering at the consensus layer crosses a line the ecosystem is unwilling to cross. Fee markets, mempool policies, and relay rules are the accepted mechanisms for managing blockspace demand.

3. Governance-as-designed worked. As Bitfinex's analysis noted, the episode demonstrates that "even proposals framed as defending the network cannot easily change its core rules without broad agreement." For institutional allocators, this is a data point supporting Bitcoin's resistance to arbitrary rule changes — a property that underpins its value proposition as a neutral settlement layer.

Key Takeaways

  • BIP-110 has 0.31% hashrate support with an August 7-15 mandatory signaling deadline requiring 55%. Activation is not viable.
  • Only Ocean pool (operated by Luke Dashjr) has signaled. No major mining pools have committed.
  • Bitcoin Core has not endorsed or merged any BIP-110 implementation. The reference client does not support it.
  • Michael Saylor, Adam Back, Mark Erhardt, Jameson Lopp, and Peter Todd have publicly opposed the proposal.
  • The 55% activation threshold — 40 points below the 95% convention — was itself a source of opposition, separate from the content-filtering debate.
  • Chain split risk exists but is limited to a small minority of Bitcoin Knots nodes, not a network-wide event.
  • The economic case for content-neutral blockspace is strengthened by declining block subsidies and the demonstrated fee revenue from inscription-related transactions.

Conclusion

BIP-110 will almost certainly expire without activating. Its mandatory signaling window opens in early August 2026 with support at a fraction of a percent, 175x below the required threshold. No major mining pool, no reference client, and no prominent Bitcoin figure has endorsed it.

The proposal's significance lies not in what it would have done — restrict non-monetary data for one year — but in what its failure reveals about Bitcoin's governance. The network rejected content-based transaction filtering at every level: miners, developers, node operators, and large holders. The mechanism for managing blockspace demand remains the fee market, not consensus rules.

For the broader Web3 ecosystem, BIP-110's trajectory provides a case study in how decentralized governance handles contentious proposals. The outcome was not predetermined by any single actor. It emerged from the aggregated decisions of thousands of independent participants — each evaluating whether the proposal created or destroyed economic value. The answer, measured in hashrate, was unambiguous.

Sources & References

  1. Michael Saylor calls Bitcoin's new BIP-110 proposal 'a bad idea' — CoinDesk, July 19, 2026
  2. Bitcoin's BIP-110 sparked a fight over who gets to decide the future of Bitcoin — CoinDesk, July 14, 2026
  3. BIP-110 fork deadline nears with miner support at zero — CoinDesk, July 12, 2026
  4. Michael Saylor opposes BIP 110, calls for Bitcoin neutrality — Crypto Briefing, July 2026
  5. BIP-110 miner support struggles ahead of August deadline — Crypto Briefing, July 2026
  6. BIP-110 and Bitcoin's High Bar for Consensus Change — Bitfinex Blog, July 2026
  7. Saylor's 110-Point Case Against BIP-110 — TFTC, July 2026
  8. BIP-110 Falls Flat: Zero Miner Support — TechTimes, July 14, 2026
  9. BIP-110 Signaling Tracker — BGeometrics, June 2026
  10. 2026 Bitcoin Mining Outlook — The Block, 2026
  11. BIP-110 Official Proposal — BIP-110.org
  12. Bitcoin BIP-110 Proposal Reopens Fight Over Ordinals — NewsBTC/TradingView, July 2026