XRP Ledger batch processing function V1.1 is about to be activated, and asset management companies a

XRP Ledger Batch V1.1 迈向有条件激活

交付与支付（DvP）塑造升级应用场景

XRP Ledger Batch V1.1 已获得 35 个受追踪验证节点中的 30 个支持，但其激活取决于在 9 月 29 日之前维持至少 80% 的支持率。

该功能可将多达八个交易打包，使资产转移、付款和平台费用能够作为一个整体操作共同结算或失败。Ripple 表示，资产管理者和商业项目正在围绕“交付与支付”机制构建应用，但合作伙伴的具体细节尚未披露。

此前，开发人员在发现签名漏洞后撤回了 Batch V1.0，随后发布了经过重新设计的授权机制并经过 Halborn 和 Common Prefix 审查的 V1.1 版本。Ripple 指出，资产管理公司正在为 XRP Ledger Batch V1.1 做准备，这是一项针对链接交易的支付升级功能。

有条件激活路径

此次投票为 XRP Ledger Batch V1.1 提供了一条有条件的激活路径。在倒计时期间，验证节点可以改变其立场。如果支持率降至 80% 以下，计时器将停止。一旦修正案重新达到阈值，必须开始一个新的十四天周期。

According to data from the XRPL Dashboard, 30 of the 35 tracked verification nodes currently express support. The amendment requires 28 votes to start the countdown process, which began at 14:06:41 UTC on September 15. If support remains above 80% over the next 14 days, the activation may take effect after September 29.

Atomic Settlement and Batch Processing

XRP Ledger Batch V1.1 places transactions under parent operations. Users can submit up to eight linked transactions, with each transaction retaining its details. The "all-or-nothing" setting prevents partial settlements due to a single transaction failure. Unlike multi-step workflows, grouping operations provide settlement conditions for counterparties. If one of the links fails, the ledger will not complete the transactions in the other links. This design may simplify the settlement process for funds, trading venues and token issuers that use XRP Ledger.

In addition, it allows developers to combine transfer operations without relying on callbacks or manual reconciliations. Although this feature is not guaranteed to be adopted because the project still requires testing, compliance and preparation, it is crucial for asset management companies building digital markets. Funds can transfer tokenized assets and receive payments in the same ledger operation. This use case gives XRP Ledger Batch V1.1 a direct role in atomic settlement.

Application scenarios for delivery and payment

Akinyele identified "delivery and payment" as key application scenarios. This method links asset delivery to payment rather than requiring one party to send the asset first, thereby reducing the risk of incomplete settlement during the transaction process.

Ripple also pointed out that fee charging is another application scenario. Exchanges, wallets and marketplaces can attach service fees to customer transactions and then process payments and fees together as a grouped operation.

RippleX has not yet named commercial projects that use this feature. Akinyele said more details will be announced after partners formally define plans and release timetables. He added that activation would bring development work closer to the production environment.

Security Review and Historical Background

Activation of the plan follows the withdrawal of Batch V1.0. Researchers discovered a key signature verification flaw in February. Under certain conditions, the code may stop checking signatures early, allowing attackers to include transactions from other accounts without authorization. Because developers withdrew the verification node before activating the original amendment, the vulnerable code never controlled the real-time ledger, nor did it directly expose user funds.

RippleX used this incident to redesign parts of the signature and authorization model. The alternative was released on August 6 with xrpld version 3.3.0. Ripple said the code currently under consideration is consistent with this version.

The review includes internal adversarial testing, AI-assisted analysis, and Sherlock attack competitions. Security companies Halborn and Common Prefix conducted the assessment. RippleX also used internal adversarial testing before seeking verification node approval. The company said its broader review covered work before V1.1 returned to the vote.

This extended process supports the XRP Ledger Batch V1.1 regression verification node process. Akinyele said the team improved the review standards, resolved the flaws, and submitted Batch V1.1 for a new round of verification node voting.

According to the current timetable, the amendment will last until September 29. During this period, approval must remain at 80% or above. Any drop below that level will suspend activation and require a restart of the countdown after support returns.