Help is rising for a Bitcoin proposal that will quickly restrict the quantity of information embedded in transactions, as a debate over community spam and node decentralization intensifies.
Key Takeaways:
- BIP-110 has gained early traction, with 583 Bitcoin nodes signaling help for a brief cap on transaction information.
- The proposal seeks to reverse latest Bitcoin Core modifications that eliminated OP_RETURN limits.
- Supporters argue stricter information limits are wanted to curb spam and protect node decentralization.
Bitcoin Enchancment Proposal 110 (BIP-110) is at the moment signaling help from 583 nodes, or about 2.38% of the community, based on information from The Bitcoin Portal.
Out of roughly 24,481 reachable nodes, these backing the proposal are primarily working Bitcoin Knots, another node implementation typically favored by operators essential of latest modifications to Bitcoin Core.
BIP-110 Proposes One-12 months Cap on Bitcoin Transaction Knowledge
BIP-110 proposes a brief tender fork that will reintroduce strict limits on transaction information on the consensus degree.
Particularly, it caps transaction output sizes at 34 bytes and restricts OP_RETURN information, a script used to embed arbitrary info into transactions, to 83 bytes.
The tender fork is designed to final for one yr, after which the boundaries might be prolonged, modified or allowed to run out.
The proposal emerged in response to modifications launched in Bitcoin Core model 30, launched in October 2025.
That replace eliminated the long-standing 83-byte restrict on OP_RETURN information following a pull request first launched earlier within the yr.
The transfer was controversial and met with widespread criticism from components of the Bitcoin group, which argued the change was made with out enough consensus.
OP_RETURN has lengthy been a flashpoint in Bitcoin governance debates. Whereas it permits use instances reminiscent of timestamping and metadata anchoring, critics say uncapped information fields encourage blockchain spam and non-financial use of block area.
Bigger information payloads enhance storage and bandwidth necessities for nodes, elevating considerations that working a full node may turn out to be cost-prohibitive for on a regular basis customers.
BIP-110 RC3
pic.twitter.com/5KeoTCyhWV
— Justin (@innerhat) January 21, 2026
Critics of the Core replace argue that increased {hardware} calls for danger undermining one in all Bitcoin’s defining options, which is the flexibility for people to confirm the community utilizing consumer-grade {hardware}.
As node operation turns into costlier, they warn, the community may drift towards better centralization.
Bitcoin educator Matthew Kratter in contrast unchecked information utilization to a parasitic menace. He has argued that extreme spam may overwhelm the community’s underlying construction, weakening Bitcoin’s resilience over time.
BIP-110 Backers Body Proposal as Non permanent Repair
Supporters of BIP-110 see the proposal as a corrective measure quite than a everlasting coverage shift.
By making the tender fork explicitly short-term, its authors goal to present the community time to evaluate the impression of restored limits with out locking Bitcoin right into a long-term rule change.
Others stay unconvinced. Bitcoin Core contributor Jameson Lopp has defended the removing of OP_RETURN limits, arguing that synthetic caps do little to discourage spam and will as an alternative push undesirable exercise into different components of the protocol.
From this view, market charges ought to decide how block area is used.
The put up Proposal to Briefly Cap Bitcoin Transaction Knowledge Features Help From 583 Nodes appeared first on Cryptonews.