The Bitcoin civil war nobody signed up for: BIP 110 heads toward a fork deadline with miners absent

BIP 110 was always a long shot. The proposal, which would impose a one-year cap on arbitrary data carried inside Bitcoin transactions, reaches its activation window on 12 July 2026 with no measurable support from the mining pools whose hashpower would have to run the new rules. The absence is the story. The proposal is the excuse.

The fight, in plain terms, is over what Bitcoin is for. A loose coalition of node operators and developers want the chain to function as a settlement layer for money and nothing else, and they have spent two years watching the Ordinals and BRC-20 crowd use witness data to inscribe JPEGs, token tickers and other artefacts they consider spam. BIP 110 is the most concrete attempt yet to draw a line. The problem is that "spam" is in the eye of the protocol user, and the loudest voices against the proposal are the ones who built their businesses on the assumption that Bitcoin's base layer would keep absorbing whatever the market threw at it.

What the proposal actually does

BIP 110 introduces a one-year limit on the volume of arbitrary data a single transaction can carry, with the cap tuned to the size of a typical value transfer. The mechanism is a soft fork: nodes that adopt the rules reject blocks that exceed the cap, while old nodes continue to see those blocks as valid but accept a slower chain. In practice, the chain that respects the cap becomes the economic chain for participants running the new software, and the chain that ignores it forks away into a parallel asset.

The technical detail matters less than the political signal. For the first time, a credible coalition of full-node advocates is asking the network to vote, with hashpower, on whether inscribing a 200-kilobyte JPEG into the witness section of a transaction is a legitimate use of block space. The pro-cap side argues the question is economic: spam fills blocks, drives up fees, and crowds out payments. The anti-cap side argues the question is values: Bitcoin is a permissionless ledger, and what counts as a "legitimate" transaction is a question no soft fork should be answering.

Where the heavyweights are landing

The opposition is the loudest signal in the room. Strategy executive chairman Michael Saylor, whose company holds the largest single Bitcoin treasury of any public firm, and Blockstream CEO Adam Back have both publicly criticised the proposal, according to Cointelegraph's 12 July 2026 reporting. The argument, as Saylor and Back have framed it, is that turning a disagreement about transaction-level spam into a consensus-level fight introduces a categorically larger risk: a chain split, a replay-trading mess, two BTC tickers, two communities, two narratives. The cure, in this reading, is worse than the disease.

Cointelegraph's 12 July coverage also notes that the volume of Ordinals transactions has fallen sharply over the last two years. That context matters. The original Ordinals mania of 2023-2024 produced congestion, fee spikes, and a wave of media attention. By mid-2026, the inscribed-asset market is a fraction of its peak, and the fee market has long since reverted to a payments-driven equilibrium. The case for emergency intervention is harder to make when the emergency has already passed. The counter-case, advanced by proponents, is that the lull is a temporary reprieve, that the next inscription cycle will arrive when mempool economics turn favourable, and that the protocol should harden itself in advance.

The structural frame: who decides what Bitcoin is

The deeper argument is about governance, in a system explicitly designed not to have one. Bitcoin's de facto rule-making process runs through five overlapping centres of gravity: core developers who write the code, mining pools that signal on which software they will build, businesses that build on top of the chain, node operators who validate it, and the wider holder base that prices it. None of these groups can impose a change on the others. The system works because, in normal times, a rough consensus forms before any rule change is shipped.

BIP 110 is a stress test of that model. The pro-cap coalition has the node argument; the anti-cap coalition has the hashpower and the capital argument. If the proposal activates on 12 July with no mining support, it dies on arrival. If it activates with thin mining support and a chain splits, the market gets to decide which chain survives, and the decision will not be made on the merits of the data-cap question. It will be made on liquidity, exchange listings, custody support, and the path of least resistance for the largest holders. The Saylor-Back critique, on this reading, is not really about Ordinals. It is about the precedent: once you start soft-forking what is and is not a valid economic use of block space, you have started writing content moderation into the base layer.

What happens next, and what is still unclear

The activation window closes in the next few weeks if no further support materialises. The most likely path, on current signalling, is that BIP 110 expires as a missed proposal and the question is relitigated through a successor BIP that addresses the procedural objections. The least likely path, but the one that markets are quietly pricing, is a chain split and a brief period of two-tickers confusion that would resolve, as past splits have, on the side of the chain exchanges choose to custody.

What the public sources do not yet say is whether any major pool has changed its position in the final 72 hours before the window closes, or whether Cointelegraph's reported downturn in Ordinals transaction volume over the last two years has continued into mid-2026. The market for inscribing is quiet; whether it stays quiet is the variable the pro-cap side will be watching most closely. If the next inscription cycle does not arrive, the case for BIP 110 weakens on its own terms. If it does, expect the proposal to return in a different form, under a different number, with a coalition that has spent the interim months trying to win over a few of the pools whose absence has defined this round.

This article is the Monexus staff desk's read of the BIP 110 activation window. Where the wire coverage emphasised the personalities at the centre of the debate, the desk note here is that the more durable story is the precedent: the first serious attempt to soft-fork Bitcoin's data policy is also the first serious attempt to give a particular faction of node operators a binding veto over what runs on the chain. That fight is not over; the 12 July deadline is just the end of the first round.