Ripple: Asset Managers Are Preparing for XRP Ledger’s Next Payment Push

Ripple says asset managers and other commercial projects are preparing to use Batch V1.1, an XRP Ledger feature that allows multiple connected transactions to be executed as a single operation.

The upgrade can bundle up to eight transactions into one batch. Its all-or-nothing design requires every transaction to succeed; otherwise, the entire batch is canceled. This is intended to prevent situations where one side of a linked transaction settles while the other does not.

Ayo Akinyele, RippleX’s head of engineering, said Ripple expects to disclose more information once Batch goes live, including details involving key asset managers.

One major application is delivery-versus-payment, in which an asset changes hands at the same time as the payment. By processing both transfers together, Batch removes the need for either party to send its side first.

The feature could also be used by exchanges, wallets and marketplaces to combine customer payments with service charges. Both the payment and the platform’s fee could be handled within one transaction instead of requiring separate transfers.

RippleX said commercial projects are already being developed with Batch in mind. Activation could move those initiatives closer to production, while information about specific partners and launch schedules will be shared when those plans are finalized.

The proposal has backing from 30 of the XRP Ledger’s 35 tracked validators, exceeding the 28 votes needed to begin the activation countdown.

Batch V1.1 Moves Forward After Security Redesign

The activation countdown began Sept. 15 at 14:06:41 UTC. Batch V1.1 is expected to activate shortly after 14:06:41 UTC on Sept. 29 if validator support remains at 80% or higher throughout the 14-day period.

The expected activation date could change because validators are able to alter their votes during the countdown.

The rollout follows the withdrawal of Batch V1.0 after researchers uncovered a critical flaw in its signature-validation process in February.

Under certain conditions, the vulnerability could cause signature checks to stop before validation was complete, potentially allowing an attacker to include transactions belonging to another account without authorization.

The flaw was found before the amendment went live. Since validators had not yet approved and activated the feature, the vulnerable implementation never operated on the live XRP Ledger and no funds were exposed.

RippleX subsequently carried out a wider overhaul instead of simply patching the identified issue. Developers redesigned parts of the signing and authorization system and expanded the security assessment.

The revised implementation was released with xrpld version 3.3.0 on Aug. 6. Akinyele said the code in that release is the same version now being considered for activation.

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

RippleX said the expanded review was intended to strengthen the implementation before deployment. After stopping V1.0, developers redesigned and hardened the system, increased the scope of testing and then returned the revised version to validators.

The current countdown will run through Sept. 29. If support drops below the 80% threshold before then, the process will pause. Once the proposal regains the required validator support, another 14-day countdown will be needed.