🎉 The #CandyDrop Futures Challenge is live — join now to share a 6 BTC prize pool!
📢 Post your futures trading experience on Gate Square with the event hashtag — $25 × 20 rewards are waiting!
🎁 $500 in futures trial vouchers up for grabs — 20 standout posts will win!
📅 Event Period: August 1, 2025, 15:00 – August 15, 2025, 19:00 (UTC+8)
👉 Event Link: https://www.gate.com/candy-drop/detail/BTC-98
Dare to trade. Dare to win.
Bitcoin core developers propose to lift OP_RETURN limitations, sparking community controversy.
Bitcoin core developers propose to lift OP_RETURN data limit, sparking controversy
Recently, a member of the Bitcoin core development team proposed a plan to remove the OP_RETURN data limit, sparking extensive discussions within the community. OP_RETURN is an opcode in Bitcoin scripts that allows embedding a small amount of data in transactions. Currently, the Bitcoin core client defaults to limiting the size of OP_RETURN data to 80 bytes and restricts the propagation of related transactions exceeding 83 bytes through node policies.
This proposal suggests removing the above restrictions while also eliminating the related configuration options. Supporters argue that the current restrictions do not effectively prevent users from storing large amounts of data, as there are various ways to circumvent these limitations. They also point out that lifting the restrictions may be more compatible with miner incentives, as miners can earn more revenue by competing for block space.
However, opponents are concerned that removing restrictions could lead to more non-transaction data being written to the blockchain, thereby occupying valuable block space and driving up transaction fees. Although existing restrictions can be circumvented, they believe that node strategies still have their role, such as limiting the dissemination of certain data and reducing pressure on the network.
An investment research director stated that he tends to oppose lifting restrictions. He believes that although there were no such restrictions during the Satoshi era, it does not mean that the current restrictions are unreasonable. He emphasized that the role of the Bitcoin core client needs to be re-examined to find a balance between security patches, node strategies, and consensus rules.
Another industry expert supports lifting the restrictions, believing it aligns with the original design philosophy of Bitcoin. He points out that the current limitations are essentially nominal and can be easily circumvented in various ways. He also believes that lifting the restrictions could help reduce the burden on the network from certain protocols (such as inscriptions) and provide additional income for miners.
The attitude towards miners is currently unclear. On one hand, increased competition for block space may boost their income; on the other hand, some mining pools may not favor this change as it could reduce their advantage in handling non-standard transactions.
This controversy highlights the challenges faced by the Bitcoin community in terms of technological development and network management. Regardless of the final decision, users still have the choice to run stricter clients or retain older versions to align with their personal needs and philosophies.