提升比特币的OP_Return Caps就其作为数据载体的角色引发了辩论

op_return在比特币核心0.9.0中添加的脚本opcode允许用户附加80字节的任意信息

Bitcoin (BTC) developers have removed the default 80-byte limit on OP_RETURN outputs in an upcoming release of Bitcoin Core, enabling the insertion of larger data payloads and multiple OP_RETURN entries within a single transaction.

比特币（BTC）开发人员已在即将发布的比特币核心版本中删除了OP_Return输出的默认80字节限制，从而使较大的数据有效载荷插入，并且在单个交易中插入了多个OP_Return条目。

The change follows a prolonged debate within the Bitcoin community over whether the existing cap, introduced in 2014, has outlived its usefulness.

这一变化是在比特币社区中关于2014年推出的现有上限是否超过其有用性的持续辩论之后的。

As of May 12, 2025, Bitcoin Core had not merged any pull requests related to altering OP_RETURN limits and proposals remain open for review.

截至2025年5月12日，比特币核心没有合并与更改OP_RET_RETURN限制有关的任何拉动请求，并且提案仍在审查中。

What Is OP_RETURN?

什么是op_return？

OP_RETURN is a script opcode that allows users to append up to 80 bytes of arbitrary information—such as text, hashes, or protocol indicators—to transactions. Unlike spendable outputs, which are stored in the unspent transaction output (UTXO) set, OP_RETURN outputs are provably unspendable, allowing nodes to prune them without loss of funds.

OP_RETURN是一个脚本OpCode，允许用户将多达80个字节的任意信息（例如文本，哈希或协议指标）附加到交易中。与存储在Untpent Transaction输出（UTXO）集中的可支出输出不同，OP_RETTRURN输出是不可算力的，可以使节点修剪它们而不会损失资金。

This capability supports nonpayment applications, including timestamping ownership proofs, embedding metadata for layer-two (L2) protocols or intentionally burning coins in targeted use cases.output

此功能支持非付款应用程序，包括时间戳所有权证明，将元数据嵌入层 - 第二个协议（L2）协议或在目标用例中有意燃烧硬币。