XRP Ledger's Batch Upgrade Gets Delayed Again as Validator Votes Reset
Validator support briefly dipped below the network's 80% threshold, restarting the two-week activation clock and pushing the earliest launch to October 9.

The XRP Ledger's long-awaited Batch upgrade will have to wait a little longer. According to CoinDesk, validator support for the feature briefly fell below the network's required threshold, wiping out weeks of accumulated votes and restarting its two-week activation clock. If support holds this time, the earliest the upgrade can go live is October 9 — at least 10 days later than planned.
What the upgrade would do
Batch would let users submit up to eight transactions together, including all-or-nothing exchanges. That design could let a buyer pay for a tokenized asset and receive it in a single operation, reported CoinDesk — preventing either side of the trade from completing without the other. It's the kind of atomic settlement that makes a ledger attractive to institutions moving tokenized assets on-chain.
RippleX's head of engineering, Ayo Akinyele, previously told CoinDesk that projects were already being built with Batch in mind, and that Ripple planned to say more about work with asset managers once the feature went live. Activation, he said, would let that development work move closer to production — though he did not name the partners or give launch dates.
A strict voting system
The XRP Ledger has an unforgiving upgrade process: changes must keep the support of more than 80% of trusted validators for two consecutive weeks, and any dip below that line resets the clock entirely, even if the votes return quickly afterward.
The corrected upgrade, formally named BatchV1_1, regained support from 30 of 35 trusted validators on September 25, according to the XRPL amendment dashboard — kicking off a fresh two-week countdown that ends October 9 around 14:46 UTC if support holds. Batch had been counting down since September 15 before the reset.
This is already the second attempt at the feature. Developers withdrew the original version before activation after finding a critical signature-checking flaw, and the corrected implementation shipped in August with version 3.3.0 of the ledger's software.
A second upgrade slips too
Batch isn't the only upgrade that lost its qualifying support. A separate amendment, PermissionDelegationV1_1, would let account owners delegate specific tasks — for example, letting a token issuer assign payment and compliance duties to different operational accounts — without sharing the signing keys that control funds.
That upgrade lost its support on September 23 and regained it a day later, moving its earliest activation from October 5 to October 8 around 21:25 UTC, CoinDesk reported.
For a network competing to be the rails for institutional finance, two reset countdowns in a week are an awkward look — but the system's insistence on sustained supermajority support is doing exactly what it was designed to do.
Written by the BidAsk Newsroom. Based on reporting from the sources below.
Is your VPN actually protecting you?
LeakCheck runs a free VPN leak test right in your browser — real WebRTC leak detection, your public IP and location, and a clear pass/fail verdict. No signup, no cost.
Test my VPN →Free tool run by the same publisher as BidAsk. No affiliate links.


