The development team behind Bitcoin Core, the open-source software driving the world's largest cryptocurrency's blockchain, has announced that the default limit for OP_RETURN data transactions will be increased from 80 bytes to nearly 4MB in the October version 30 release. This change, confirmed through a GitHub update, follows a period of debate within the Bitcoin community. Critics have raised concerns that lifting the limit could lead to increased embedding of arbitrary data, potentially causing network spam and shifting the focus of bitcoin away from its primary function as a financial tool. The decision marks a significant moment in the ongoing debate about blockchain usage, highlighting the tension between network efficiency, practical applications, and ideological principles.
The OP_RETURN function allows users to include data in transactions, similar to but distinct from the method used by Inscriptions to embed images and text directly into the blockchain using Ordinals and witness data. Some argue that adding transaction data in this way contradicts the original vision for the Bitcoin blockchain as proposed by Satoshi Nakamoto.
The existing 80-byte limit on OP_RETURN has encouraged alternative data storage methods, some of which have caused issues like bloating the unspent transaction output (UTXO) set. Bitcoin Core developer Gloria Zhao outlined the reasoning behind the change in a detailed GitHub summary and subsequent post, emphasizing the intention to mitigate unintended consequences of the existing limit. Zhao noted that the primary motivation for this change is to address the mismatch between the harmfulness and standardness of data storage techniques. Developer Greg Sanders, who authored the merged pull request, highlighted that removing the limit yields at least two tangible benefits: a cleaner UTXO set and more consistent default behavior.
The debate also touches on broader governance issues, with Zhao stressing the importance of transparency and meritocracy in Bitcoin Core's decision-making process. She warned against the risks of social engineering or corporate pressure influencing the developers, emphasizing the community's role in maintaining these principles. If Bitcoin Core's contributors abandon these values, the community will switch to another node implementation, Zhao urged, encouraging users to remain vigilant and informed. The debate has been contentious, with developer Luke Dashjr opposing the easing of limits, labeling the move as potentially harmful and encouraging users to avoid upgrading or to adopt alternative node implementations.
The controversy mirrors concerns from 2023 surrounding Ordinals and Inscriptions, when substantial non-financial data was embedded into Bitcoin transactions, prompting concerns about blockchain misuse and network congestion. Despite these concerns, Zhao maintained that attempts to censor transaction types are impractical and ineffective against strong economic incentives, emphasizing the need for Bitcoin Core's approach to remain neutral and reflect the network's principles of censorship resistance and decentralization.
The Core 30 release will retain manual control options, allowing users to enforce stricter limits, but these options are now marked as deprecated and will trigger warning messages, indicating potential removal in future updates.