• BIP-110 would temporarily restrict arbitrary or non-payment data in Bitcoin transactions by changing consensus validity rules.
  • The proposal would cap new outputs, limit OP_RETURN fields, restrict script-based data pushes and expire after 52,416 blocks unless extended.
  • Bitfinex frames the debate as a governance test, with supporters defending monetary purity and critics warning about neutrality, continuity, miner signalling and economic coordination risks during the expected August activation period.

Bitfinex’s breakdown of BIP-110 frames the proposal as more than another technical argument over Bitcoin transaction policy. The temporary soft fork would restrict arbitrary or non-payment data inside Bitcoin transactions, moving the debate from relay defaults toward what the network should recognize as valid at all. Supporters see a defense of Bitcoin’s monetary purity, while critics see a dangerous intervention in neutrality, continuity and coordination. For institutions watching Bitcoin’s adoption case, the dispute exposes Bitcoin’s slow but confidence-building governance, where even defensive rule changes face an unusually high bar.

BIP-110 would cap the size of new transaction outputs, limit OP_RETURN fields and restrict other script-based data pushes. It would grandfather UTXOs created before activation and expire after 52,416 blocks, or about one year, unless extended by a later consensus change. The proposal also reaches into parts of Taproot, including certain conditional script paths, which critics say could affect existing wallet and application assumptions. The design is temporary but not narrow, because it changes consensus validity rather than simply discouraging transaction relay.

Bitcoin’s data fight becomes a governance test

The proposal responds to expanded use of Bitcoin block space for Ordinals, BRC-20 tokens and Runes, which have carried information unrelated to direct bitcoin transfers since 2023 and added to onchain activity and fee pressure. The dispute intensified after Bitcoin Core v30 made relay and mining policy more permissive by allowing multiple OP_RETURN outputs and raising the default data-carrier setting from 83 bytes to 100,000 bytes. The core question is scarce block space, and whether valid, fee-paying transactions should be treated differently because of purpose.

Critics argue that consensus restrictions could create larger risks than the data they target. If only part of the network enforces BIP-110, miners, nodes, exchanges and custodians could diverge on which chain is valid, raising operational questions around deposits, withdrawals and liquidity. Public signalling from major mining pools has remained in the low single digits since May, far below the 55% threshold for early lock-in. The strongest warning is coordination failure, especially because mandatory signalling expected in August 2026 would not itself guarantee a viable economic chain. The result is unresolved: BIP-110 shows how hard it is to change Bitcoin’s rules, even when the stated goal is protecting Bitcoin’s monetary purpose under institutional scrutiny and pressure.