BIP-110 Fork Deadline Looms With Miner Support at Zero

Bitcoin's most contentious governance battle of 2026 is heading toward a hard wall: the BIP-110 Reduced Data Temporary Soft Fork faces a voluntary lock-in deadline at block 961,542, expected in early August, with miner signaling stuck at zero in the current period and node adoption confined to the low single digits, according to CoinDesk. Strategy founder Michael Saylor and Blockstream co-founder Adam Back both publicly rejected the proposal on July 11, 2026, with Saylor arguing the fork "turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions." On the Fear & Greed Index, sentiment sits at 26 (Fear), reflecting broad market caution that gives high-stakes protocol disputes extra visibility among investors weighing Bitcoin's longer-term governance integrity.

What BIP-110 Actually Proposes — and Why It Has No Miner Support

BIP-110 targets the two main routes by which non-financial data enters Bitcoin blocks. First, it would cap OP_RETURN — the standard "note field" for small data payloads — back to its older, smaller size limit. Second, it would block most arbitrary data chunks above 256 bytes and restrict certain script formats used primarily for data storage. The practical effect would be to sharply curtail Ordinals inscriptions, token metadata schemes, and image data that has proliferated inside Bitcoin's witness data since an October protocol change that supporters of BIP-110 cite as a turning point toward Bitcoin-as-database rather than Bitcoin-as-money.

Critically, BIP-110 does not use the traditional 95% miner-signaling threshold for soft fork activation. Its designers opted for a user-activated soft fork (UASF) mechanism with a 55% miner-signaling threshold — already far below the historical standard. Even at that significantly lower bar, current signaling has never exceeded approximately 1% in any period and sits at zero now, with no major mining pool backing the proposal, per the BIP-110 signaling monitor cited by CoinDesk. The current signaling window runs from block 957,600 to 959,615. After the voluntary lock-in deadline at block 961,542 passes, nodes running BIP-110 software would begin rejecting blocks that do not signal support, with full activation projected around September 2026.

Node adoption tells the same story. Support is concentrated almost entirely in Bitcoin Knots, an alternative client to the dominant Bitcoin Core software. Bitcoin Core — run by the overwhelming majority of full nodes globally — has not adopted BIP-110, meaning the fork, if it activates at all, would produce a minority chain rather than a network-wide consensus change.

Saylor, Adam Back, and the Precedent Argument

The opposition from Michael Saylor and Adam Back carries particular weight given their standing in the Bitcoin ecosystem. Saylor posted on July 11, 2026, that "there are 110 things more dangerous to Bitcoin than spam," and framed the real danger as the precedent of turning a spam dispute into a consensus change.isuse but as the precedent of using a consensus rule to determine which fee-paying transactions are valid. His position: the fight should not be elevated from a social or policy dispute to a protocol-level enforcement mechanism.

Adam Back, whose Hashcash proof-of-work design is cited directly in Satoshi Nakamoto's Bitcoin whitepaper, addressed the proposal's newer backers at length, stating plainly that "Bitcoin respectfully says no to what you want" and that their recourse, if unconvinced, is to fork away — but that "bitcoin won't be joining it." Back's framing points to a long-established principle in Bitcoin governance: changes require genuine, distributed opt-in from thousands of independent node operators and miners, not a vocal minority enforcing rules on a reluctant majority.

The institutional context matters here too. Bitcoin treasury vehicles and ETF products are directly exposed to chain-split risk, however small. Empery Digital, a publicly listed Bitcoin treasury company, this week sold approximately half of its BTC holdings to fund an AI data center project — a move that signals at least one corporate treasury is actively repositioning rather than simply accumulating. Separately, the crypto IPO market has stalled as capital rotates toward AI and macro uncertainty weighs on new listings. Both developments reflect an environment where protocol-level uncertainty is the last thing institutional BTC holders want layered on top of existing macro pressure. For deeper reading on how Bitcoin ETFs compare to direct Bitcoin ownership in scenarios like this, CoinHours has a comprehensive breakdown.

Background: Bitcoin's Resistance to Change Is a Feature, Not a Bug

BIP-110 is unlikely to be the last attempt to restrict non-financial data on Bitcoin, but its near-certain failure illustrates something fundamental about how the network governs itself. Bitcoin has no CEO, no board, and no formal amendment process. Changes propagate only when an overwhelming supermajority of independent node operators and miners choose to run updated software. That design is intentional — and traces directly to Bitcoin's cypherpunk origins. For historical context on why Bitcoin was architected this way from the genesis block forward, see our guide on the History of Bitcoin Part 1: Cypherpunks to Genesis Block.

The underlying concern driving BIP-110 is not without merit. Blocks have carried substantially more non-financial data since the October 2025 changes, and the question of whether Bitcoin's block space should be treated as a general-purpose data layer is a legitimate one. But Bitcoin's answer to that question — as Back put it — is delivered through the consensus mechanism itself, not through a minority enforcing rules on a non-consenting majority. For investors tracking how this interacts with long-term market positioning, WealthWatchPro macro market analysis provides broader context on protocol governance risk and institutional Bitcoin exposure.

What to Watch Before the August Lock-In Deadline

The most important metric to monitor is miner signaling through the current window (blocks 957,600 to 959,615). Any meaningful uptick from zero toward the 55% threshold would be a significant surprise given current pool-level opposition, but it would change the calculus materially. Watch for any major mining pool — Foundry USA, AntPool, or F2Pool — publicly shifting position; none has done so as of July 12, 2026.

Node counts running BIP-110-compatible software (principally Bitcoin Knots) are also worth tracking. If adoption remains in the low single digits at lock-in, the fork produces an economically marginal minority chain that exchanges and ETF custodians would likely not credit. Conversely, any sign that Bitcoin Core maintainers are considering incorporating BIP-110 language — currently zero indication — would immediately reprice the probability of a network-wide change. The September activation window, if reached, is when custodians and exchange operators would need to formally communicate their chain-split policies to users.

For Bitcoin ETF holders specifically, the practical near-term risk is low given the support numbers, but the governance debate itself is a signal worth tracking: it reflects genuine tension inside the Bitcoin developer community over the protocol's long-term identity. How that tension resolves — through soft fork, social consensus, or persistent minority chains — will shape Bitcoin's positioning as a settlement layer versus a programmable data platform in the years ahead. The August deadline, block 961,542, is the next concrete marker.