比特幣（BTC）開發人員從OP_Return操作代碼中刪除數據尺寸限制以啟用銘文和序數

經過多年的無效試圖預防比特幣區塊鏈上的非財務（“任意”）存儲空間，開發人員正在疲憊不堪，他要求比特幣核心維護者將代碼更改拉入生產中，以消除數據尺寸限制。

Bitcoin (BTC) developers are discussing a code change to remove a data size limit, following years of ineffective attempts to prevent non-financial (“arbitrary”) storage on the blockchain.

經過多年的無效試圖防止區塊鏈上的非財務（“任意”）存儲，比特幣（BTC）開發人員正在討論刪除數據大小限制的代碼更改。

Peter Todd created a pull request (PR) no 32359 that would lift arbitrary limits on datacarrier outputs via Bitcoin’s “OP_Return” operation code, acknowledging two years of failed attempts.

彼得·托德（Peter Todd）創建了一個拉動請求（PR）No 32359，該請求將通過比特幣的“ OP_Return”操作代碼上的DataCarrier輸出進行任意限制，並確認兩年的失敗嘗試。

If Core maintainers pull the change into production via the main repository, Bitcoin node operators like miners would be able to publish more bytes of data via OP_Return outputs.

如果核心維護者通過主要存儲庫將更改納入生產，則像礦工這樣的比特幣節點運算符將能夠通過OP_Return輸出發布更多的數據字節。

According to Todd’s formalization of the proposal by Chaincode Labs’ Antoine Poinsot, for any developers who think the 83-byte limit on OP_Return’s scriptPubKey is silly, they should test the code changes and consider whether they agree with lifting the limit.

根據托德（Todd）對Chaincode Labs的Antoine Pooinsot對提案的形式化，對於任何認為OP_Return ScriptPubkey的83字節限制的開發人員很愚蠢，他們應該測試代碼更改並考慮是否同意提高限制。

Although the attempt to disincentivize datacarrier data use was mildly effective, many developers note that people can still store media, spam, and otherwise arbitrary data via non-OP-Return places like scriptsigs and unspendable outputs.

儘管試圖抑制DataCarrier數據使用的嘗試非常有效，但許多開發人員指出，人們仍然可以通過scriptsigs和不可投放的輸出來存儲媒體，垃圾郵件或其他任意數據。

Moreover, some users were simply bypassing scriptPubKey’s 83-byte limit altogether by privately broadcasting transactions to miner mempools like MARA Slipstream or non-mainstream nodes like Libre Relay, whose operators never even bothered enforcing that limit.

此外，一些用戶僅通過向Mara Slipstream或非主流節點（如Libre繼電器）等私人廣播交易而完全繞過ScriptPubkey的83字節限制，例如Libre繼電器，其運營商甚至從未費心執行該限制。

Poinsot cited users storing data on unspendable Taproot outputs as another example of the many workarounds to store arbitrary data on Bitcoin’s blockchain.

Puinsot引用了存儲無用的Taproot輸出數據的用戶，這是許多解決方法的另一個示例，這些解決方法可以在比特幣的區塊鏈上存儲任意數據。

Reactions

反應

Overall, developers posted mixed reactions to Bitcoin Core’s mailing list. Some developers sympathized with the ineffectiveness of limiting OP_Return when alternative data storage options were plentiful.

總體而言，開發人員對比特幣Core的郵件列表發表了不同的反應。當替代數據存儲選項大量時，一些開發人員對限制OP_RETURN的無效性表示同情。

On the other hand, Luke Dashjr, a staunch critic of OP_Return arbitrary data storage and its uses — such as Inscriptions and Ordinals — criticized the idea as “utter insanity.” Others joined him with upvotes and supportive comments.

另一方面，對OP_RET_RETURN任意數據存儲及其用途（例如銘文和序言）的堅定評論家Luke Dashjr批評了這一想法是“完全瘋狂的”。其他人則加入了他的支持和支持評論。

“The bugs should be fixed, not the abuse embraced,” he exclaimed in his typical style. A fervent defender of Bitcoin’s limited blockspace for financial purposes, he noted over two years of “attacks” by arbitrary data “spammers,” claiming that “the damage it has already done should be more than enough to prove the hands-off attitude is not viable. Am I the only one left on this list who actually cares about Bitcoin’s survival?”

他以典型的風格喊道：“這些蟲子應該是固定的，而不是虐待所接受的。”他是一位對財務目的有限的比特幣有限塊狀空間的捍衛者，他指出，在任意數據“垃圾郵件機”的兩年“攻擊”中，他聲稱“它已經造成的損害應該足以證明可行的態度是不可行的。

Many agreed with him. Others saw the limitation as pointless.

許多人同意他。其他人則將限制視為毫無意義。

OP_RETURN WARSEPISODE IV: NIXTHEFILTERShttps://t.co/IJxyZc87dI

op_return warsepisode iv：nixthefiltershtps：//t.co/ijxyzc87di

New reviews by developers were arriving by the hour via the mailing list thread and GitHub.

開發人員的新評論是通過郵件列表線程和github按小時到達的。

Some upvoted with a simple “concept ACK,” supportive lingo for ‘concept acknowledged,’ while falling short of a full technical test. Others posted “concept NACK” in non-acknowledgement of its conceptual merits.Got a tip? Send us an email securely via Protos Leaks.

有些人以簡單的“概念ack”投票，這是“概念認可”的支持性術語，同時還沒有進行完整的技術測試。其他人則在其概念優點的非挑選中發布了“概念nack”。提示？通過Protos洩漏向我們發送電子郵件。

For more informed news, follow us on X, Bluesky, and Google News, or subscribe to our YouTube channel.

有關更多知情的新聞，請關注我們在X，Bluesky和Google News上，或訂閱我們的YouTube頻道。