Bitcoin governance fight over limits on data inscriptions

Bitcoin is approaching the activation window for BIP-110, which is tied to block 961,632 and sits fewer than 10,000 blocks away. The proposal would add consensus rules that make certain data-heavy transactions invalid for nodes that adopt the change. The measures target inscriptions such as Ordinals and Runes that embed text, images or token metadata directly on Bitcoin’s base layer.

BIP-110 sets a 55% miner signaling threshold for activation and includes a failsafe that would cause enforcing nodes to reject blocks that do not conform if the threshold is not met. Proponents say the rule would be temporary, expiring after about one year, and aim to reduce large arbitrary data payloads that increase storage, bandwidth and processing requirements for full-node operators.

Blockstream CEO Adam Back called the proposal technically deficient and warned that attempting to force the change without broad economic support could create a fractured, minority chain. Veteran developer Jameson Lopp described the plan as dangerous overreach and cautioned the code could strand funds and disrupt edge-case wallet behavior. Analyst Luis Marcano argued that nodes enforcing the new rules would reject noncompliant blocks and that mining power and market activity could migrate to the chain that remains valid under the altered rules.

On-chain enforcement so far is limited. The number of nodes running software configured to enforce BIP-110 remains low, major mining pools have not signaled support and most exchanges and custodians have not indicated plans to recognize a restricted ledger. Market infrastructure operators have said they would likely take defensive steps if a contested ledger appears, including temporary pauses on deposits and withdrawals, additional replay-protection checks and assessments of which chain to credit.

Critics also question the rule’s effectiveness. Some developers say users could hide arbitrary data in other transaction fields, which would reduce the proposal’s ability to stop the behavior it targets. Core developers warn that a time-limited change would require wallets, libraries and services to support two sets of consensus rules, adding operational complexity for businesses and developers.

The debate reflects a division in the Bitcoin community over whether the protocol should accept any valid transaction that pays fees or whether block space should be limited to preserve a monetary settlement function. The activation window around block 961,632 will determine whether the proposal advances, fails to activate, or triggers a contested fork with operational responses from miners, node operators and market intermediaries.