Bitcoin’s debate over non-monetary data has intensified as BIP-110 supporters call for stronger backing, while prominent critics warn that forcing activation could divide the network.
Robert Allen urged Bitcoin users concerned about blockchain spam to support the proposal rather than remain undecided. He acknowledged that BIP-110 is imperfect but described it as preferable to leaving the issue unaddressed.
Adam Back took the opposite position. He argued that the filter proposal carries technical defects, lacks broad agreement, and risks producing a low-hashrate minority chain instead of a widely accepted Bitcoin upgrade.
BIP-110 proposes a temporary soft fork that would tighten the amount and format of arbitrary data permitted inside Bitcoin transactions.
Its rules would generally limit new output scripts to 34 bytes, while permitting up to 83 bytes when the first opcode is OP_RETURN. Other large data pushes and witness items would face additional restrictions.
Supporters say the proposal targets inscriptions and other non-payment data that consume block space. Their concern is that growing storage and bandwidth requirements could make running a full node more expensive, placing pressure on Bitcoin’s decentralization.
The restrictions are designed to last for one year. That temporary period would allow developers and node operators to observe the effects before deciding whether similar limits should remain.
Allen directed his message toward users who oppose spam but remain hesitant about BIP-110. He argued that waiting for a perfect solution could allow the disputed activity to persist without a meaningful response.
His position reflects the view that node operators should actively enforce stricter monetary-use rules rather than depend only on relay policies or transaction fees to discourage non-financial data.
Early adoption began slowly. In January, 583 of 24,481 detectable nodes were reportedly running the BIP-110 implementation, representing 2.38% of the observed network.
Support later increased, with an implementation update in March estimating that BIP-110 software accounted for more than 8% of listening nodes. Node adoption, however, does not automatically establish miner support or guarantee enforcement on the chain with the greatest accumulated proof of work.
Back said the proposal’s supporters have dismissed concerns about its technical design. In his view, that has prevented the formation of both technical and ecosystem consensus.
A central dispute concerns activation. BIP-110 allows early enforcement if 55% of hash power signals are supported, far below the roughly 95% threshold associated with previous major Bitcoin upgrades.
Supporters argue that a lower threshold prevents a minority of miners from blocking action. Critics respond that 55% leaves too much room for incompatible blocks, chain disruption, and confusion among exchanges, wallets, miners, and node operators.
(adsbygoogle = window.adsbygoogle || []).push({});Back warned that weak miner participation could leave BIP-110 nodes following a separate chain with limited hash power. Such an outcome would turn an attempted soft fork into a contentious split in practical terms.
The argument now extends beyond transaction data. BIP-110 has become a wider test of how Bitcoin should handle protocol changes when users agree that a problem exists but disagree sharply over the proposed solution and its activation method.
