Bitcoin changes in depth… and the purists cry out for betrayal

A technical decision raises waves in the Bitcoin community. The heart of the protocol is about to change. For a long time, a limit prevented users from storing too much data in transactions. This limit, fixed at 80 bytes, concerned the OP_return field. Created to allow the inclusion of data on the blockchain, it had to remain light and discreet. But this symbolic barrier is now considered useless. And its effects would even be counterproductive. Bitcoin Core developers have therefore decided: the limit will be deleted.

A rule that has become counterproductive at Bitcoin

Op_return allowsIntegrate data into a transaction without creating UTXO. Introduced to avoid polluting scripts, it represented a compromise: limited freedom, but security maintained. There 80 bytes limit aimed at dissuade massive storage of content.

But users quickly bypassed the rule. Some have inserted their data via fake multisig scripts. Others used Factical addressescreating much greater pollution. Even some minors ignored this limit, making its application uneven.

Greg Sanders, Bitcoin Core developer, summed up the problem on GitHub:

Massive data inscriptions take place anyway, often more opaque and more harmful. The limit only redirects them to worse practices for the network.

From then on, there Deletion of this limit appears as a pragmatic choice.

Voices rise against evolution

But This change is not unanimous. For many users, the deletion of this barrier has not been discussed collectively. Marty Bent affirms it on x ::

It is clear that there is no consensus today on the question OP_return.

For his part, Samson Mow calls for caution:

Many find this decision regrettable. They can stay on version 29.0 or use another customer like Bitcoinknots.

THE problem of the problem is there: Who decides changes in Bitcoin? Some denounce a progressive shift towards centralized governance, dominated by some technical teams. There Proposal P 32359yet discussed on Github, would have lacked community consultation.

This disagreement Watch how fragile the protocol governance remains. Users are not all ready to follow the changes imposed, even when they seem logical.

What it really changes

Behind this technical quarrel, concrete implications for the network ::

• The withdrawal of the limit sanitizes the UTXO: fewer stored bogus scripts;
• Transactions will be more consistent between minors and node;
• This improves the estimation of the costs and the transmission of compact blocks;
• The blocks remain limited to 4 million weight units, no explosive drift;
• The rules of consensus do not change: only the relay rules are concerned.

This change is therefore Neither a revolution nor an abandonment of principles. This is a technical realignment with the real network practice. The developers assume a minimalist philosophy: the costs market must decide.

The protections against abuse will always exist. But they will be targeted and adapted to real threats. The project management remains clear: avoid drifts while lightening the protocol.

But the heart of the debate goes beyond the technique. It touches even Bitcoin DNA. Do you still need symbolic rules when uses evolve? Or should community control be strengthened? The deletion of the OP_TREN limit comes as the question of governance returns to the front. Charles Hoskinson, founder of Cardano, had already criticized the absence of a clear structure in Bitcoin. Even today, this decision relaunches the debate: is the Protocol ruled collectively or directed in the undermanship?