|

Proposal to Temporarily Cap Bitcoin Transaction Data Gains Support From 583 Nodes

🫡

Support is rising for a Bitcoin proposal that might briefly 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 short lived 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 Improvement Proposal 110 (BIP-110) is at present signaling help from 583 nodes, or about 2.38% of the community, in accordance to data from The Bitcoin Portal.

Out of roughly 24,481 reachable nodes, these backing the proposal are primarily running Bitcoin Knots, an alternate node implementation typically favored by operators important of latest modifications to Bitcoin Core.

BIP-110 Proposes One-Year Cap on Bitcoin Transaction Data

BIP-110 proposes a short lived mushy fork that might reintroduce strict limits on transaction information on the consensus degree.

Specifically, it caps transaction output sizes at 34 bytes and restricts OP_RETURN information, a script used to embed arbitrary data into transactions, to 83 bytes.

The mushy fork is designed to final for one 12 months, after which the boundaries could possibly be prolonged, modified or allowed to expire.

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 12 months.

The transfer was controversial and met with widespread criticism from elements of the Bitcoin neighborhood, which argued the change was made with out enough consensus.

OP_RETURN has lengthy been a flashpoint in Bitcoin governance debates. While it permits use circumstances comparable to timestamping and metadata anchoring, critics say uncapped information fields encourage blockchain spam and non-financial use of block house.

Larger information payloads enhance storage and bandwidth necessities for nodes, elevating considerations that operating a full node may develop into cost-prohibitive for on a regular basis customers.

Critics of the Core replace argue that increased {hardware} calls for threat undermining certainly one of Bitcoin’s defining options, which is the power 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 compared unchecked data usage 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 Frame Proposal as Temporary Fix

Supporters of BIP-110 see the proposal as a corrective measure relatively than a everlasting coverage shift.

By making the mushy fork explicitly momentary, its authors purpose to give the community time to assess the affect 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 removal of OP_RETURN limits, arguing that synthetic caps do little to deter spam and will as an alternative push undesirable exercise into different elements of the protocol.

From this view, market charges ought to decide how block house is used.

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

Similar Posts