XRP Ledger batch upgrade nears activation after signature flaw forced a redesign
Ripple says asset managers are preparing to use the rebuilt Batch feature, which bundles up to eight transactions into one all-or-nothing settlement, once a 14-day validator vote concludes on Sept. 29.
Illustration · generated, not a photograph
Ripple is pointing commercial partners — asset managers among them — toward a rebuilt XRP Ledger feature designed to settle multiple linked transactions in a single step, weeks before it is due to switch on, the company told CoinDesk.
The upgrade, Batch V1.1, bundles as many as eight transactions into one operation and runs in an all-or-nothing mode: either every transaction completes or the entire group is discarded. That removes the risk of one leg of a deal landing while the other stalls out.
The most prominent use case is delivery-versus-payment, a settlement structure that ties the movement of an asset to its payment so that neither side has to hand over first and trust the other to follow. RippleX engineering head Ayo Akinyele said the feature matters precisely because the asset and the payment have to move atomically. He added that Ripple plans to name specific asset-manager partners once the feature is live.
Beyond settlement
The bundling capability has applications outside trading, too. Exchanges, wallets and marketplaces could fold their service fees into a customer's transaction itself, processing payment and charge as one unit instead of two separate transfers.
Whether the upgrade goes live now rests with the ledger's validator vote. Thirty of the 35 tracked validators have backed the amendment, clearing the 28-vote threshold needed to start the activation countdown. That clock started Sept. 15 at 14:06:41 UTC and, if support holds at 80% or higher for the full 14 days, Batch V1.1 should activate at roughly the same time of day on Sept. 29. Validators can still change their votes, so the date is not guaranteed. Should support slip below the 80% floor, the countdown halts and a fresh 14-day window begins once the proposal recovers its majority.
The rebuilt version follows a serious security episode. In February, researchers discovered a critical flaw in the original Batch V1.0: under certain conditions, its signature-validation process could stop checking early, letting an attacker slip in transactions from another account without that account holder's approval. Because the amendment had not yet reached the live ledger, the bug never affected real funds.
RippleX treated the incident as a prompt for a wider overhaul rather than a spot fix. "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 reworked code shipped in xrpld version 3.3.0 on Aug. 6 — the same implementation now before validators. The expanded review combined internal adversarial testing, AI-assisted analysis, a Sherlock attack contest, and assessments from security firms Halborn and Common Prefix.
Akinyele characterized the episode as a proof of process: the flaw was caught before activation, the implementation was redesigned and hardened, the review was broadened, and only then was the replacement put back to a vote.
Source reporting
The outlets whose reporting this account was written from.
Written from the reporting and primary documents credited at the foot of this story. Facts are credited to the outlet or document that established them. How Chainpress works