Bitcoin (BTC) Core Developers and Community Clash Over OP_RETURN Limits

Bitcoin Core developer Peter Todd has proposed removing arbitrary size limits on OP_RETURN, a move that could have far-reaching implications for the cryptocurrency's ecosystem.

The proposal, which is still pending approval, has sparked heated debate among developers and community members, highlighting deep divisions over Bitcoin's purpose and future.

OP_RETURN, or operation code, is a small data payload that can be embedded in Bitcoin transactions. It is currently limited to 80 bytes, which several use cases have nearly filled to capacity.

The proposal, no. 32359 on GitHub, aims to streamline Bitcoin's codebase by removing the limit, which is easily bypassed by substitution and forks of Bitcoin Core anyway, according to Todd.

"The proposal is to simply remove the arbitrary size limit and instead set a maximum input count for each transaction (which is currently limited to 200, and which would also prevent transactions from becoming too large), and also to add an output size limit (which is currently limited to 80, and which could be set to something like 512 to provide lots of room for new use cases)," explained the developer.

Many community members have expressed concern over the proposal, arguing that it could lead to a shift in focus away from Bitcoin's monetary use cases.

"Sidechain builders shouldn't influence Bitcoin Core. Bitcoin on its base layer is money and should be only focused on money," said Willem S, founder of Botanix Labs.

"It's also setting a bad precedent to change standard rules like this to make development easier, when there are already workarounds in place."

This isn't the first time Bitcoin developers have had to contend with spammers and adjust the limits accordingly. Back in 2014, during the so-called OP_RETURN wars, services like Veriblock began flooding the chain with data, leading to increased transaction fees and a discussion about the role of maximalism in development.

After testing the limits of 40 bytes, leading to a service called BlockChainComplete pouring gigabytes of data into the chain, developers decided to reduce the cap to 40 bytes.

The heated debate unfolding in the community comes as Bitcoin developers are making progress toward a new version of the standard node software.