XRP Ledger Sets 29 September for Its Batch Payments Upgrade

The XRP Ledger's Batch amendment is on a clock. A fourteen-day countdown began on 15 September at 14:06:41 UTC, which puts activation at 29 September at the same minute if validator support holds above 80% for every one of those days. Batch lets up to eight transactions from different accounts settle in a single ledger close, all of them or none of them. Ripple said on Friday that asset managers are preparing to use it. This is the rebuilt version of a feature pulled from the network in February over a signature flaw.

Three counts of the same Tuesday

How many validators stood behind the amendment when the clock started depends on which account is read. CoinDesk, filing at 13:39 UTC on Friday, and Phemex, filing six minutes later, both give 30 of 35 tracked validators against a threshold of 28. FinanceFeeds gives the same 30, dated to 15 September. A KuCoin flash of 16 September puts support at 82.86%, which is 29 of the 35. crypto.news and Bitcoin Magazine, both writing from Tuesday's figures, and Crowdfund Insider on the 16th, all give 27 of 35, one vote short of the bar. Those are three readings of one day, and no account acknowledges another. This desk published the 27-vote count on 15 September. Support stood at 24 of 35 a week earlier.

Settlement that cannot half-happen

An amendment on the XRP Ledger is a change to the consensus rules that ships dormant in the server software and waits for a validator vote. Batch is the one application developers have waited longest for. Without it, a swap between two parties has to be assembled out of separate transactions, with someone standing behind them to make sure both legs land.

"Batch allows multiple transactions to be grouped together so they either all execute or none do," Ayo Akinyele, head of engineering at RippleX, said.

Three accounts carry that sentence identically. The two uses Ripple names are delivery-versus-payment, where an asset transfer and its payment settle together or fail together, and platform fees bundled into a customer payment. Crowdfund Insider is alone in this sweep in setting out four execution modes, called all-or-nothing, single-success, until-failure and independent. Take that detail as one account's.

Ten bugs, or eleven

RippleX published its own account of the rebuild on 14 September, and it does not match the coverage of it. The post by engineer Mayukha Vadari lists the root-cause fix plus ten further bugs: a validation bypass that crashed nodes, a path-size bypass, signature-verification bypasses in release builds, and a signer-ordering flaw that let authorization checks be manipulated. crypto.news and Bitcoin Magazine both say eleven issues were resolved. The primary source and the secondary accounts differ by one, and neither explains the other. Common Prefix rated one issue critical, covering the reuse of signed permissions for transactions the signer never authorized.

The February flaw, in RippleX's words

The original bug surfaced on 19 February, found by security researchers and Cantina AI. Vadari's post describes it plainly: the signature check returned success and stopped when it met a signer whose account did not yet exist on the ledger, skipping every signer after that one. The amendment was still in voting at the time, so no user funds were exposed. Validators were told within hours to vote no, and an emergency release marked both amendments unsupported. The replacement shipped inside xrpld 3.3.0 on 6 August. The review that followed ran to four senior engineers, a Sherlock attackathon, audits by Halborn and Common Prefix, and regression testing on devnet and testnet.

Still no customer named

Ripple has not named a single commercial partner. Akinyele told CoinDesk that some projects are already being built with Batch in mind, and the company says it will publish partners and production timelines once the feature is live. What happens between now and the 29th is a validator decision and nobody else's. If support slips under 80% at any point in the fourteen days, the countdown resets and the date goes with it.