The Bitcoin community has a heated discussion on OP_RETURN data limits

Recently, the Bitcoin community has engaged in heated discussions about the proposal to remove the OP_RETURN data limit. This proposal was put forward by Bitcoin Core developers and aims to eliminate the current default limit of 80 bytes, sparking differing opinions among supporters and opponents.

Background

OP_RETURN is an opcode in Bitcoin scripts that allows embedding a small amount of data in a transaction. Currently, Bitcoin Core defaults to limiting the size of OP_RETURN data to 80 bytes and restricts the propagation of related transactions exceeding 83 bytes through node policy.

Controversy Focus

Supporters argue that the current restrictions have become ineffective, as users can bypass them in various ways. They advocate for removing the restrictions, which may better align with the miners' incentive system, allowing miners to earn more income by competing for block space.

Opponents are concerned that lifting restrictions could lead to more non-transactional data being written to the blockchain, occupying precious block space and driving up transaction fees. Although the restrictions can be circumvented, they believe that node policies still play a role, such as limiting the spread of junk data.

Highlights of Opinions

A blockchain researcher supports lifting restrictions, believing it aligns with Bitcoin's original design, could help reduce network burden, support ecological development, increase miner income, and better adhere to liberal ideals.

Another investment research director tends to disagree, worrying that non-trading data may occupy block space. He emphasizes the importance of preserving users' freedom of choice and criticizes the practice of removing configuration options as potentially limiting users' rights.

There are also views that instead of letting users bypass restrictions, it is better to open up directly. Some voices point out that projects that treat Bitcoin merely as a data availability layer may not be very meaningful.

Consensus Rules and Node Strategies

It is important to understand the distinction between the consensus rules involved in OP_RETURN and the node policies. The basic functionality of OP_RETURN belongs to the consensus rules, while the limitation on data size falls under node policies. Nodes can make their own choices in terms of transaction propagation and data processing.

Potential Impact

Removing restrictions may increase miners' income and support certain Bitcoin ecosystem projects, but it could also crowd out ordinary users' block space. Miners' attitudes towards this are still unclear, as it may affect their income structure and service advantages.

Suggestions

If the proposal passes but users do not agree, they can choose to run a stricter client or retain the old version. This discussion also prompts the community to rethink the role of Bitcoin Core and how to balance security, strategy, and consensus rules.