Bitcoin Core Developer Peter Todd suggested lifting the imposed size restrictions on OP_RETURN. However, some developers disagree with his proposal, arguing it could destroy Bitcoin’s future and that of its investors.
One of the proposal’s opponents is Jason Hughes, Vice President of Development and Engineering at Ocean Mining, who believes the suggested adjustments could compromise Bitcoin’s value proposition. He commented, “Bitcoin Core developers are about to merge a change that turns Bitcoin into a worthless altcoin, and no one seems to care to do anything about it. I’ve voiced objections, lost sleep over this, and despite clear community rejection of the PR, it’s moving.”
Todd claims developers have been bypassing the data size restrictions
Todd proposed removing the size limit of data stored with OP_RETURN on GitHub. The current limit on data is just 80 bytes, but Todd said that removing that limitation would streamline Bitcoin’s codebase. He also said it could enhance efficiency without sacrificing network security and offer support for sidechains and cross-chain bridges.
Moreover, he believes the limit is largely ineffective, as developers can easily bypass it by directly modifying the code or using a forked version of Bitcoin Core.
Nevertheless, many in the BTC community still oppose his proposal, saying it’s foolish and a potential slippery slope to the 2014 OP_RETURN Wars. At the time, fear of spam forced the developers to cut the data limit in half from 80 to 40 bytes, causing greater block sizes and fees for transactions. From then on, developers were forced to drop the data cap back down to 80 bytes.
Willem Schroe sees no need to change the data size restrictions at the moment
On the proposal, Willem Schroe, founder of Botanix Labs, argued that increasing the OP_RETURN sizes can be done, but he does not see the point in changing the standard rules to make that process easier. He stated that everyday users don’t necessarily need data limit changes, especially when workarounds already exist.
He argued that if an increasing majority used different transaction rails, the situation would be completely different, but that is not the case.
Moreover, he claimed that sidechain builders should not influence Bitcoin Core’s decision, saying that the BTC’s foundation is centered on money. Thus, decisions concerning the asset should be focused on money first and all other functionalities developed around it.
Supporters say the proposal could boost Bitcoin’s efficiency without sacrificing its core identity
Some Bitcoin community members view the proposal more positively as a potential improvement for the network.
For example, a well-known X user, Karbon, has argued that the data cap changes could lead to more transactions being pushed through sidechains and bridges, which, in turn, would have a net benefit for the network.
Some have attempted to compare the current situation to Ethereum’s perennial woes. One X user made the point that BTC should not be an L2-centric plan like Ethereum – that is what killed Ethereum, he says. Like Willem, he says it’s money, and we should keep calling it that.
