Bitcoin BIP-110 Raises Chain Split Risk As August Activation Window Nears

Bitcoin BIP-110 has pushed the Ordinals and data-storage fight back into the center of Bitcoin politics, with supporters trying to restrict non-monetary data and critics warning that the proposal could damage confidence in the network.

The proposal would cap most new output scriptPubKeys at 34 bytes, while allowing OP_RETURN outputs up to 83 bytes. It would also restrict larger data pushes, witness items, and some undefined witness versions during the deployment window. The goal is to reduce arbitrary data use from Ordinals inscriptions, Runes, Stamps, and other non-payment activity that consumes Bitcoin block space.

The risk comes from where the fight is being moved. Relay policy can shape what nodes choose to pass around. Consensus rules decide what blocks are valid. BIP-110 would move the dispute into consensus enforcement, meaning upgraded nodes would reject blocks that violate the new limits once activation conditions are met.

That turns a cultural fight over Bitcoin’s purpose into a technical coordination problem for miners, nodes, wallets, exchanges, custodians, and infrastructure providers.

Miner Support Remains Too Low For A Clean Rollout

BIP-110 uses bit 4 signaling and a 55% miner-signaling threshold across a 2,016-block difficulty period. If enough miners coordinate, the proposal can lock in through the normal signaling path. If they do not, the plan moves toward a more contentious activation window around August.

That is where the danger sits. Node support has grown through Bitcoin Knots, but miner signaling remains far below the level needed for a clean deployment. Nodes can enforce rules once they choose a chain, but miners decide which blocks are produced, and exchanges decide which chain receives market liquidity during any dispute.

The proposal’s signaling monitor has kept attention on the gap between visible node support and miner support. A soft fork with weak miner backing can create a rule mismatch: upgraded enforcing nodes reject blocks that other nodes and miners still treat as valid.

If that happens near the mandatory-signaling window, Bitcoin could face a temporary split around block validity. That does not automatically mean a permanent fork, but it can disrupt deposits, withdrawals, confirmations, wallet behavior, mining strategy, and market confidence while the network resolves which rules have economic backing.

Supporters Want Bitcoin Refocused On Money

BIP-110 supporters argue that Bitcoin should not become a general-purpose data-storage layer. Their view is that block space should primarily serve payments, savings, settlement, and self-custody rather than large inscriptions or arbitrary files.

That argument gained strength after Ordinals, Runes, and Stamps increased demand for non-payment transactions. Supporters say these uses raise storage and bandwidth burdens for every node operator while creating long-term chain bloat that future users must carry.

The proposal is designed as a temporary one-year restriction, not a permanent redesign of Bitcoin. Supporters see that as a safer way to reduce data abuse while keeping ordinary monetary activity intact.

The problem is that a temporary consensus change can still create permanent reputational damage if it is poorly coordinated. Bitcoin users tend to treat neutrality, predictable rules, and backward compatibility as core network strengths. BIP-110 now tests how much the community is willing to risk to discourage data-heavy activity.

Adam Back And Jameson Lopp Warn Against The Plan

Opposition from long-time Bitcoin figures has made the debate sharper. Blockstream CEO Adam Back argued that the proposed restrictions would not stop determined data users while still harming Bitcoin’s upgrade path and neutrality.

His criticism was blunt: “BIP-110 restrictions are bypassable. The innovation damage is not.” He also warned that Bitcoin’s strength comes from neutral, predictable rules rather than selective limits on how valid transactions are used.

Jameson Lopp has pushed back from a similar direction. His detailed review called BIP-110 “reckless and doomed to fail,” warning that the cure could become worse than the data problem it is trying to solve.

Their shared concern is not only Ordinals. It is governance. A low-threshold, contentious soft fork aimed at filtering unwanted uses of Bitcoin could weaken confidence that Bitcoin’s base layer remains politically neutral and hard to change.

Chain Split Risk Comes From Incompatible Rules

The chain-split concern is straightforward. If one group of nodes enforces BIP-110 and another group continues under existing rules, the network can disagree over which blocks are valid.

A miner could produce a block that includes a transaction violating BIP-110 limits. Non-enforcing nodes would treat that block as valid if it satisfies existing Bitcoin rules. BIP-110 enforcing nodes would reject it. From that point, the network can diverge until hash power, economic nodes, exchanges, and users converge on one rule set.

That kind of split would be especially sensitive because Bitcoin is the market’s reserve crypto asset. Exchanges would need to manage deposits and withdrawals carefully. Custodians would need chain-handling policies. Wallets would need confirmation guidance. Miners would need to choose which rules to follow. Traders would price the uncertainty immediately.

Bitcoin has survived political and technical fights before, but chain-split risk around a data-filtering proposal is a difficult sell for institutions that mainly want predictable settlement and monetary neutrality.

August Puts Bitcoin Governance Under Pressure

The next phase will depend on miner behavior. Strong miner support would reduce the risk of a disorderly activation. Continued weak signaling would leave BIP-110 exposed as the August window approaches, especially if node support keeps rising through Bitcoin Knots while mining pools remain unconvinced.

The debate is larger than OP_RETURN. It is a fight over whether Bitcoin should actively defend a narrow monetary use case at the consensus layer or preserve broad transaction neutrality even when some users fill block space with data that others consider spam.