Proposal to Limit Bitcoin Transaction Data Gains Backing from 583 Nodes

Support is increasing for a Bitcoin proposal that aims to temporarily restrict the amount of data included in transactions, as discussions about network spam and node decentralization escalate.

Key Takeaways:

• BIP-110 has received initial backing, with 583 Bitcoin nodes indicating support for a temporary limit on transaction data.
• The proposal intends to revert recent Bitcoin Core modifications that eliminated OP_RETURN restrictions.
• Proponents contend that stricter data limitations are essential to reduce spam and maintain node decentralization.

Bitcoin Improvement Proposal 110 (BIP-110) is currently showing support from 583 nodes, which represents approximately 2.38% of the network, based on information from The Bitcoin Portal.

Among about 24,481 reachable nodes, those endorsing the proposal are mainly operating Bitcoin Knots, an alternative node implementation often preferred by operators critical of recent adjustments to Bitcoin Core.

BIP-110 Suggests One-Year Limit on Bitcoin Transaction Data

BIP-110 advocates for a temporary soft fork that would reestablish strict limits on transaction data at the consensus level.

In particular, it sets a cap on transaction output sizes at 34 bytes and confines OP_RETURN data, a script employed to embed arbitrary information into transactions, to 83 bytes.

The soft fork is intended to last for one year, after which the limits could be prolonged, altered, or allowed to lapse.

The proposal arose in response to changes implemented in Bitcoin Core version 30, which was released in October 2025.

This update abolished the longstanding 83-byte restriction on OP_RETURN data following a pull request first proposed earlier in the year.

The decision was contentious and faced significant backlash from segments of the Bitcoin community, which argued that the change was made without adequate consensus.

OP_RETURN has frequently been a contentious issue in Bitcoin governance discussions. While it facilitates use cases such as timestamping and metadata anchoring, critics argue that unlimited data fields promote blockchain spam and non-financial utilization of block space.

Larger data payloads heighten storage and bandwidth demands for nodes, raising concerns that operating a full node may become financially burdensome for average users.

BIP-110 RC3 pic.twitter.com/5KeoTCyhWV

— Justin (@innerhat) January 21, 2026

Opponents of the Core update assert that increased hardware requirements threaten to undermine one of Bitcoin’s fundamental characteristics, which is the ability for individuals to verify the network using standard consumer hardware.

As node operation becomes pricier, they caution, the network could trend toward increased centralization.

Bitcoin educator Matthew Kratter likened unchecked data usage to a parasitic danger. He argues that excessive spam could inundate the network’s foundational structure, eroding Bitcoin’s resilience over time.

BIP-110 Advocates Present Proposal as a Temporary Solution

Proponents of BIP-110 view the proposal as a remedial action rather than a permanent policy alteration.

By explicitly making the soft fork temporary, its creators aim to allow the network to evaluate the effects of reinstated limits without committing Bitcoin to a long-lasting rule change.

Others remain skeptical. Bitcoin Core contributor Jameson Lopp has supported the elimination of OP_RETURN limits, arguing that artificial restrictions do little to prevent spam and may instead drive unwanted activity into other areas of the protocol.

From this perspective, market fees should dictate how block space is utilized.

The post Proposal to Temporarily Cap Bitcoin Transaction Data Gains Support From 583 Nodes appeared first on Cryptonews.