The Network Divides: Bitcoin Nodes Adopt BIP-110 Amid Controversy over OP_RETURN

The Bitcoin community faces a new breaking point. Amid an intense debate over data limits on the network, a growing number of nodes have begun to signal their support for Bitcoin Improvement Proposal 110 (BIP-110), reflecting the ideological fractures running through the ecosystem.

The Network Pulse: Percentage of Nodes Supporting the Proposal

So far, 583 nodes out of a total of 24,481 are running BIP-110, representing 2.38% of the network. According to Cointelegraph reports, Bitcoin Knots has become the main software implementation running this temporary soft fork. The figure, although modest, illustrates the dynamism of a network that allows its participants to express technical preferences in a distributed manner. This support, while minor in absolute numbers, marks the beginning of a possible transition.

Unlimited OP_RETURN: Spam or Freedom in Bitcoin?

The core of the conflict lies in a specific technical element: the OP_RETURN code. This operation allows users to embed arbitrary data within Bitcoin transactions, a capacity that for years was limited to 83 bytes. BIP-110 seeks precisely to set that cap again, in addition to restricting transaction output sizes to 34 bytes.

The turning point arrived with Bitcoin Core version 30, recently released in the update cycle. That version removed the OP_RETURN data limit, a controversial decision initially proposed months ago, but which faced massive resistance within the community. The controversy intensified when the update went live, triggering warnings about the consequences of this permissiveness.

Decentralization at Risk: Concerns About Hardware

Critics warn of an existential risk to Bitcoin: the increase in arbitrary data significantly raises storage costs for those running nodes. Unlike high-performance blockchains requiring specialized machines, Bitcoin has historically allowed conventional computers to run nodes. If hardware requirements multiply, participation would concentrate among actors with greater investment capacity, eroding Bitcoin’s central promise as a decentralized monetary network.

Matthew Kratter, a network advocate, used a disturbing metaphor: he compared data spam to a parasitic plant choking a tree. The image captures the concern that digital noise could corrupt the very structure of the network.

Two Visions of the Future: Crypto Defenders vs. Collaborators

Not everyone shares this catastrophic view. Jameson Lopp, an experienced Bitcoin Core collaborator, defends removing the limit, arguing that filters are never effective against spam. For him, data freedom is preferable to technical restrictions.

This divide reflects a fundamental tension in Bitcoin: prioritize decentralized accessibility or allow maximum technical flexibility? The gradual adoption of nodes running BIP-110 will indicate where the network participants truly lean.

The temporary measure is scheduled to last one year, allowing for an assessment of its real impact before making permanent decisions. Meanwhile, the percentage of nodes supporting the proposal will continue to be a crucial thermometer of community sentiment in this fundamental debate.