刪除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輸出，而不是在各種精美的腳本或多個交易中糾纏在一起；其次，節點在什麼方面更加統一