Ripple says asset managers are preparing for XRP Ledger’s next payments upgrade
Ripple says commercial teams including asset managers are preparing to use Batch V1.1, an XRP Ledger upgrade that can group up to eight transactions so they either all settle or all fail. The amendment cleared an extensive redesign and security review after a critical signature-validation flaw was discovered in an earlier draft.

Why It Matters
Atomic grouping of payments and asset transfers could enable delivery-versus-payment workflows and let platforms process fees alongside customer payments, changing how exchanges, wallets and marketplaces build payment rails on the XRP Ledger.
Key Facts
- Feature name: Batch V1.1
- Maximum transactions per batch: Up to 8 transactions
- All-or-nothing mode: Yes — either all transactions execute or none do
- Use cases cited: Delivery-versus-payment; attaching service fees to customer payments
- Validator support at time of report: 30 of 35 tracked validators (above the 28 votes required to enter activation countdown)
RippleX says developers and some asset managers are building commercial projects that will use Batch V1.1, an XRP Ledger amendment that groups up to eight transactions into a single operation so they either all succeed or the entire group is rolled back. RippleX engineering head Ayo Akinyele told CoinDesk the feature is especially useful for delivery-versus-payment flows, where asset transfers and matching payments must occur atomically. Batch V1.1 could also let exchanges, wallets and marketplace operators attach platform fees directly to a customer’s payment so the fee and the payment are processed as one operation rather than as separate transfers. RippleX said several projects are being developed with Batch in mind and that activation would allow those builds to move closer to production. The amendment entered a 14-day activation countdown on Sept. 15 at 14:06:41 UTC. If support among validators remains at or above 80% for the full window, Batch V1.1 is projected to activate shortly after the same time on Sept. 29; validators can change their votes during the countdown and a drop below 80% would pause the clock and require a new window after majority is regained. At the time of reporting, 30 of 35 tracked validators had voted in favor — above the 28 votes needed to start the countdown. Batch V1.1 is a rebuilt version of an earlier proposal that was withdrawn after researchers identified a critical flaw in Batch V1.0’s signature-validation logic in February. That vulnerability could have let an attacker include transactions from another account under certain conditions. RippleX said the vulnerable code never activated on the live ledger because the amendment had not reached activation. The team used the issue to redesign parts of the signing and authorization model, expanded the security review, and released the replacement implementation in xrpld version 3.3.0 on Aug. 6. The review process included internal adversarial testing, AI-assisted analysis, a Sherlock attack contest, and assessments by security firms Halborn and Common Prefix, according to RippleX.
Keep Reading

Kalshi joins Coinbase with filing for US stock perpetual futures

REX launches 2x leveraged ETF tied to Bitcoin treasury firm Strive

Grayscale Is Making Its Red-Hot Zcash ETF More Affordable

Bitcoin's Sharpest Rally in Two Years Ran Almost Entirely on Short Liquidations
Original source: CoinDesk