BIP-110 Heads Toward Defeat as Miner Support Hits Zero and Bitcoin’s Biggest Voices Push Back
When BIP-110 first attracted serious attention earlier this year, miner signaling sat at approximately 0.31% of total hashrate, roughly 5 exahashes per second out of a network total near 940 EH/s. As of July 12, 2026, that number has dropped to 0.00%. CoinDesk confirmed yesterday that not a single block in the current signaling window carries BIP-110 support, with the mandatory activation window approaching block 961,632 between August 7 and 15.
The proposal, authored by Dathon Ohm and advanced to Complete status on June 30, seeks a one-year soft fork to restrict non-financial data on the Bitcoin blockchain, targeting Ordinals inscriptions, Runes, BRC-20 tokens, and large OP_RETURN payloads by capping transaction output data at 34 bytes and restricting OP_RETURN usage to 83 bytes. Standard monetary transactions would remain fully valid throughout.
The Bitcoin Community Has Spoken
The opposition from Bitcoin’s most prominent voices arrived this week. Strategy executive chairman Michael Saylor posted publicly on July 11 that BIP-110 turns a spam dispute into a consensus change that would invalidate currently valid, fee-paying transactions, warning that the precedent itself is the real danger. “There are 110 things more dangerous to Bitcoin than spam,” he wrote, adding that the community should save its energy for threats that actually matter.
Blockstream CEO Adam Back, whose hashcash design is cited in the Bitcoin whitepaper, was equally direct. Bitcoin, he said, “respectfully says no” to policing other people’s transactions through code. His message to BIP-110 supporters was plain: their permissionless recourse is to fork, but Bitcoin will not be joining it. Developer Jameson Lopp has also called the proposal’s activation parameters reckless, warning it could break compatibility with existing protocols and scripts.
What Happens Now
BIP-110 uses a modified user-activated soft fork mechanism requiring 55% miner signaling rather than the traditional 95% threshold. Even at that significantly lower bar, it cannot reach lock-in without a major pool, and no major pool including Foundry USA, Antpool, ViaBTC, or F2Pool has signaled support. Ocean pool, run by Bitcoin Core developer Luke Dashjr, has produced the handful of historical signaling blocks. Nothing in the current data suggests any reversal before the deadline.
If BIP-110 activates with near-zero miner support, nodes running BIP-110 software, primarily Bitcoin Knots variants, begin rejecting blocks that do not signal support and follow a slower minority chain. The main Bitcoin chain, carrying nearly all of the network’s hashrate and running Bitcoin Core, continues unchanged. Exchange and custodian operations on the main chain are unaffected. BIP-110 in its current state appears set to produce a small, isolated minority chain rather than any network-wide change.