Ripple says asset managers and other commercial projects are preparing to use Batch V1.1, an XRP Ledger upgrade that groups up to eight transactions so they all settle or all fail together. The amendment has cleared the validator threshold needed to enter its activation countdown and is projected to go live shortly after Sept. 29, following a redesign prompted by a critical flaw found in the original version.
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 nears activation after 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 every transaction in the group succeeds or the entire batch is canceled, avoiding cases where one side of a deal settles while the other fails.
According to CoinDesk: "the asset and payment need to move atomically," Ayo Akinyele, head of engineering at RippleX, said. Delivery-versus-payment links the transfer of an asset to its payment, so 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 service charges directly to a customer transaction, processing a payment and the platform's fee as one operation rather than through separate transfers.
Commercial projects already in motion
Akinyele said some projects are already being built with Batch in mind, so activation would let that work move closer to production. Ripple plans to share more on specific partners and launch timing once 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.
Feature arrives after earlier flaws fixed
That countdown began Sept. 15 at 14:06:41 UTC, and Batch V1.1 is projected to activate shortly after the same time on Sept. 29, provided support stays at or above 80% for the full 14-day window. Validators can still change their votes, so the date remains 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. However, 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.
RippleX did more than patch the individual error before returning the feature for another vote. The team redesigned parts of the signing and authorization model and expanded the security review, which included internal adversarial testing, AI-assisted analysis, a Sherlock attack contest and assessments by security firms Halborn and Common Prefix. The replacement shipped in xrpld version 3.3.0, released Aug. 6, and that implementation is the same code validators are now voting to activate, according to Akinyele.
Source: CoinDesk
Trading involves risk.
Risk Disclaimer
