BIP-110 Reignites Bitcoin’s Blocksize War Fault Lines Ahead of August UASF Deadline

BBTC$64,761.00▲0.21% is fighting itself again. A proposed soft fork called BIP-110 — which would temporarily restrict non-financial data embedded in Bitcoin transactions at the consensus level — has split developers, miners, and node operators ahead of a user-activated soft fork (UASF) expected in August, reopening governance wounds that most in the community assumed had healed after the 2017 SegWit resolution.

The proposal’s stated intent, per its GitHub text, is to “set Bitcoin back on the path to becoming the world’s money by rejecting the standardization of data storage as a supported use case.” Plain English: limit what proponents call spam — arbitrary data inscribed into Bitcoin blocks by protocols that have nothing to do with payments. Jameson Lopp’s Cypherpunk Cogitations blog frames BIP-110 as an act of protection, preserving Bitcoin’s core function as money by pushing out what its backers call parasitic data storage.

The opposition sees something darker. Users on Reddit’s r/Bitcoin have described BIP-110 as “a coercive change to Bitcoin to radically reduce its flexibility” — one that “even disables OP_IF” and “nukes the ability to do safe upgrades.” Unverified social media claims, yes; but they’ve landed hard enough to mobilize real resistance. OP_IF is a fundamental conditional opcode in Bitcoin’s scripting language, and disabling it would constrain how smart contracts and conditional transactions function on-chain. Supporters contest the characterisation. The fear alone, though, has been enough to organise opposition.

Then there’s the classification fight. It matters more than it sounds. A Start9 community forum post from March 2026 argues that BIP-110 is not a soft fork at all but a hard fork — a distinction with enormous consequences, because soft forks are backward-compatible and hard forks are not, carrying real chain-split risk. If BIP-110’s critics are right about the classification, the proposal is far more disruptive than its proponents admit. If they’re wrong, the accusation is a political weapon designed to bleed momentum. Either way, the inability to agree on what to even call BIP-110 tells you everything about how little trust exists between the two camps.

CoinDesk reported on July 14 that the fight is fundamentally about “who gets to decide the future of Bitcoin” — a question that cuts to the bone of how the protocol actually governs itself. There is no CEO. No board. No foundation with binding authority. Changes require rough consensus among developers, adoption by node operators, and ultimately signaling from miners; when those groups disagree, the mechanism of last resort is the UASF — users and nodes enforcing a rule change without miner majority.

The UASF is a historically charged tool. Last prominently deployed during SegWit activation in 2017, it forced miners into adopting the upgrade by threatening to reject non-compliant blocks — a resolution, yes, but one that left scars. The 2015–2017 Blocksize Wars — which similarly divided miners, developers, and users over Bitcoin’s fundamental design — ended with the small-block faction prevailing and the big-block side splitting off into Bitcoin Cash. BIP-110 is not a re-litigation of block size. But it touches the same raw nerve: what is Bitcoin for, and who gets to answer that?

Node adoption is still marginal. Growing, but marginal. By January 24, 2026, nodes running BIP-110 had crossed 2.38% of the network, according to CoinTelegraph data via TradingView, as what the outlet termed the “spam wars” intensified. Two percent is not a mandate — it is, however, enough to signal a committed base willing to run the code before consensus is reached, a posture that historically precedes either adoption or a messy fork.

The Block reported on July 14 that the Bitcoin community remains divided over BIP-110 and the looming August UASF deadline. The timing is not accidental; August is close enough to create urgency but far enough out for both sides to dig in. Proponents are framing the fork as a necessary corrective against data-storage protocols that bloat the chain and drive up transaction fees for ordinary users. Opponents are calling it a power grab — an attempt by one faction of Bitcoin’s developer ecosystem to impose its vision of Bitcoin-as-money over Bitcoin-as-platform, using consensus rules to settle what should be a market dispute.

Both readings have merit. Which is exactly why the fight is so volatile. The data-storage protocols that BIP-110 targets have undeniably increased block pressure and transaction costs. But the proposed remedy — consensus-level restrictions on arbitrary data, potentially disabling conditional opcodes — would constrain Bitcoin’s programmability in ways critics argue are irreversible and dangerous, and whether the cure is worse than the disease is a genuinely open question with no neutral arbiter to decide it.

All of this is playing out against a backdrop of market anxiety. Bitcoin is trading at $64,865, up 0.43% in 24 hours and 4.53% over seven days, with a market cap of $1.30 trillion and BTC dominance at 56.3%. The broader crypto Fear & Greed Index sits at 25 out of 100 — Extreme Fear — as of July 15, 2026. A governance crisis is the last thing a market in that condition needs, but markets don’t schedule crises. Bitcoin’s price resilience suggests institutional buyers are either unaware of or indifferent to the BIP-110 dispute; the real price impact, if any, arrives only if the August UASF produces a chain split or a protracted activation conflict.

The August deadline is the flashpoint. If BIP-110 supporters push a UASF without broad consensus, they risk the same chain-split chaos that defined the Blocksize Wars’ final act. If they back down, the data-storage protocols they oppose continue operating unchecked — and the spam-war faction loses its best shot at a consensus-level fix. Either outcome reshapes what Bitcoin is, and who gets to define it.

Watch the node count. If BIP-110 adoption climbs sharply above its current single-digit percentage before August, the UASF attempt becomes more credible and more dangerous; if it stalls, the proposal dies the quiet death of most BIPs. The next signal will come from the developer mailing lists and the major mining pools, whose signaling — or deliberate silence — will determine whether August brings resolution or fracture.