重點

xrpld 3.3.0 版本請驗證者考慮五項修正案：先前撤回的 Batch 與 Permission Delegation 功能的修訂版本，以及三項新提案 — Confidential MPT、Sponsored Fees and Reserves 與 Dynamic MPT。 Batch 與 Permission Delegation 先前因發現重大安全性漏洞而被撤回，重新引入的版本反映了已修正的設計與額外保護措施。 如果通過，這些變更旨在改善私人代幣轉移、允許機構贊助使用者費用，並使代幣管理更具彈性。每項修正案仍需獲得 80% 驗證者連續兩週的支持才能啟動。

情緒分析

• 整體情緒審慎偏正面。下方的進度條以中度有利的強度量化此情緒，反映出對修正後設計和新功能的樂觀，同時因過去的安全問題而持續保持警惕。
  65%

文章內容

The XRP Ledger is preparing an xrpld 3.3.0 release that will place five amendments before validators. Two of those—Batch and Permission Delegation—are revised versions of features previously removed after researchers discovered critical vulnerabilities. The other three proposals—Confidential MPT, Sponsored Fees and Reserves, and Dynamic MPT—introduce new capabilities intended to broaden privacy, lower onboarding friction, and increase token flexibility. All amendments require the network’s established threshold of at least 80% of trusted validators to back them for two consecutive weeks before they take effect.

Batch, originally intended to allow up to eight cross-account transactions to execute atomically so that either all succeed or none do, was pulled after a flaw in signature validation was found. Security researchers showed that the issue could theoretically permit unauthorized execution of transactions from accounts without holding their keys. Validators were advised to reject the amendment then, and an emergency server release prevented its activation on the main network. No funds were lost because the amendment never reached activation.

Permission Delegation aimed to let an institution grant narrowly scoped signing authority to another account without handing over full control. That amendment was disclosed as vulnerable in September 2025; the bug could allow one account to charge fees to another and potentially drain balances. As a result, it was disabled and its documentation marked obsolete. The revised Permission Delegation included in xrpld 3.3.0 is intended to correct the prior design flaws and reintroduce the feature with stronger safeguards.

The three new proposals target privacy, cost sponsorship and token management. Confidential MPT combines zero-knowledge proof techniques with elliptic-curve encryption so that balances and transfer amounts on Multi-Purpose Tokens can remain private while still allowing selective verification by auditors or regulators. Sponsored Fees and Reserves allows an institution or platform to cover another account’s transaction fees and the XRP reserve requirement, removing a barrier for users who might otherwise need to acquire XRP before interacting with tokens. Dynamic MPT gives token issuers the ability to designate, at issuance, which token properties may be changed later, so updates to fees or metadata can occur without a full token migration.

Collectively, these amendments are framed as steps toward using the XRPL’s token capabilities at scale for activities like global transfers, trading, collateralization and settlement. However, activation is not automatic. Past amendment votes show that obtaining 80% approval is a high bar: recent lending-protocol and single-asset-vault proposals each attracted roughly a third of validator support, well short of the threshold. Batch in particular has a prior record of failing to pass the voting stage, and that history may influence how validators view a reintroduced version.

Validator approval is central to the ledger’s governance model. Amendments only take effect when the validator set itself reaches the supermajority threshold for two consecutive weeks; this design ensures that protocol changes are driven by the decentralized validator community rather than any single organization. The xrpld 3.3.0 release therefore reflects both technical revisions to earlier features and the community-oriented process that determines whether those revisions become part of the running network.

There are trade-offs and considerations to monitor. Enhanced privacy through Confidential MPT must be balanced with compliance and auditability requirements; sponsored fees increase accessibility but shift cost burdens to sponsors; and dynamic token properties provide flexibility while requiring careful governance to prevent undesirable unilateral changes. These amendments collectively aim to make tokenized activity on XRPL more practical and private, but their real-world impact depends on validator approval and the robustness of the updated designs.

As the community evaluates xrpld 3.3.0, the revision and reintroduction of previously flawed features will likely draw scrutiny alongside interest in the new proposals. The eventual outcome will shape how the ledger accommodates token-scale use cases while maintaining security and decentralization.

關鍵見解表