The Bitcoin network splits on BIP-110: Strong support for OP_RETURN limitation

The debate around Bitcoin Improvement Proposal 110 (BIP-110) reflects a deep rift within the community, with approximately 2.38% of Bitcoin nodes already supporting it. According to October 2025 data, 583 out of 24,481 active nodes have already implemented this measure, with Bitcoin Knots being the main software supporting it. This modest support illustrates the broader skepticism among node operators.

Why Bitcoin Core 30 Led to a Major Change

Tensions escalated with the release of Bitcoin Core version 30, which completely removed the OP_RETURN size limit of 83 bytes, a restriction that had existed for years. The change, initially proposed in April 2025 through a controversial pull request, was finalized in October 2025 and received mixed reactions. The OP_RETURN script code allows users to embed arbitrary data into blockchain transactions, a functionality that has increasingly raised concerns within the community.

Objectives of BIP-110: Curbing Arbitrary Data

BIP-110 proposes a partial rollback, aiming to limit transaction output sizes to 34 bytes and reintroduce an 83-byte limit for OP_RETURN data. This is designed as a temporary measure, initially set for a period of one year, with the possibility of extension or modification in the future, according to details available on GitHub. The intention is to balance functionality with responsibility.

Controversy Driven by Spam Concerns

The main concern leading to this proposal is the increasing potential for spam on the Bitcoin ledger. Critics highlight that unlimited arbitrary data can significantly increase storage costs for node operators, threatening the network’s decentralized nature. Unlike other high-capacity blockchains that require specialized equipment, Bitcoin nodes have always been accessible on ordinary household computers. However, increasing hardware requirements could fundamentally undermine Bitcoin’s value proposition as a decentralized currency.

Divided Opinions in the Community

Bitcoin supporter Matthew Kratter expressed this concern, comparing spam to a parasitic plant that overwhelms a tree, suggesting it could similarly compromise the core structure of the network. On the other hand, Jameson Lopp, a senior contributor to Bitcoin Core, argues that OP_RETURN limits are ineffective in preventing spam and that node-level filters are a more appropriate approach. This debate reflects a fundamental tension: how to maintain network integrity without restricting innovation or functionality.

Support for BIP-110 remains limited to 2.38% of nodes, suggesting that the majority of the network has not yet adopted this stance, leaving the future of this proposal uncertain in the face of the Bitcoin community.