Bitcoin’s BIP-110 debate has moved back into focus as users argue over whether the network should temporarily restrict large OP_RETURN outputs and other non-payment data inside transactions.
The proposal would cap most new output scriptPubKeys at 34 bytes while allowing OP_RETURN outputs up to 83 bytes. It would also limit large data pushes and witness items, creating a consensus-level filter against some inscription, BRC-20, Runes, Stamps and other data-heavy transaction patterns.
The fight is not only about block space. OP_RETURN lets users place small pieces of data into provably unspendable Bitcoin outputs, while newer inscription-style systems use Bitcoin transactions to carry metadata, token instructions or file-like payloads. That activity has already pushed Runes and Alkanes into the center of Bitcoin’s block-space debate, with microtransaction-heavy activity recently dominating network usage.
Supporters Want Data Limits
Supporters of BIP-110 want Bitcoin refocused on payments, savings and monetary settlement rather than becoming a broader data-storage layer. The proposal’s temporary restriction model is designed to run for one year, with output, witness and Taproot-related limits aimed at reducing data bloat while leaving ordinary monetary transactions usable.
The strongest pro-BIP-110 argument is UTXO cost. Unspent outputs must be tracked by nodes, while large scripts and metadata-heavy patterns can increase the storage and validation burden over time. Supporters view that as a decentralization risk because higher resource demands can make full-node operation more expensive.
Bitcoin Knots has become the main visible software lane for users who want stricter filtering. Some supporters point to the share of nodes running Knots-compatible clients as evidence that the anti-spam camp has real user demand, though node counts, reachable-node samples and BIP-110-specific signaling can vary across dashboards.
Critics Warn Of Censorship And Split Risk
Opponents see the proposal as a censorship path because it moves a cultural dispute over transaction use into consensus rules. Bitcoin already has a fee market: valid transactions compete for block space, and miners choose which transactions to include. Critics argue that changing consensus rules to block certain data patterns weakens Bitcoin’s neutrality.
The coordination risk is also practical. BIP-110 would move beyond ordinary relay policy and into block-validity enforcement. A prior CryptoAdventure analysis warned that BIP-110 raises chain-split risk if nodes, miners and economic users do not line up around the same rules.
That concern has widened as Bitcoin figures continue debating how protocol changes should gain legitimacy. Michael Saylor’s recent comments tied Bitcoin changes to alignment between nodes, miners and holders, a framing that maps directly onto the BIP-110 fight.
Miner Signaling Remains The Key Checkpoint
BIP-110 uses version-bit signaling for miner support. The mainnet signaling monitor tracks blocks that set bit 4 for the proposal, separating miner behavior from broader node-client adoption.
That distinction matters because nodes can enforce rules, but miners produce blocks and exchanges assign liquidity to the chain that market participants treat as BTC. A large node minority without matching miner and economic support could create mempool divergence, rejected blocks or temporary settlement confusion during a contentious activation window.
The proposal remains a live Bitcoin governance fight, with supporters focused on spam, UTXO growth and inscription bloat, and opponents focused on censorship risk, fee-market neutrality and the danger of changing consensus rules without broad miner and market alignment.
