介紹第一個1兆格塊，塞滿了3,333個巫師銘文的巫師

最近幾週，一項旨在消除比特幣對腳本Opcodes的80字節限制的建議引起了人們的辯論，最終導致了一些人稱之為2025年的OP_Return War。

In recent weeks, a proposal to eliminate Bitcoin’s 80-byte limitation on script opcodes has sparked lively debate, culminating in what some are calling the OP_RETURN War of 2025.

最近幾週，一項提議消除了比特幣對腳本操作編碼的80字節限制的提議引發了激烈的辯論，最終導致了一些人稱之為2025年的OP_Return War。

The adjustment, which concerns relay policies rather than consensus rules, ultimately comes down to individual nodes. Meanwhile, individuals and organizations have been creatively employing OP_RETURN transactions—to experiment, make statements, or signal potential shifts in Bitcoin’s direction as it straddles the line between storing JPGs or serving as a peer-to-peer (P2P) payment mechanism.

調整涉及中繼政策而不是共識規則，最終取決於單個節點。同時，個人和組織一直在創造性地採用OP_Return交易 - 試驗，陳述或信號向比特幣的方向轉移，因為它跨越了存儲JPG或用作點對點（P2P）支付機制之間的界線。

OP_RETURN is a Bitcoin script opcode that permits embedding up to 80 bytes of unspendable data without contributing to the UTXO set expansion. It’s used for purposes ranging from timestamping and asset issuance to inscriptions, but the size ceiling has remained a point of contention due to the varied use cases.

OP_RETURN是一個比特幣腳本OPODE，允許嵌入80個字節的不可投放數據，而無需為UTXO SET擴展做出貢獻。它用於目的，從時間戳和資產發行到銘文，但由於用例的不同，尺寸的上限仍然是爭論的點。

Lifting the cap would eliminate the need for convoluted methods, such as the insertion of an image into a bitcoin transaction. However, it also raises concerns about potential spam if transactions are brimming with an excess of bytes.

舉起蓋子將消除需要捲曲的方法的需求，例如將圖像插入比特幣交易中。但是，如果交易覆蓋過多的字節，這也會引起人們對潛在垃圾郵件的擔憂。

For a deeper exploration of the mechanics of OP_RETURNs and the central issues driving the current debate, check out this article.

要更深入地探索OP_Returns的機制和推動當前辯論的中心問題，請查看本文。

One recent OP_RETURN transaction was set up to process transactions in a specific order and filter out any that didn't meet the criteria.

建立了最近的一項OP_RETTRACH交易，以特定順序處理交易，並過濾掉不符合標準的任何內容。

“Never gonna give you OP_RETURN. never gonna let you down Never gonna run around and desert you Never gonna make you cry, never gonna say goodbye Never gonna tell a ‘lie and hurt you.”

“永遠不會給你op_return。永遠不會讓你失望，永遠不會逃避，而你永遠不會讓你哭泣，永遠不會說再見永遠不會說'謊言和傷害你。”

Another OP_RETURN reads: “Filters have a huge influence on what gets mined.”

另一位OP_RETURN讀到：“過濾器對開采的東西產生了巨大影響。”

The ‘First-Ever 1 Megger’

“有史以來1 Megger”

On May 15, the group known as The Wizards of Ord crafted a block—notably block 896,696—to showcase their full set of 3,333 The Wizards of Ord inscriptions.

5月15日，該小組被稱為Ord的巫師，製作了一個街區（尤其是896,696塊），以展示其完整的3,333個Ord Inscriptions的巫師。

“We just created the largest OP_RETURN in Bitcoin history,” the X account @lifofifo wrote. “Introducing the first-ever 1 megger, Block 896696, which includes every single The Wizards of Ord in OP_RETURN data.”

X帳戶@lifofifo寫道：“我們剛剛創建了最大的OP_Return。” “引入第一個Megger，第896696塊塊，其中包括OP_Return數據中ORD的每個嚮導。”

