删除OP_Return限制

最近几天，Internet对删除OP_Return限制的提议一直很夸张 - 这是比特币核心OG开发人员Peter Todd提出的提案。

Author: Jaleel Jialiu

作者：Jalel Jialiu

In recent days, the Internet has been abuzz with the proposal to remove the OP_RETURN restriction - this is a proposal made by Bitcoin Core OG developer Peter Todd.

最近几天，Internet对删除OP_Return限制的提议一直很夸张 - 这是比特币核心OG开发人员Peter Todd提出的提案。

Although there are many doubts in the community about the change to OP_RETURN, according to an announcement posted on GitHub on May 5 by Bitcoin developer and Blockstream core contributor Greg Sanders (nicknamed "instagibbs"): In the next network upgrade, Bitcoin Core will no longer impose any byte or quantity restrictions on OP_RETURN.

尽管社区中对OP_Return的变化有很多疑问，但根据Github在5月5日在GitHub上发布的公告，比特币开发人员和Blockstream Core贡献者Greg Sanders（昵称为“ Instagibbs”）：在下一个网络升级中，比特币核心将不再对OP_Return对Opte或数量限制。

What exactly is OP_RETURN?

op_return到底是什么？

We all know that Bitcoin is a ledger that can never be tampered with, and every transaction is like writing a line of record on it.

我们都知道，比特币是一个永远无法篡改的分类帐，每笔交易就像在上面写一条记录。

OP_RETURN is like sticking a "note" on the edge of a book page - you can write a few dozen words or a small piece of data into it. This note is marked as "read-only" by the system. Others cannot use it as money, and it will not have any impact on other "money" records in the ledger.

op_return就像在书页面的边缘上贴上“注释” - 您可以在其中写几十个单词或一小部分数据。该注释由系统标记为“只读”。其他人不能将其用作钱，也不会对分类帐中的其他“钱”记录产生任何影响。

The reason for having such a "note" function is that sometimes people want to permanently pin some additional information (such as legal proof, short messages, anniversaries or even confessions) on the chain, but do not want to occupy the UTXO space used to store "tradable" bitcoins. With OP_RETURN, this information is thrown into a drawer like waste paper - the node only leaves traces and does not occupy the inventory, and the "available money" on the chain is still clean and neat.

具有这种“注释”功能的原因是，有时人们希望在链条上永久固定一些其他信息（例如法律证明，简短消息，周年纪念日甚至供认），但不想占用用于存储“可交易”比特币的UTXO空间。借助OP_Return，将这些信息扔到诸如废纸之类的抽屉中 - 节点只会留下痕迹而不会占据库存，而链条上的“可用货币”仍然很干净整洁。

In the past, in order to prevent people from writing long "notes" and clogging up the network, Bitcoin Core only allowed one OP_RETURN in each transaction by default, and a maximum of 80 bytes of content could be stored. If the content exceeded, the node would directly refuse to relay it and would not help package it.

过去，为了防止人们编写长长的“注释”并堵塞网络，默认情况下，比特币核心仅允许每笔交易中的一个OP_Return，最多可以存储80个字节的内容。如果内容超过内容，则节点将直接拒绝中继它，并且不会帮助包装。

Now, the 80-byte and single-line limit are gone - you can write as long as you want, as many notes as you want, and nodes will automatically relay and miners will be happy to package them.

现在，80字节和单线限制已经消失 - 您可以根据需要写的时间来编写，并随心所欲，节点会自动中继，矿工将很乐意打包它们。

But the fact is that people have been working around 80 bytes for a long time.

但事实是，人们已经工作了大约80个字节了很长时间。

Before the OP_RETURN limit, there were ways to bypass the 80-byte limit. No matter how strict the filtering and relay strategies were, they could not stop people who really wanted to write data on Bitcoin. Because only miners and handling fees determine which transactions are put on the chain, giving miners higher rewards will naturally tend to pack more transactions, and the gameplay will not change due to node strategies.

