Ripple says asset managers and other commercial projects are getting ready for Batch V1.1, an XRP Ledger upgrade that allows related transactions to be processed together. The feature is approaching activation after developers completed an extensive security review of the redesigned version.

Batch V1.1 can combine up to eight transactions into one operation. Its atomic, all-or-nothing structure means the entire group is executed only if every transaction succeeds. If one fails, the complete batch is canceled.

The design is intended to support use cases such as delivery-versus-payment, where an asset and its corresponding payment need to settle simultaneously.

Ayo Akinyele, head of engineering at RippleX, said Ripple plans to provide additional information after the feature goes live, including details about its work with major asset managers.

Under delivery-versus-payment, the transfer of an asset is directly tied to the payment for it. Batch allows both sides to be processed together, removing the need for one party to transfer first and rely on the other side to complete its obligation afterward.

The upgrade could also help exchanges, wallets and marketplaces combine customer payments with their service fees. Rather than sending separate transactions, both the payment and associated fee could be included in a single batch.

RippleX said several projects are already being developed with the feature in mind. Activation would allow those initiatives to progress toward production, while details on individual partners and launch plans will be released as they are finalized.

Batch V1.1 has received approval from 30 of the 35 tracked XRP Ledger validators. The figure is above the 28-validator threshold required to start the activation countdown.

Batch Upgrade Advances After Security Review

The 14-day activation countdown began Sept. 15 at 14:06:41 UTC. If support remains at or above 80% for the full period, Batch V1.1 is expected to activate shortly after the same time on Sept. 29.

The activation date is conditional because validators can change their votes during the countdown.

The new implementation follows the withdrawal of Batch V1.0 after researchers discovered a serious vulnerability in its signature-validation system in February.

In certain circumstances, the flaw could cause signature checks to end prematurely, potentially allowing an attacker to insert transactions belonging to another account without authorization.

The vulnerable version had not been activated when the issue was found. Because it was still awaiting validator approval, the code never operated on the live XRP Ledger and no user funds were exposed.

Rather than making only a targeted fix, RippleX conducted a broader redesign of the feature. Developers reworked elements of the signing and authorization system and significantly expanded the security review.

The updated code was released as part of xrpld 3.3.0 on Aug. 6. Akinyele said this is the same implementation currently being considered by validators.

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

RippleX said the expanded process was designed to raise the security standard before the feature could go live. After identifying the V1.0 flaw, developers stopped the rollout, strengthened the implementation and subjected it to additional testing before putting the revised version back to a validator vote.

The activation countdown will continue through Sept. 29. If validator support falls below 80% during that period, the countdown will stop, and a new 14-day window will need to begin once the proposal regains the required support.