比特币核心对op_return限制的删除sparks敏锐的部门

即将发布

Plans by Bitcoin Core to remove the long-standing OP_RETURN limit have sparked sharp division across the ecosystem.

比特币核心的计划消除了长期的OP_Return限制，使整个生态系统都引发了敏锐的划分。

The upcoming release will, by default, lift the 80-byte ceiling that previously restricted transaction-embedded data, presenting the change as a modernization of policy in response to shifting network practices.

默认情况下，即将发布的版本将取消以前限制交易包含数据的80字节天花板，将这一变化表示为政策的现代化，以响应转移网络实践。

Originally introduced as a soft deterrent, OP_RETURN allowed users to embed small, provably unspendable data without bloating the unspent transaction output (UTXO) set. The limit aimed to prevent abuse while enabling legitimate use cases such as timestamping or cryptographic commitments.

OP_RETURN最初以软威慑作用引入，允许用户嵌入小的，可证明的不可投射的数据，而无需膨胀未固定交易输出（UTXO）集。该极限旨在防止滥用，同时实现合法用例，例如时间戳或加密承诺。

However, the cap has increasingly proved ineffective. Developers, including Greg “instagibbs” Sanders, argued that the existing ceiling merely shifted these activities into more opaque alternatives that undermined network health.

但是，盖子越来越多地证明是无效的。包括Greg“ Instagibbs” Sanders在内的开发人员认为，现有的天花板仅将这些活动转变为破坏网络健康的更不透明的替代方案。

In a public statement, Sanders noted that “large-data inscriptions are happening regardless.”

桑德斯在一份公开声明中指出：“无论如何，大数据铭文正在发生。”

"We're rendering these inscriptions unreadable by refusing to process transactions with unsupportable script types or cooperating with attempts to disable dust limits. We're also making it harder for miners to accept unserializable transactions or transactions that violate node policy in other ways."

“我们正在通过拒绝使用无法支持的脚本类型处理交易或与试图禁用灰尘限制的尝试进行交易，从而使这些铭文变得不可读。我们也使矿工更难接受无效的交易或以其他方式违反节点策略的交易或交易。”

Pointing out that "persistent actors will continue to attempt to circumvent these measures," rendering the inscriptions readable seems like a natural progression.

指出“持久的演员将继续尝试避免这些措施”，使铭文可读似乎是自然的进步。

"Inscriptions are a fact of life. Let's move them out of script and into the open, simplify relay and fee estimation, and collect these outputs into a single, provably unspendable structure."

“铭文是生活的事实。让我们将它们从脚本中移出，简化继电器和收费估算，并将这些输出收集到一个单一的，可证明的无人负担的结构中。”

Aligning behavior with miners

与矿工保持一致

The move also saw the deprecation of the “-datacarriersize” parameter in pull request #32406.

此举还看到了“ - dataCarriersize”参数的弃用＃32406。

These changes align Core's behavior more closely with how miners and other node implementations already operate. Unlike consensus rules, which govern what can be included in blocks, standardness rules such as the OP_RETURN cap primarily dictate how transactions are relayed across the peer-to-peer network.

这些更改与矿工和其他节点实现的运作方式更加紧密地融合了Core的行为。与共识规则不同，该规则可以控制块中可以包含的内容，诸如OP_RETURN CAP之类的标准性规则主要决定了在点对点网络中如何中继交易。

As such, removing the ceiling does not force a change in what miners can include in blocks but recalibrates policy to match the real-world conditions that miners and other nodes already factor into their behavior.

因此，卸下天花板不会迫使矿工可以在区块中包含的东西变化，而是重新校准了策略以匹配矿工和其他节点已经将其行为融入其行为的现实情况。

However, criticism of the move has been voiced by prominent figures who view the decision as deviating from Bitcoin's minimalist ethos.

但是，对这一举动的批评是由著名人物表达的，他们认为该决定偏离了比特币的极简主义精神。

Luke Dashjr, maintainer of Bitcoin Knots—an increasingly popular alternative client with almost 5% of nodes—described the removal as "utter insanity."

比特币结的维护者卢克·达什（Luke Dashjr）是一个越来越受欢迎的替代客户，几乎有5％的节点，将其描述为“完全疯狂”。

Samson Mow, CEO of Jan3 and an outspoken Bitcoin advocate, suggested that operators who wish to reject the change can do so by running Knots or staying on older versions of Bitcoin Core.

