Ripple prepares asset managers for atomic settlement upgrade
Ripple is moving toward activation of Batch V1.1 on the XRP Ledger, a rebuilt feature that groups up to eight transactions to settle atomically or fail together. The upgrade is scheduled for Sept. 29, 2026, conditional on 80% validator support, according to Ayo Akinyele, head of engineering at RippleX.
The activation countdown began on Sept. 15 at 14:06:41 UTC, with 30 of 35 validators currently supporting the amendment. A 14-day window allows validator positions to shift; if support drops below the 80% threshold before the projected activation date, a new countdown period must begin.
Batch V1.1 enables delivery-versus-payment transactions where asset and payment transfers occur atomically or not at all. “Batch allows multiple transactions to be grouped together so they either all execute or none do. That is particularly important for use cases like delivery-versus-payment, where the asset and payment need to move atomically,” Akinyele said.
The feature also allows exchanges, wallets, and marketplaces to attach service fees directly to customer transactions as a single operation, eliminating settlement risk where one party settles while the other fails.
Security overhaul follows critical flaw discovery
Batch V1.1 represents a redesigned version of the original Batch V1.0, which contained a critical flaw in its signature-validation process discovered in February 2026. Under certain conditions, the vulnerable code could stop checking signatures early and allow attackers to include transactions from another account without authorization. The flawed code never governed the live ledger and no funds were exposed.
RippleX responded by conducting internal adversarial testing, AI-assisted analysis, a Sherlock attack contest, and security assessments by firms Halborn and Common Prefix before resubmitting Batch V1.1. The xrpld version 3.3.0 containing the rebuilt feature was released on Aug. 6, 2026.
“We used it as an opportunity to go much deeper on the implementation, redesign parts of the signing and authorization model, and significantly expand the security review,” Akinyele said. “The bigger point is that we established a very high bar. We found a serious issue in V1.0 before activation, stopped it, redesigned and hardened the implementation, expanded the review considerably, and only then put V1.1 back in front of validators.”
Commercial projects lined up for launch
Asset managers are preparing to deploy applications using Batch V1.1 once the feature activates. “Some projects are already being built with Batch in mind, so activation would allow that work to move closer to production. We’ll share more on specific partners and launch timing as those plans are finalized,” Akinyele said.
He added that Ripple plans to disclose more details about asset manager partnerships after the feature goes live. “We’ll be sharing more once the feature is live, including work with key asset managers,” Akinyele said.
