介绍第一个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。