Ripple says asset managers are preparing for XRP Ledger’s next payments upgrade

Ripple says asset managers and other commercial projects are preparing to use an XRP Ledger feature that can make several linked transactions settle together, as a rebuilt version of the upgrade approaches activation following an extensive security review.

The feature, called Batch V1.1, can combine as many as eight transactions into a single operation. Its all-or-nothing mode ensures that every transaction succeeds or the entire group is canceled, avoiding cases in which one side of a deal settles while the other fails.

“We’ll be sharing more once the feature is live, including work with key asset managers,” Ayo Akinyele, head of engineering at RippleX, said in comments shared with CoinDesk.

“Batch allows multiple transactions to be grouped together so they either all execute or none do,” Akinyele said. “That is particularly important for use cases like delivery-versus-payment, where the asset and payment need to move atomically.”

Delivery-versus-payment links the transfer of an asset to its payment. Instead of trusting one party to send first, the ledger completes both legs together or neither of them.

Batch could also let exchanges, wallets and marketplaces attach their service charges directly to a customer transaction. A payment and the platform’s fee could be processed as one operation rather than through separate transfers.

“Some projects are already being built with Batch in mind, so activation would allow that work to move closer to production,” Akinyele shared. “We’ll share more on specific partners and launch timing as those plans are finalized.”

The amendment has support from 30 of the XRP Ledger’s 35 tracked validators, above the 28 votes required to enter its activation countdown.

That countdown began Sept. 15 at 14:06:41 UTC. Batch V1.1 is projected to activate shortly after the same time on Sept. 29, provided support remains at or above 80% for the full 14-day window. Validators can change their votes, making the date conditional.

The approaching activation follows a security failure that caused developers to withdraw the original version.

Researchers found a critical flaw in Batch V1.0’s signature-validation process in February. Under certain conditions, the code could stop checking signatures early and allow an attacker to include transactions from another account without its owner’s authorization.

Read More: XRP Ledger upgrade brings back features once pulled over critical bugs

The amendment was still being considered by validators and had not activated, meaning the vulnerable code never governed the live ledger and no funds were exposed.

Meanwhile, RippleX did more than patch the individual error before returning the feature for another vote, Akinyele said.

“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,” he said.

The replacement shipped in xrpld version 3.3.0, released Aug. 6. That implementation is the same code validators are now voting to activate, according to Akinyele.

The review included internal adversarial testing, AI-assisted analysis, a Sherlock attack contest and assessments by security firms Halborn and Common Prefix.

“The bigger point is that we established a very high bar,” Akinyele added. “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.”

The amendment will remain in its countdown through Sept. 29. If validator support drops below 80% before then, the clock stops and a new 14-day window must begin after the proposal regains the required majority.