比特幣核心對op_return限制的刪除sparks敏銳的部門

即將發布

Plans by Bitcoin Core to remove the long-standing OP_RETURN limit have sparked sharp division across the ecosystem.

比特幣核心的計劃消除了長期的OP_Return限制，使整個生態系統都引發了敏銳的劃分。

The upcoming release will, by default, lift the 80-byte ceiling that previously restricted transaction-embedded data, presenting the change as a modernization of policy in response to shifting network practices.

默認情況下，即將發布的版本將取消以前限制交易包含數據的80字節天花板，將這一變化表示為政策的現代化，以響應轉移網絡實踐。

Originally introduced as a soft deterrent, OP_RETURN allowed users to embed small, provably unspendable data without bloating the unspent transaction output (UTXO) set. The limit aimed to prevent abuse while enabling legitimate use cases such as timestamping or cryptographic commitments.

OP_RETURN最初以軟威懾作用引入，允許用戶嵌入小的，可證明的不可投射的數據，而無需膨脹未固定交易輸出（UTXO）集。該極限旨在防止濫用，同時實現合法用例，例如時間戳或加密承諾。

However, the cap has increasingly proved ineffective. Developers, including Greg “instagibbs” Sanders, argued that the existing ceiling merely shifted these activities into more opaque alternatives that undermined network health.

但是，蓋子越來越多地證明是無效的。包括Greg“ Instagibbs” Sanders在內的開發人員認為，現有的天花板僅將這些活動轉變為破壞網絡健康的更不透明的替代方案。

In a public statement, Sanders noted that “large-data inscriptions are happening regardless.”

桑德斯在一份公開聲明中指出：“無論如何，大數據銘文正在發生。”

"We're rendering these inscriptions unreadable by refusing to process transactions with unsupportable script types or cooperating with attempts to disable dust limits. We're also making it harder for miners to accept unserializable transactions or transactions that violate node policy in other ways."

“我們正在通過拒絕使用無法支持的腳本類型處理交易或與試圖禁用灰塵限制的嘗試進行交易，從而使這些銘文變得不可讀。我們也使礦工更難接受無效的交易或以其他方式違反節點策略的交易或交易。”

Pointing out that "persistent actors will continue to attempt to circumvent these measures," rendering the inscriptions readable seems like a natural progression.

指出“持久的演員將繼續嘗試避免這些措施”，使銘文可讀似乎是自然的進步。

"Inscriptions are a fact of life. Let's move them out of script and into the open, simplify relay and fee estimation, and collect these outputs into a single, provably unspendable structure."

“銘文是生活的事實。讓我們將它們從腳本中移出，簡化繼電器和收費估算，並將這些輸出收集到一個單一的，可證明的無人負擔的結構中。”

Aligning behavior with miners

與礦工保持一致

The move also saw the deprecation of the “-datacarriersize” parameter in pull request #32406.

此舉還看到了“ - dataCarriersize”參數的棄用＃32406。

These changes align Core's behavior more closely with how miners and other node implementations already operate. Unlike consensus rules, which govern what can be included in blocks, standardness rules such as the OP_RETURN cap primarily dictate how transactions are relayed across the peer-to-peer network.

這些更改與礦工和其他節點實現的運作方式更加緊密地融合了Core的行為。與共識規則不同，該規則可以控制塊中可以包含的內容，諸如OP_RETURN CAP之類的標準性規則主要決定了在點對點網絡中如何中繼交易。

As such, removing the ceiling does not force a change in what miners can include in blocks but recalibrates policy to match the real-world conditions that miners and other nodes already factor into their behavior.

因此，卸下天花板不會迫使礦工可以在區塊中包含的東西變化，而是重新校準了策略以匹配礦工和其他節點已經將其行為融入其行為的現實情況。

However, criticism of the move has been voiced by prominent figures who view the decision as deviating from Bitcoin's minimalist ethos.

但是，對這一舉動的批評是由著名人物表達的，他們認為該決定偏離了比特幣的極簡主義精神。

Luke Dashjr, maintainer of Bitcoin Knots—an increasingly popular alternative client with almost 5% of nodes—described the removal as "utter insanity."

比特幣結的維護者盧克·達什（Luke Dashjr）是一個越來越受歡迎的替代客戶，幾乎有5％的節點，將其描述為“完全瘋狂”。

Samson Mow, CEO of Jan3 and an outspoken Bitcoin advocate, suggested that operators who wish to reject the change can do so by running Knots or staying on older versions of Bitcoin Core.

