Bitcoin Core DEVS commit to change the limit of the Op_Rreturn data storage by October

Bitcoin core developers have confirmed plans to delete long-term data storage restrictions in the coming version 30-release, planned for October 30.

The change essentially eliminates the current limit of 80 bytes from Bitcoin on on_return outputs, which are special transaction fields with which users can embed random data about the blockchain. According to the new rule, transactions can contain multiple on_return outputs, each of which contains up to 4 MB of data.

“Bitcoin Core is only one protocol implementation that can be copied and changed by someone; the only thing that makes it special is the way in which the contributors make decisions,” Gloria Zhao, core contribution to the approved changes, explained in a github note and tweet.

The adjustment is an important policy shift that tackles how Bitcoin processes non-financial data.

On_Rreturn, popular during the 2024 inscription tree, users enable users to store information such as images, text or metadata directly on Bitcoin’s blockchain without making the UTXO database of the network (unspoken transaction output) storing the UTXO database.

It is worth noting that although users can still restore the old 80 bytes limit manually if they prefer, these configuration options are ultimately completely removed in future Bitcoin core versions.

The debate on the debate

The confirmation follows months of a heated debate among Bitcoiners, where supporters consider it a means to improve Bitcoin in a programmable platform that can support wider use cases, while critics such as long -term Bitcoin -core bidding bearer Jason Hughes himself claims “The nature” The nature “The nature” The nature “the change” the change “the change” the change “the change” the change “the change of change”

For Zhao, however, the “primary motivation” behind the decision to implement on_return was to address people who store data on Bitcoin with harmful methods that permanently inflate the memory of the network – which could “represent a long -term costs for the network,” Zhao claimed.

When the rules of Bitcoin Core were stricter than what miners “reliable mined” and accepted, large players began to bypass the public transaction pool and deal with miners directly. This “creates centralization pressure” and undermines Bitcoin’s design and damages its censorship resistance, Zhao explained.

By removing the limits from Op_Rreturn, Bitcoin Core concludes his policy with the realities of Bitcoin -MIERBUITEncourage people to use the cleaner method for data storage instead of force them to harmful techniques or centralized solutions.

But Zhao’s attempt to pass on the ideas and motivations of the Bitcoin core developers for the change was received with a recoil from some sections of the Bitcoin community.

“There was no clear consensus about this and therefore should never have been merged!” Juan David Diaz, a software engineer, commented on the thread.

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

People apparently do not understand ‘that this is standard“An engineer who claims to work at ZK-compatible Bitcoin infrastructure developer Alpen Labs noted.

“You can still simply set your own limits in your configuration. If you do not agree, you can simply change them at your nodes,” the pseudonyms claimed.