The new version of Bitcoin software will raise the OP_RETURN DATA CAP as the debate ends
Bitcoin core developers, the main open-source software for connecting the blockchain behind the world’s largest cryptocurrency, said version of October 30 will increase the default limit For OP_RETURN data Transactions from current 80 bytes to about 4MB, a limit imposed by the size of the Bitcoin block.
The proposal for change, which confirmed to an update on GitHubhas caused a debate within the Bitcoin community. Critics argue that removal of the limit may encourage increasing increasing unjust data, which potentially leads to network spam and a transition from bitcoin
Main operating as a financial tool.
This decision to proceed marks another significant moment in the community debate about the use of blockchain, which features ongoing tightening between network efficiency, practical cases of use and ideological principles.
The OP_RETURN code allows Bitcoin users to include data in transactions. The function is similar to, though technically different from, the way Inscriptions I -Embed images and texts directly with the use of blockchain Ordinary and witness data.
Some argue that the addition of data of this transaction is “unreasonable” and opposed the original vision for the Bitcoin blockchain as Satoshi Nakamoto suggested.
The 80-byte limit on OP_RETURN has encouraged alternative data storage techniques, some of which have caused issues such as unspen transaction output (UTXO) bleeding.
In a detailed summary of GitHub And next X post, Bitcoin core developer Gloria Zhao outlined the reasoning behind the change.
Zhao emphasized the intent to ease the accidental consequences of the existing limit, to note, “the main motivation for (change) is to correct a mistake between the damage and the standard of data storing techniques.”
Development Greg Sanders, who wrote the Merged Pull Request, said in the GitHub discussions that removal of the limit “produces at least two tangible benefits: a cleaner set of UTXO and more and more default behavior.”
Debate about management
Zhao Also addressed greater management issues with his x pageThe highlight of the Bitcoin Core promise in transparency and meritocracy.
He emphasized the importance of the role of the community in maintaining these principles, warning against the dangers of social engineering or corporate pressure that influence the software decision making process.
“If those who contribute to the Bitcoin Core leave these values, for example, to comfort social media or corporate preferences, the community will move to another node implementation that is better,” Zhao wrote, urging users to remain vigilant and knowledgeable.
Developer Luke Dashjr continues to oppose the limits, labeled the transition as potentially harmful. He encouraged users to avoid upgrading the new version or to adopt alternative node implementation, such as bitcoin knots.
Debate reflects the controversies of 2023.
Despite these concerns, Zhao has maintained that attempts tocensor transactions through relay policy are impractical and ineffective against strong economic incentives. The Bitcoin core approach should remain neutral, reflecting the foundational principles of the censorship resistance network and decentralization, he said.
The main release of 30 will maintain manual control options, allowing users to implement tighter limits through existing command-line parameters. However, these options are now marked as deleted and prompting warning messages, indicating potential removal of future updates without a set timeline.
