Hassan Maishera
TL;DR
-
Ripple says asset managers and other commercial projects are preparing to use the XRP Ledger’s Batch V1.1 feature.
-
The upgrade can group up to eight transactions and execute them together on an all-or-nothing basis.
-
Batch V1.1 has secured support from 30 of 35 tracked validators, exceeding the threshold needed to begin activation.
-
The amendment could activate shortly after 14:06 UTC on Sept. 29 if validator support remains above 80%.
XRP Ledger Batch Upgrade Approaches Activation
Ripple says asset managers and other commercial projects are preparing to use an XRP Ledger feature that allows multiple connected transactions to settle as a single operation.
Known as Batch V1.1, the upgrade can group up to eight transactions. Its all-or-nothing mode ensures that every transaction in the group succeeds or the entire batch is canceled.
The structure prevents situations in which one part of a financial agreement settles while another fails.
Ayo Akinyele, head of engineering at RippleX, said the company plans to provide more details about participating asset managers after the feature goes live.
He added that some projects are already being developed with Batch in mind, meaning activation could bring them closer to entering production.
One of the main potential applications for Batch V1.1 is delivery-versus-payment settlement.
Delivery-versus-payment links the transfer of an asset directly to its corresponding payment. Instead of relying on one party to complete its side of the transaction first, the ledger processes both components together or rejects both.
This mechanism can reduce counterparty and settlement risks for asset managers, tokenized securities platforms, and other financial institutions using blockchain infrastructure.
Batch could also help exchanges, wallets and marketplaces collect fees more efficiently. A customer payment and a platform’s service fee could be included in the same operation instead of being processed through separate transfers.
Validator Support Clears Required Threshold
Batch V1.1 has received support from 30 of the XRP Ledger’s 35 tracked validators. The amendment needed at least 28 votes to enter its activation countdown.
The 14-day countdown began on Sept. 15 at 14:06:41 UTC. If validator support remains at or above 80% throughout the full period, the feature is expected to activate shortly after the same time on Sept. 29.
The activation date remains conditional because validators can change their votes at any time.
If support falls below 80% before the countdown ends, the clock will stop. A new 14-day window would begin only after the amendment regains the required level of validator backing.
Batch V1.1 replaces an earlier version of the amendment that developers withdrew after researchers found a serious security vulnerability.
The flaw, discovered in Batch V1.0 in February, affected the feature’s signature-validation process. Under certain conditions, the code could stop checking signatures too early.
That weakness could have allowed an attacker to include transactions belonging to another account without receiving authorization from its owner.
However, the amendment was still under validator consideration when the flaw was discovered and had not been activated on the XRP Ledger. The vulnerable code therefore never controlled transactions on the live network, and no user funds were exposed.
RippleX Expands Security Review Before New Vote
Rather than addressing only the individual error, RippleX redesigned parts of the Batch feature’s signing and authorization system.
Akinyele said the development team conducted a broader examination of the implementation and significantly expanded its security review before resubmitting the amendment to validators.
The replacement code was included in xrpld version 3.3.0, released on Aug. 6. That implementation is now approaching activation.
Testing included internal adversarial reviews, AI-assisted analysis and a Sherlock attack contest. Security firms Halborn and Common Prefix also assessed the revised code.
Akinyele said the process established a higher standard for XRP Ledger upgrades, emphasizing that developers detected the original vulnerability before activation, stopped the proposal, and hardened its replacement before starting another validator vote.
