比特币核心通过抛弃其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限制和继电器政策的讨论可能会持续存在，尤其是在新用例的出现以及需要与比特币网络的核心原理平衡创新的情况下。