Bitcoin BIP-110 Fork Failed: What Actually Happened

BIP-110 was a proposal to let miners signal support for capping the size of "inscription" data — the Ordinals-style content some users embed in Bitcoin transactions — via a soft fork. Soft forks on Bitcoin don't activate by fiat; they need a voluntary supermajority of miners to signal readiness, and BIP-110 set that bar at 55%. There was no backup mechanism forcing the change through if signaling came up short, which matters, because it came up very short: only about 2.53% of hashpower signaled support heading into the activation window.

That's the whole story, mechanically. A pseudonymous mining group called Roughnecks, using infrastructure from Ocean — the pool whose team publicly backed BIP-110 — produced the first block under the new rules at block height 961,632. They managed two blocks total, spread over roughly 8 to 17 hours depending on which report you read, before the effort effectively stopped. Meanwhile, by Michael Saylor's estimate, more than 99.85% of Bitcoin's hashpower kept mining the unmodified chain exactly as before. A design that requires 55% agreement and gets 2.53% isn't a close call that narrowly failed — it's a system doing exactly what it was built to do when consensus isn't there.

Not in any way that matters to holders. The minority chain that Roughnecks mined fell between roughly 26 and 111 blocks behind the main chain within its first day, with the gap widening constantly since the vast majority of hashpower never touched it. To survive long-term, a minority chain needs enough of its own hashpower to complete a full difficulty adjustment — 2,016 blocks — at a pace that doesn't make mining it hopeless. At the rate it was producing blocks, that was never going to happen.

Just as important: no exchange, wallet provider, or major node operator treated the minority chain as a separate, tradeable version of Bitcoin. There was no listing, no "airdrop," no second BTC ticker to claim. Some miners running Ocean's DATUM mining protocol reportedly ended up mining the fork without realizing it, believing they were mining standard Bitcoin; Ocean has said it reimbursed those miners for the mix-up. That's an operational embarrassment for one pool, not a market event.

No. There's no new coin to claim, no wallet setting to change, and no exchange deposit or withdrawal freeze tied to this. The chain that would have required any action from holders — a genuine, sustained split with exchange support on both sides — never got off the ground. If you held BTC before block 961,632 and you hold it now, nothing about your coins has changed.

The clearest signal ahead of the failed activation was public opposition from figures with real weight in Bitcoin's ecosystem, including Strategy's Michael Saylor and Blockstream's Adam Back, who argued the proposal didn't have the backing to justify forcing a change this way. Their position held: the "economic majority" — the miners, exchanges, and node operators whose cooperation actually makes a fork stick — never showed up for BIP-110. That's a loss for the specific faction pushing to restrict Ordinals-style data through this method, and a mild vindication for Bitcoin's conservative, consensus-heavy approach to protocol changes.

Nobody gains a trading edge from this outcome. It's not the kind of event that creates winners in a price sense; the "winner" is the status quo. The debate over whether Bitcoin should limit non-financial data in transactions doesn't go away, but it reverts to informal discussion among developers and miners rather than an active fork attempt.

There's no announced second attempt at signaling from Ocean, Roughnecks, or the wider "Knots" node community as of Tuesday, though that's the thing worth watching over the next couple of weeks if this debate resurfaces. The event that will actually move Bitcoin's price is Wednesday's July CPI report: with Fed rate-cut odds for September already shifting on recent data, a soft inflation print would likely support the case for a cut and could be what finally pushes BTC through the resistance it's failed to clear multiple times this cycle, while a hot print would reinforce the case to hold rates and keep price capped in its current range.

The one thing this episode is worth filing away: a low-signaling soft fork with no forced-activation mechanism is close to risk-free for holders by design. That won't necessarily be true of every future contentious proposal — a push paired with an actual user-activated enforcement campaign, where nodes start rejecting non-compliant blocks at scale, is a different and riskier animal. This wasn't that. It was the safety mechanism working.