Ripple says asset managers and other commercial initiatives are preparing for the activation of Batch V1.1, a new XRP Ledger feature designed to execute multiple connected transactions as one atomic operation.
The upgrade can group as many as eight transactions into a single batch. Under its all-or-nothing model, every transaction must succeed for the batch to complete. If one transaction fails, the entire group is canceled, preventing mismatches between linked transfers.
Ayo Akinyele, head of engineering at RippleX, said Ripple expects to share more information about the feature after activation, including details involving major asset managers.
Batch is particularly relevant to delivery-versus-payment applications, where an asset transfer and its corresponding payment need to occur together. Instead of relying on one party to complete its transfer before the other, both sides can be processed atomically through the ledger.
The same functionality could benefit exchanges, wallets and marketplaces by allowing customer payments and platform fees to be combined into a single transaction. This would eliminate the need to process the two transfers separately.
RippleX said some commercial projects are already being developed around Batch. Once the feature becomes active, those projects could move toward production, with further details about partners and launch schedules expected as plans are finalized.
The amendment currently has backing from 30 of the XRP Ledger’s 35 tracked validators. That exceeds the 28-validator threshold required to begin the activation process.
New Version Replaces Vulnerable Batch V1.0
The activation countdown started Sept. 15 at 14:06:41 UTC. Batch V1.1 is expected to go live shortly after that time on Sept. 29 if validator support remains at or above 80% throughout the 14-day countdown.
The date remains conditional because validators can change their votes during the activation period.
Batch V1.1 follows the withdrawal of the previous version after researchers identified a critical security flaw in Batch V1.0 in February.
The vulnerability affected the signature-validation process and, under certain circumstances, could cause verification to stop prematurely. That could potentially allow unauthorized transactions from another account to be included in a batch.
The issue was discovered before the amendment had been activated. Since validators were still considering the proposal, the vulnerable code never became part of the live XRP Ledger and no funds were exposed.
RippleX then undertook a broader review of the feature instead of limiting the response to a single code fix. The team redesigned portions of the signing and authorization system and expanded the scope of its security testing.
The revised implementation was included in xrpld 3.3.0, released Aug. 6. According to Akinyele, the implementation in that release is the version now being considered by validators.
The security process included internal adversarial testing, AI-assisted analysis, a Sherlock attack contest, and reviews by Halborn and Common Prefix.
RippleX said the revised process was intended to significantly strengthen the feature before activation. Developers identified the V1.0 problem before launch, halted the rollout, redesigned the affected components, expanded the security assessment and then returned the updated version to validators.
The Batch V1.1 proposal will remain in its current countdown until Sept. 29. Should validator support fall below 80%, the countdown will pause. A new 14-day period would then be required after the proposal regains the necessary level of support.
