比特幣核心通過拋棄其80字節OP_Return限制來激發激烈的辯論

比特幣核心正在再次搖動一切，通過拋棄其長期存在的80字節OP_Return限制，引發了激烈的辯論。

Bitcoin Core is shaking things up again, sparking intense debate by ditching its longstanding 80-byte OP_RETURN limit.

比特幣核心正在再次搖動一切，通過拋棄其長期存在的80字節OP_Return限制，引發了激烈的辯論。

The upcoming update will effectively kill the old ceiling, a move framed by the Bitcoin Core developers as aligning the relay policy closer to real-world mining practices, but not everyone is thrilled.

即將到來的更新將有效地殺死舊的天花板，這一舉動由比特幣核心開發人員構成的舉動將接力賽政策與現實世界採礦實踐更接近，但並不是每個人都很興奮。

The change was announced by developer Greg Sanders on GitHub, stating that it will allow transactions with OP_RETURN outputs exceeding 80 bytes as well as multiple such outputs per transaction. In plain terms: more data, fewer artificial restrictions, and a relay policy that finally mirrors on-chain reality.

開發人員Greg Sanders在GitHub上宣布了這一更改，並指出它將允許使用OP_RETERN輸出超過80字節的交易以及每筆交易的多個此類輸出。簡單地說：更多數據，人工限制的較少以及最終反映鏈現實的繼電器政策。

Before we get into the details, let’s have a quick rundown on what this all means.

在詳細了解之前，讓我們快速介紹一下這一切的含義。

OP_RETURN or OP_CAT?

op_return或op_cat？

OP_RETURN and OP_CAT are two Bitcoin script commands—one embedded, one exiled—that define the boundary between Bitcoin’s past limitations and its potential future.

OP_RETURN和OP_CAT是兩個比特幣腳本命令 - 一個嵌入式，一個被放逐 - 它定義了比特幣過去局限性與其潛在未來之間的邊界。

Originally introduced as a way to embed small, unspendable pieces of data into the blockchain, OP_RETURN allows up to 80 bytes of user-defined data per transaction. The catch is that it burns the Bitcoin sent with it. That output is forever unspendable, a calculated tradeoff for preventing UTXO bloat.

OP_RETURN最初是作為將小的，無用的數據嵌入區塊鏈中的一種方式，可允許每筆交易最多80個字節的用戶定義數據。捕獲是，它燃燒了用它發送的比特幣。該輸出永遠是不可承擔的，這是預防UTXO膨脹的計算折衷。

Its use cases are narrow but persistent. It’s useful for things like proving a document existed at a certain time, creating basic tokens, or adding notes. And because it’s clearly unspendable, it doesn’t make the system slower or more complicated. But Bitcoin only lets one OP_RETURN note per transaction under normal conditions—so you can’t abuse it to spam the network.

它的用例狹窄但持久。這對於諸如證明在一定時間存在文檔，創建基本令牌或添加註釋的事情很有用。而且由於它顯然是不可投射的，因此不會使系統較慢或更複雜。但是，比特幣僅在正常情況下讓每個交易中的一個op_return註釋 - 因此您不能濫用它來垃圾郵件。

OP_CAT, on the other hand, is the opcode that never really was. OP_CAT is a Bitcoin opcode that was disabled in 2010 because it could potentially crash nodes. All it does is combine two pieces of data from the stack into one. Sounds basic, right? But it’s actually very powerful.

另一方面，OP_CAT是從未真正真正如此的OPCODE。 OP_CAT是一個比特幣OpCode，在2010年被禁用，因為它可能會崩潰節點。它所做的就是將兩個數據從堆棧組合到一個數據中。聽起來很基本，對嗎？但這實際上非常強大。

If reactivated, OP_CAT would allow Bitcoin to support much more advanced smart contracts, opening the door to an entirely new class of smart contracts on the network —more composable, flexible, and modular. Think covenants, advanced multi-sigs, zero-knowledge proofs (ZKPs), or even decentralised bridges, etc.

如果重新激活，OP_CAT將允許比特幣支持更高級的智能合約，為網絡上一類全新的智能合約打開了大門 - 更加合成，靈活和模塊化。想想盟約，高級多人，零知識證明（ZKP），甚至是分散的橋樑等。

The move sparked criticism from those who prefer Bitcoin's minimalist design and pointed out the lack of consensus on the proposal.

此舉引發了那些喜歡比特幣的極簡主義設計的人的批評，並指出了對該提案的共識。

Luke Dashjr, leading the alternative Bitcoin Knots client with around 5% network presence, slammed the move as “utter insanity”, asserting it betrays Bitcoin’s minimalist principles.

盧克·達什（Luke Dashjr）以大約5％的網絡存在為領導替代性比特幣結客戶端，將其抨擊為“完全瘋狂”，並斷言它背叛了比特幣的極簡主義原則。

Samson Mow called it an “undesirable change” on X, but stated there might be pragmatic reasons for it, adding that users can simply stick to version 29.0 or switch to alternative clients if they reject the new policy.

Samson Mow稱其為X上的“不良更改”，但表示可能存在務實的原因，並補充說，如果用戶拒絕新策略，則可以簡單地堅持使用29.0版或切換到替代客戶端。

“There is no consensus at the moment on this OP_RETURN issue,” said Marty Bent, managing partner at Ten31 Fund.

TEN31 Fund的執行合夥人Marty Bent說：“目前在這個OP_RETURN問題上尚無共識。”

The change will also remove the 80-byte limit on OP_RETURN outputs, allowing for larger payloads of up to 520 bytes.

該更改還將刪除OP_RETURN輸出的80字節限制，從而允許更大的有效載荷約為520字節。

The proposal to modify the OP_RETURN relay policy and introduce support for multiple OP_RETURN outputs was originally raised in December 2023 and has since garnered attention and feedback from various community members.

修改OP_Return繼電器政策並為多個OP_Return輸出提供支持的建議最初是在2023年12月提高的，此後引起了各種社區成員的關注和反饋。

Those in favor of the change highlight the technical aspects and the alignment with the behavior of the majority of miners. They also emphasize the importance of adapting to new use cases and keeping pace with technological advancements.

贊成這一變化的人強調了技術方面以及與大多數礦工的行為的一致性。他們還強調了適應新用例並跟上技術進步的重要性。

However, critics express concern over deviating from the original Bitcoin design philosophy and the potential impact on smaller clients and full nodes. They argue that the changeover should have involved a broader consensus and a more structured proposal process.

但是，評論家對偏離原始比特幣設計理念以及對較小客戶和完整節點的潛在影響表示關注。他們認為，轉換應該涉及更廣泛的共識和更結構化的建議過程。

As the Bitcoin ecosystem continues to evolve, the discussion around OP_RETURN limits and relay policies is likely to persist, especially with the emergence of new use cases and the need to balance innovation with the core principles of the Bitcoin network.

隨著比特幣生態系統的繼續發展，圍繞OP_Return限制和繼電器政策的討論可能會持續存在，尤其是在新用例的出現以及需要與比特幣網絡的核心原理平衡創新的情況下。