To craft a transaction that could occupy an entire block with nearly 1 MB of arbitrary data via OP_RETURN, the creator had to navigate around multiple policy-level constraints embedded in the default behavior of Bitcoin node software.

為了通過OP_Return製作一項可以用近1 MB的任意數據佔據整個塊的交易，創建者必須在比特幣節點軟件的默認行為中圍繞多個策略級別的約束進行導航。

Although OP_RETURN is capped at 80 bytes to discourage misuse and excessive chain growth, this limitation isn't a consensus rule—it’s enforced solely through the standardness policies followed by most full nodes. In this instance, the transaction sidestepped that nuance by designating the outputs as non-standard and submitting the transaction directly to a mining pool—namely Marathon (NYSE:MARA)—that opted to ignore default policies and include it in a block regardless.

儘管OP_RETURN的限制為80個字節，以阻止濫用和過度的鍊鍊增長，但這種限制不是共識規則，而是僅通過標準性策略強制執行。在這種情況下，交易通過將輸出指定為非標準並將交易直接提交給採礦池（即馬拉松（NYSE：MARA））來避免這種細微差別，該池選擇忽略默認的策略，並將其包括在塊中。

The transaction was constructed using version 2 of the Bitcoin format, which supports Segwit functionality and offers expanded scripting capabilities for inputs and outputs.

交易是使用比特幣格式的版本2構建的，該版本支持SEGWIT功能，並為輸入和輸出提供擴展的腳本功能。

No bitcoin was actually transferred—0 BTC sent—as the transaction served exclusively as a vehicle for embedding data. However, miners are frequently drawn to such blocks because of the fees they offer, even in the absence of monetary exchange. When the attached fee is sufficiently generous, it can persuade a miner to include the transaction despite its inefficiency in terms of fee-per-byte economics.

實際上，沒有比特幣被轉移了-0 BTC發送的，因為該交易專門用作嵌入數據的工具。但是，即使在沒有貨幣交換的情況下，礦工也經常被吸引到這樣的區塊上。如果附件足夠慷慨的費用，它可以說服礦工在每字節經濟學方面效率低下，包括交易。

Knots Node Runners Aim to Filter

結節點跑步者的目標是過濾

The flurry of onchain messages and the debut of the “first-ever 1 megger” come amid rising adoption of the Bitcoin Knots node implementation.

由於比特幣結節點實現的採用不斷提高，因此一系列OnChain消息和“首先1 Megger”的首次亮相。

In contrast to the forthcoming release of Bitcoin Core 24.9, which will introduce an updated script opcode and adjust the standardness policy accordingly, rendering it capable of relaying transactions with a broader script opcode set, Knots retains the -datacarrier and -datacarriersize flags, offering operators granular control. Setting -datacarrier=0 allows a node to reject all OP_RETURN transactions, while modifying -datacarriersize enables the enforcement of stricter data caps, such as the conventional 80-byte limit.

與即將發布的比特幣Core 24.9發布的版本相反，該版本將引入更新的腳本OpCode並相應地調整標準性策略，使其能夠將交易與更廣泛的腳本OpCode集相關，因此Knots保留了-DataCarrier和-DataCarrier和-DataCarriers flags，並提供操作員Granular Granular Control。設置-DataCarrier = 0允許節點拒絕所有OP_Return Transactions，而修改-DataCarriersize則可以實現更嚴格的數據上限，例如常規的80字節限制。

These parameters filter incoming transactions from a node's mempool, effectively halting their dissemination to connected peers.

這些參數從節點的mempool過濾傳入的交易，從而有效停止其傳播到連接的同伴。

Knots now runs on roughly 2,000 nodes, up from just 600 in mid-March, while the total count of publicly visible Bitcoin Core nodes has remained relatively stable at 19,470.

現在的打結約為2,000個節點，高於3月中旬的600個節點，而公開可見的比特幣核心節點的總數相對穩定，為19,470。