在OP_Return限制之前，有一些方法可以绕过80字节的限制。无论过滤和继电器策略多么严格，他们都无法阻止真正想编写比特币数据的人。因为只有矿工和处理费才能确定链条上的哪些交易，所以给矿工较高的奖励自然会倾向于包装更多的交易，并且由于节点策略，游戏玩法不会改变。

For example, the well-known Tapoort Wizz NFT, a nearly 4M image, filled up an entire block. In addition, the Ordinals inscriptions and runes used various "detours and workarounds" to bypass restrictions. Some were even written into spendable outputs, which took up more resources.

例如，著名的tapoort wizz nft，近400m的图像，填满了整个块。此外，序数铭文和符文都使用了各种“弯路和解决方法”来绕过限制。有些甚至被写入了可支出的产出中，这占用了更多的资源。

Is this more in line with the spirit of Bitcoin?

这更符合比特币的精神吗？

According to the opinions of various developers, we can know that first of all, Bitcoin Core has its own "standardness policy" in the transaction propagation (relay) stage, which is used to perform three levels of checks before the transaction reaches the miners: first, to prevent "denial of service" attacks and reject transactions whose computing power, memory or bandwidth consumption far exceeds the transaction fee; second, through strategies to guide wallet authors to construct transactions that save transaction fees and do not create redundant UTXO; third, to retain upgrade security - treating unknown opcodes or version bits as "non-standard" until the soft fork is officially activated.

根据各种开发人员的意见，我们可以知道，首先，比特币核心在交易份额（接力）阶段具有自己的“标准性政策”，该阶段用于在交易到达矿工之前执行三个级别的检查：首先，首先，以防止“拒绝服务”攻击并拒绝其计算电源或频繁的交易量超过交易的交易，远远超过了交易费用远超过了交易费用远超过了交易费用远远超过了交易范围。其次，通过指导钱包作者构建交易的策略，以节省交易费用并不会产生冗余的UTXO；第三，要保留升级安全性 - 将未知的Opcodes或版本位视为“非标准”，直到正式激活软叉为止。

OP_RETURN and its 80-byte upper limit are the product of this concept: giving users a provably "unspendable" output that can store a small commitment or hash and prevent nodes from counting it as UTXO, thereby avoiding "losing money" garbage output on the chain.

OP_RETURN及其80字节的上限是此概念的产物：为用户提供一个可证明的“无法承受的”输出，该输出可以存储一个少量的承诺或哈希，并防止节点将其计算为UTXO，从而避免在链条上避免“丢失金钱”垃圾输出。

But now this soft limit has become useless. On the one hand, private mining pools and some centralized services do not enforce this rule at all. Anyone who wants to write a large amount of data can bypass the strategy - either paying miners directly, or hiding the information with bare-multisig, fake public keys, or even spendable scripts - and still put the content they want to write on the chain; on the other hand, adding a bunch of blacklist filters at every turn will only turn into a "cat and mouse" game, which can neither stop the most basic data from being written, nor increase the risk of accidentally damaging user funds.

但是现在，这种软限制已经毫无用处。一方面，私人采矿池和一些集中式服务根本不执行此规则。任何想撰写大量数据的人都可以绕过策略 - 直接向矿工付款，或者用裸露的multisig，伪造的公共钥匙或什至可以花费的脚本来隐藏信息 - 并且仍然将他们想写在链条上的内容；另一方面，每次添加一堆黑名单过滤器只会变成“猫和鼠标”游戏，这既不能阻止最基本的数据被编写，也不能增加意外损害用户资金的风险。

Developers on the supporting side believe that after completely removing the 80-byte limit, nodes and wallets can enjoy two major practical benefits: first, the UTXO set is cleaner, and the data is packed into a clearly "unspendable" OP_RETURN output, rather than entangled in various fancy scripts or multiple transactions; second, nodes are more unified in what

支持方面的开发人员认为，在完全删除了80字节的限制之后，节点和钱包可以享受两个主要的实际好处：首先，UTXO集合更加干净，并且将数据包装成一个明显的“不可投放”的OP_RETTRUNT输出，而不是在各种精美的脚本或多个交易中纠缠在一起；其次，节点在什么方面更加统一