Bitcoin Core Devs Commit to Changing OP_RETURN Data Storage Limit By October

Bitcoin Core developers have Confirmed plans Removal of long -standing data storage restrictions in the upcoming edition of version 30, scheduled for October 30th.

The change in the basis of eliminates the current limit of 80-Bajt-Bajt Bitcoin on the outlets of OP_return, which are special transactions fields that allow users to install arbitrary data on blockchain. According to the new rule, transactions may include more general output, each potentially contains up to 4MB data.

“Bitcoin Core is just one implementation of the protocol that anyone can copy and change; the only thing he does is the special way of his associates make a decision,” explained Gloria Zhao, a core of contributions approved, explained in Github note and twitter.

Modification is a significant change in policy that deals as Bitcoin The handles by non -financial data.

Op_return exits, popularized during 2024 Ordinary registration Boom, allows users to store information such as images, texts or metadats directly on Bitcoin’s blockchain without creating outputs that can be consumed that break the UTXO network (unpent transaction output) database.

It is worth noting that, although users can still manually renovate the old border of 80 bytes if they prefer, these configuration options will eventually be completely removed in the future Bitcoin Core versions.

Discussion on Op_return

Confirmation is followed by months heated discussion Among the Bitcoiners, with fans who view this as a means of improving bitcoin to a programming platform that can support wider cases of use, while critics such as the long -standing contribution of Bitcoin core Jason Hughes discuss that the change changes “the nature of what Bitcoin’s network itself is in full.”

For Zhao, however, the “primary motivation” behind the decision to implement the OP_return was to resolve people who store information about bitcoin by harmful methods that permanently break the memory of the network – which could be the “long -term network cost”, Zhao claimed.

When the rules of Bitcoin Core were stricter than what the miners “reliably mined” and accepted, the big players began to bypass the public transactions pool and directly deal with miners. This “creating centralization” and undermines Bitcoin’s design, hurting his censorship resistance, Zhao explained.

By removing the limit of op_return, the bitcoin nucleus aligns its policies with reality MiningEncouraging people to use a clean data storage method instead of forcing them to harm to harmful techniques or centralized bypasses.

But Zhao was welcomed by the Bitcoin Core programmers to welcomed the Bitcoin section in return.

“There was no clear consensus about that, so it should never have been connected!” Juan David Diaz, software engineer, commented on threads.

“This is a shameful precedent. There is no consensus for this change,” another commentator who uses pseudonym through the newly reached Github account wrote.

People obviously don’t understand “that it is according to default settings“Engineer who claims to work in ZK-OB-OPPORTED BITCOIN INFRASTRATURE COMPANY ALPEN LABS noticed.

“You can still set your own limits in configuration. If you do not agree, you can easily change it on your nodes,” the pseudonym engineer claimed.