Ripple says asset managers and other commercial projects are already preparing for XRP Ledger Batch V1.1, an upgrade designed to make linked transactions succeed together or fail together.
The feature is now moving through a 14-day validator countdown after developers rebuilt it and expanded its security review following a serious flaw in the original version.
At the center of the upgrade is a relatively simple idea with practical consequences: several transactions can be bundled into one operation, with an all-or-nothing option that prevents only part of a deal from settling.
XRP Ledger Batch V1.1 can group up to eight transactions at once. For asset transfers tied to payments, that means the two sides can be completed as a single atomic operation rather than leaving one party exposed if the other transaction fails.
“Batch allows multiple transactions to be grouped together so they either all execute or none do,” Ayo Akinyele, head of engineering at RippleX, told CoinDesk. “That is particularly important for use cases like delivery-versus-payment, where the asset and payment need to move atomically.”
Delivery-versus-payment, or DvP, connects an asset transfer directly to its payment. Instead of requiring one side to move first and trust the other to follow, the ledger can handle both legs together.
That structure could matter beyond financial-market transactions. Exchanges, wallets and marketplaces could also use Batch to combine a customer payment with the platform’s fee, rather than processing the charges in separate transfers.
“Some projects are already being built with Batch in mind, so activation would allow that work to move closer to production,” Akinyele said.
XRP Ledger Batch V1.1 Had to Survive a Security Reset
The road to activation has already included a major detour.
In February, researchers identified a critical flaw in the signature-validation process of Batch V1.0. In certain conditions, the issue could cause the software to stop checking signatures early, potentially allowing an attacker to add transactions from another account without authorization.
The vulnerable version never went live. Validators were still considering the amendment when the problem was found, so the code did not govern the live XRP Ledger and funds were not exposed.
RippleX then withdrew the original proposal and went beyond simply patching the defect. According to Akinyele, developers redesigned parts of the signing and authorization model and subjected the replacement to a broader security review.
The revised implementation arrived in xrpld version 3.3.0 on Aug. 6. That is the same code validators are now considering for activation.
The expanded review included internal adversarial testing, AI-assisted analysis, a Sherlock attack contest and assessments from security firms Halborn and Common Prefix.
“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 result is XRP Ledger Batch V1.1, now backed by 30 of the network’s 35 tracked validators. That is above the 28 votes needed to begin the activation countdown.
The countdown started Sept. 15 at 14:06:41 UTC, putting the projected activation shortly after the same time on Sept. 29.
That date is not locked in. Validator support must remain at or above 80% throughout the entire 14-day period. Validators can change their votes, and a drop below the threshold would stop the clock and require a new countdown once the proposal regains enough support.
For Ripple, that makes the next two weeks less about unveiling another experimental feature and more about seeing whether a heavily reviewed piece of infrastructure can make the jump into live use.
And with asset managers already preparing around the functionality, the significance of XRP Ledger Batch V1.1 may ultimately be measured less by the amendment itself than by what gets built once it is active.