According to Ripple, the next XRP Ledger payments upgrade has asset managers already preparing for it. The upgrade is a rebuilt version of a feature that previously failed. Called Batch V1.1, it allows up to eight transactions to settle together as one atomic operation, which means they either all succeed or all fail, with no middle ground.
Researchers discovered a serious flaw in the signature-validation process, which led to the withdrawal of the feature. Ripple then rebuilt it from the ground up, and the updated version is now being prepared for activation. Validator support currently stands at 30 out of 35 tracked nodes, surpassing the 28 votes required to begin the countdown.
The Atomic Operation
In Batch V1.1, a set of up to eight XRP Ledger transactions can be bundled together into one operation. The all-or-nothing approach ensures that either every transaction completes successfully, or none of them do at all. This design prevents a situation where one part of an arrangement settles properly while the other side falls through.
This feature handles delivery-versus-payment transactions, where the asset and the payment travel together: the ledger finishes both parts simultaneously or leaves both undone. Ripple claims exchanges, wallets and marketplaces can also employ it for processing service fees alongside customer payments.
Once the feature goes live, RippleX is planning to share more information, including its work with key asset managers. The company has said that some projects are already under construction with Batch in mind, which means activation would help that work get closer to production.
The Security Review That Followed
A security failure led to developers withdrawing the original version, which set the stage for the redesign. Researchers uncovered a serious 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 system.
Before it could take effect, the amendment remained under review by validators, so the vulnerable code never governed the live ledger and no funds were exposed. According to Akinyele, RippleX went beyond merely fixing the individual error.
“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 arrived in xrpld version 3.3.0, which came out Aug. 6. The code being voted on by validators matches what was already deployed in that release, according to Akinyele.
What the Review Involved
Security firms Halborn and Common Prefix conducted external reviews alongside the work done internally. Internal adversarial testing, AI-assisted analysis, and a Sherlock attack contest all made up part of the security review.
“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 Countdown and Its Conditions
A countdown started on Sept. 15 at 14:06:41 UTC. Batch V1.1 is expected to come online soon after the same moment on Sept. 29, assuming support stays at or over 80% for the entire 14-day span. Since validators can adjust their votes, the timing is not fixed.
The countdown to the amendment’s deadline will stop if the number of validators falls below 80% before Sept. 29. Once the proposal regains the required majority, a new 14-day window must begin. The amendment will keep its countdown through Sept. 29.
Projects Are Already Built Around It
Akinyele said some commercial projects are already under construction with Batch in mind, and activation would bring that work closer to production.
“We’ll share more on specific partners and launch timing as those plans are finalized,” Akinyele shared.
The upgrade is now in its final stretch toward activation.
What Comes After Activation
Ripple has yet to announce specific partners or a launch date for the feature beyond what Akinyele described. Once it goes live, the company will share more information, including its work with key asset managers.
The update could enable delivery-versus-payment deals, letting exchanges, wallets and marketplaces handle service charges alongside customer payments at the same time. These applications rest on the atomic behavior staying intact.
The Road From Failure to Deployment
The journey from weakness to deployment bears remarking upon. The initial edition was withdrawn due to a security failure. A redesign came after, and the revised edition is now advancing toward activation with 30 of 35 tracked validators behind it.
A thorough review led to a rebuilt feature, and it now meets a higher standard than what came before it.
Key Facts Box
- Feature: Batch V1.1
- Transactions per batch: Up to eight
- Validator support: 30 out of 35 tracked nodes, above the 28 votes required
- Countdown began: Sept. 15 at 14:06:41 UTC
- Projected activation: Shortly after Sept. 29, if support stays at or above 80% for the full 14-day window
- Redesign shipped: xrpld version 3.3.0, released Aug. 6
- Security review included: Internal adversarial testing, AI-assisted analysis, Sherlock attack contest, assessments by Halborn and Common Prefix
Our View of the Upgrade
Ripple spotted a serious problem with V1.0, halted it, rebuilt the design to make it stronger, and now V1.1 is being presented to validators again.
A major overhaul has been carried out, and the feature is now nearing completion before it becomes operational.
Whether the upgrade succeeds hinges on whether the atomic behavior actually works when put into use. Ripple has said it will provide further details after the feature goes live.
Source material: “Ripple says asset managers are preparing for XRP Ledger’s next payments upgrade,” CoinDesk.
Get the Notebook.
The day's best stories and every fresh verdict, in plain English, in your inbox by seven. One email a day, no more.