Errata Faith: This article has been updated and the discussion remains open regarding the limitations of Op_return in Bitcoin Core, and there is no definitive decision yet as to whether it will be implemented in the next version of the Bitcoin client.
Blockstream engineer Greg Sanders has created a draft to create arguments to eliminate the 80-byte limit for OP_return transactions on customer Bitcoin cores and allow multiple outputs of this type per transaction. This change is trying to adapt the network to new dynamics and user use, according to a developer known by the pseudonym Instagibbs.
This draft was published in the midst of a fierce debate in which many participants in the Bitcoiner community oppose these changes in core clients, as reported by Cryptootics.
Non-financial transaction restrictions
Bitcoin has a transaction that contains a special type of instruction called op_return. You can embed a small amount of arbitrary data In these networks, without representing unexpended, i.e. transferable funds.
Since its establishment, the 80-byte limit for op_return is Using Bitcoin as a Non-Financial Data Depositprioritizes that feature as a payment system.
However, Sanders argues that the restrictions have lost their relevance. In the GitHub repository, he explained that the restrictions generated “evil incentives” and encouraged users to embed data in “false public keys.” script Spectable taints the UTXO set (an incredible transactional outing) and complicates network consistency.
According to Sanders, eliminating this limitation will bring at least two benefits. More predictable and pre-determined behavior of the cleaner UTXO set and node. Additionally, developers can use OP_Return more flexible to facilitate data integration into their applications without compromising network efficiency.
In addition to Sanders, some of Bitcoin's most recognized collaborators agreed to these changes. Among them are Antoine Poinsotto, Peter Todd, Gloria Zao, Jeremy Rubin, James O'Vine, Michael Falkson and Jameson Ropp.
Currently, Criponoticias has reported an increase in non-financial operations within Bitcoin. This is a behavior that matches the changes in the core client.
Transparency and risk of abuse
The discussion of this change revolves around two distinct locations. On the other hand, defenders argue that lifting the 80-byte limit and allowing multiple op_returns by transactions will promote transparency and simplify Bitcoin data management. This can benefit network-dependent protocols (eg ordinals and runes) to register information.
Meanwhile, critics warned that the decision would open the door to abuse; Promotes spam on your network It will move away from Bitcoin from its original purpose as a financial system.
In the context of Bitcoin, and according to the vision of detractors, spam refers to transactions that have no legitimate financial objectives. They take up space with unnecessary data Or any of the following: messages, images, or information not related to payment.
Opposition of Bitcoin's “purist”
Some of their opponents include Luke Dashul and the team behind the Ocean Mining Pool.
For these opponents, you can eliminate the OP_RETURN limit Aggravate the use of Bitcoin as an optional storage systemThis undermines Nakamoto At, which designed the network as a decentralized financial system. Additionally, Samson Mow, which promotes Bitcoin adoption, also opposed the core update.
According to his position, change Facilitate the increase in non-monatary transactionscongestion of networks and increases fees for users who prioritize payments. These issues have already happened in the past, especially during 2023, with the use booming, with the commission rising to $30 or $40 on average trading.
Delicate balance and customer transition knot
Bitcoin Core's decision reflects the constant challenges of balance innovation and fidelity to the fundamental principles of networks.
While this update defends a step towards a more versatile network, critics fear that Bitcoin will lose its essence as a system focused on economic freedom.
Ultimately, it is also important to emphasize that in this context the number of nodes with Bitcoin knots is increasing at the expense of a slight reduction in their behavioral centers.
The core is still a big difference Most second-hand customer with around 20,000 nodes (22,000 total cases at the time of this language), or 95% of the network, Knots already have 1,060 operational nodes. This corresponds to almost 5% of the total, according to Cindance data. On April 30, when Cryptootics noted an increase in knot nodes, these operators were 840, resulting in an additional 220 people taking part in the seven days.
According to Cryptonotics, a possible explanation for the movement is that Minero's view of Pool Ocean is that “the participation of knots is increasing and increasing the power of the hash of the ocean and datum, making it undoubtedly difficult to undermine blocks full of data.” This suggests it pools like the ocean Due to low data, prioritize transactionsThey may be advertising the knot, and their composition is complicated, including heavy blocks.
Additionally, others provided technical visions. The nodes reject what they don't want to spread. Miners only provide services. The network depends on the complete node». This comment highlights that nodes are enhanced by enhancing user autonomy by verifying transactions and enhancing consensus, allowing the nodes to do not require data.