JAN3首席执行官和直言不讳的比特币拥护者Samson Mow建议，希望拒绝更改的运营商可以通过打结或保持较旧版本的比特币核心来做到这一点。

According to Mow, maintaining stricter relay policies is crucial to preserve Bitcoin's role as a global, censorship-resistant monetary network.

根据MOW的说法，维持更严格的继电器政策对于保留比特币作为全球，持审查的货币网络的作用至关重要。

Nevertheless, Mow pragmatically recognized that the removal of the limit has its advantages.

然而，MOW务实地认识到，去除极限具有其优势。

"Delete the cap. Aligns default policy with actual network practice, minimises incentives for harmful workarounds, and simplifies the relay path.

“删除上限。将默认策略与实际网络实践保持一致，最大程度地减少对有害解决方法的激励措施，并简化继电器路径。

Option 3 earned broad, though not perhaps unanimous, support. Dissenting parties remain free to modify software, run stricter policy, or propose new resource limits if empirical harm emerges."

选项3赢得了广泛的支持，尽管不是一致的支持。如果经验危害出现，则无权政党可以自由修改软件，运行更严格的政策或提出新的资源限制。”

Those in favor of removing the limit highlight the fact that with blocks still subject to four million weight units, dust limits, and other constraints, fears of unchecked data spam are overstated.

那些赞成消除限制的人强调了一个事实，即由于块仍然受到400万个重量单位，尘埃限制和其他限制的限制，对未经检查的数据垃圾邮件的担忧被夸大了。

They argue that removing arbitrary barriers makes relay and fee estimation more predictable and encourages cleaner data use by consolidating inscriptions into provably unspendable OP_RETURN outputs rather than misusing spendable script paths.

他们认为，消除任意障碍会使继电器和费用估计更可预测，并通过将铭文合并到可证明的无用的OP_Return输出中，而不是滥用可支付的脚本路径，从而鼓励更清洁的数据使用。

A broader shift in programmability

可编程性的更大转变

The timing of the OP_RETURN policy shift coincides with growing momentum for more ambitious protocol upgrades.

OP_Return政策转变的时机与增长的动力相吻合，以进行更雄心勃勃的协议升级。

Once a memetically disabled opcode assigned to OP_SUCCESS126 in BIP-347, OP_CAT has advanced to become a subject of serious discussion and proposal among developers and industry researchers.

一旦在BIP-347中分配给OP_SUCCESS126的模因残障的OPCODE后，OP_CAT已提出，成为开发人员和行业研究人员中认真讨论和建议的主题。

Galaxy Digital's research team positioned both OP_CAT and OP_CTV as straightforward enhancements that could be coded in a few days and boasted major implications for DeFi applications.

Galaxy Digital的研究团队将OP_CAT和OP_CTV都定位为直接的增强功能，可以在几天内编码，并对DEFI应用程序具有重大影响。

"Unassigned opcodes and opcode variants can be used to introduce new capabilities to the VM. This is done by modifying the node software to recognise and process transactions that use these codes in a defined way. Once an opcode is assigned, it can be used in transactions to perform a specific operation or function.

“未分配的OPCODES和OPCODE变体可用于将新功能引入VM。这是通过修改节点软件来识别和处理以定义的方式使用这些代码的交易来完成的。一旦分配了OPCODE，就可以在交易中使用该代码，以执行特定的操作或功能。

For example, a new opcode could be used to enable support for a new type of cryptographic signature scheme, or to introduce a new class of script operations that could be used to build more complex contracts."

例如，可以使用新的OpCode来支持新型的加密签名方案，或引入新的脚本操作，该操作可用于建立更复杂的合同。”

With discussions on activation paths now ongoing, and proposals such as A Complete Union: Merging Bitcoin Improvement Proposals (March 2024) detailing integration of OP_CAT and PayToMany into a single upgrade package, the trajectory of this initiative suggests that Bitcoin's programmability may soon expand further.

随着有关现在正在进行的激活路径的讨论，以及诸如完整联合的建议：合并比特币改进建议（2024年3月），详细介绍了OP_CAT和Paytomany整合到单个升级软件包中，该计划的轨迹表明，比特币的可编程性可能很快就可以进一步扩展。

Together, these developments present a deeper tension around Bitcoin's identity.

这些发展共同围绕比特币的身份带来了更深的张力。

Those in favor of more permissive data policies view this evolution as pragmatic,

那些赞成更允许的数据政策的人将这种进化视为务实，