JAN3首席執行官和直言不諱的比特幣擁護者Samson Mow建議，希望拒絕更改的運營商可以通過打結或保持較舊版本的比特幣核心來做到這一點。

According to Mow, maintaining stricter relay policies is crucial to preserve Bitcoin's role as a global, censorship-resistant monetary network.

根據MOW的說法，維持更嚴格的繼電器政策對於保留比特幣作為全球，持審查的貨幣網絡的作用至關重要。

Nevertheless, Mow pragmatically recognized that the removal of the limit has its advantages.

然而，MOW務實地認識到，去除極限具有其優勢。

"Delete the cap. Aligns default policy with actual network practice, minimises incentives for harmful workarounds, and simplifies the relay path.

“刪除上限。將默認策略與實際網絡實踐保持一致，最大程度地減少對有害解決方法的激勵措施，並簡化繼電器路徑。

Option 3 earned broad, though not perhaps unanimous, support. Dissenting parties remain free to modify software, run stricter policy, or propose new resource limits if empirical harm emerges."

選項3贏得了廣泛的支持，儘管不是一致的支持。如果經驗危害出現，則無權政黨可以自由修改軟件，運行更嚴格的政策或提出新的資源限制。 ”

Those in favor of removing the limit highlight the fact that with blocks still subject to four million weight units, dust limits, and other constraints, fears of unchecked data spam are overstated.

那些贊成消除限制的人強調了一個事實，即由於塊仍然受到400萬個重量單位，塵埃限制和其他限制的限制，對未經檢查的數據垃圾郵件的擔憂被誇大了。

They argue that removing arbitrary barriers makes relay and fee estimation more predictable and encourages cleaner data use by consolidating inscriptions into provably unspendable OP_RETURN outputs rather than misusing spendable script paths.

他們認為，消除任意障礙會使繼電器和費用估計更可預測，並通過將銘文合併到可證明的無用的OP_Return輸出中，而不是濫用可支付的腳本路徑，從而鼓勵更清潔的數據使用。

A broader shift in programmability

可編程性的更大轉變

The timing of the OP_RETURN policy shift coincides with growing momentum for more ambitious protocol upgrades.

OP_Return政策轉變的時機與增長的動力相吻合，以進行更雄心勃勃的協議升級。

Once a memetically disabled opcode assigned to OP_SUCCESS126 in BIP-347, OP_CAT has advanced to become a subject of serious discussion and proposal among developers and industry researchers.

一旦在BIP-347中分配給OP_SUCCESS126的模因殘障的OPCODE後，OP_CAT已提出，成為開發人員和行業研究人員中認真討論和建議的主題。

Galaxy Digital's research team positioned both OP_CAT and OP_CTV as straightforward enhancements that could be coded in a few days and boasted major implications for DeFi applications.

Galaxy Digital的研究團隊將OP_CAT和OP_CTV都定位為直接的增強功能，可以在幾天內編碼，並對DEFI應用程序具有重大影響。

"Unassigned opcodes and opcode variants can be used to introduce new capabilities to the VM. This is done by modifying the node software to recognise and process transactions that use these codes in a defined way. Once an opcode is assigned, it can be used in transactions to perform a specific operation or function.

“未分配的OPCODES和OPCODE變體可用於將新功能引入VM。這是通過修改節點軟件來識別和處理以定義的方式使用這些代碼的交易來完成的。一旦分配了OPCODE，就可以在交易中使用該代碼，以執行特定的操作或功能。

For example, a new opcode could be used to enable support for a new type of cryptographic signature scheme, or to introduce a new class of script operations that could be used to build more complex contracts."

例如，可以使用新的OpCode來支持新型的加密簽名方案，或引入新的腳本操作，該操作可用於建立更複雜的合同。 ”

With discussions on activation paths now ongoing, and proposals such as A Complete Union: Merging Bitcoin Improvement Proposals (March 2024) detailing integration of OP_CAT and PayToMany into a single upgrade package, the trajectory of this initiative suggests that Bitcoin's programmability may soon expand further.

隨著有關現在正在進行的激活路徑的討論，以及諸如完整聯合的建議：合併比特幣改進建議（2024年3月），詳細介紹了OP_CAT和Paytomany整合到單個升級軟件包中，該計劃的軌跡表明，比特幣的可編程性可能很快就可以進一步擴展。

Together, these developments present a deeper tension around Bitcoin's identity.

這些發展共同圍繞比特幣的身份帶來了更深的張力。

Those in favor of more permissive data policies view this evolution as pragmatic,

那些贊成更允許的數據政策的人將這種進化視為務實，