Bitcoin nodes running BIP-110 rise to 2.38% as OP_RETURN cap

2.38% of Bitcoin nodes back BIP-110 to temporarily cap transaction output and OP_RETURN sizes, igniting debate over spam, storage costs and centralization.

  • 2.38% of Bitcoin nodes (583 of 24,481) are signaling support for BIP-110.
  • BIP-110 would cap transaction output size at 34 bytes and limit OP_RETURN data to 83 bytes for one year.
  • The main software implementing the proposal is Bitcoin Knots, and node data is publicly available via node count records.
  • The removal of arbitrary data limits in Bitcoin Core version 30 in October 2025 sparked debate over spam and centralization.
  • Critics warn of increased storage costs and centralization; supporters argue filters do little to stop spam.

583 of 24,481 Bitcoin nodes — about 2.38% — are signaling support for BIP-110, which seeks a temporary soft fork to limit data in transactions, according to node count data. The proposal sets output sizes at 34 bytes and caps OP_RETURN entries at 83 bytes, with a planned one-year deployment as detailed on the BIP-110 GitHub page. The primary implementation is Bitcoin Knots.

- Advertisement -

The change aims to reduce the amount of arbitrary data written to the ledger. A deployment timeline and related materials are available on the deployment timeline. Proponents say the limits will lower long-term node storage growth and help keep node hardware requirements within consumer-grade ranges.

The debate intensified after Bitcoin Core released version 30 in October 2025 and removed the arbitrary data cap via a controversial pull request. That pull request is documented on GitHub at the linked pull request, which drew broad opposition from parts of the community.

Critics argue that uncapped arbitrary data can incentivize spam, raise storage costs for node operators, and push the network toward centralization. Educator Matthew Kratter warned of that outcome, saying "It’s like one of those parasitical plants, like ivy, completely covering a tree, eating up the tree, and then the inner scaffolding collapses, and the ivy collapses because it’s basically destroyed the structure. This is what spam has the potential to do to Bitcoin." His comment is available in a linked video.

Others, including Jameson Lopp, have defended the uncapped limit and have argued that filters do little to stop spam; see his statement on X.

- Advertisement -

Readers are encouraged to verify details and review the platform’s editorial policy.

✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.

Previous Articles:

- Advertisement -

Latest News

Global Survey: 39% of Crypto Users Get Paid in Stablecoins

A YouGov survey finds 39% of crypto users receive income in stablecoins, while 27%...

Bank Slashes 70% Off XRP Forecast, Citing Market Weakness

Standard Chartered significantly lowered its price forecast for XRP, now predicting it will reach...

Bitcoin Long-Term Holders Capitulate as Support Weakens

Long-term Bitcoin holders accumulated less during February's price dip compared to events like the...

Logan Paul Sells Pokémon Card for Record $16.5M

YouTuber Logan Paul sold a rare Pokémon card for a record $16.5 million, netting...

Nagel Backs Euro Stablecoins to Counter US Dollar Dominance

Joachim Nagel, president of Deutsche Bundesbank, advocates for a euro CBDC and stablecoins to...

Must Read

Symbiosis Crypto Bridge: Your Guide to Moving Assets Between Blockchains

What is a Cross-Chain Crypto Bridge?Why Choose Symbiosis for Your Cross-Chain Needs?Support for 50+ BlockchainsAutomatic Routing for the Best RatesNo Need for RegistrationDirect Wallet...
🔥 #AD Get 20% OFF any new 12 month hosting plan from Hostinger. Click here!