XRP Ledger Batch upgrade slips to Oct. 9 after validator support reset
By Node Zero
September 26, 2026
The XRP Ledger’s Batch upgrade—expected to activate September 29—has slipped by at least 10 days after validator support briefly fell below the network’s 80% threshold, CoinDesk reported early Saturday. The corrected amendment BatchV1_1 regained support from 30 of 35 trusted validators on September 25, restarting the two-week countdown and putting earliest activation at about 14:46 UTC on October 9 if support holds. Attribute the reset, headcount, and clock to CoinDesk plus the XRPL amendment dashboard—do not invent that Batch already shipped on mainnet.
Why Dev Pulse desks flag a governance clock reset. XRPL upgrades must keep more than 80% of trusted validators for two consecutive weeks. Losing that support wipes accumulated time even if votes return shortly afterward. Batch had been counting down since September 15. This is already a second attempt: developers withdrew the original version over a critical signature-checking flaw before activation, and the corrected implementation shipped in August with ledger software version 3.3.0.
What Batch is supposed to unlock. The feature would let users submit up to eight transactions together. Its all-or-nothing option could let a buyer pay for a tokenized asset and receive it in one operation, preventing either side of the trade from completing alone—useful color for NFT and RWA settlement rails once live. RippleX head of engineering Ayo Akinyele previously told CoinDesk that projects were being built around Batch and that Ripple would share more about work with asset managers once the feature went live; he did not name partners or give launch dates. Stick to that attribution.
Companion delay: PermissionDelegationV1_1. A separate upgrade that lets account owners authorize another account for approved actions without sharing signing keys also lost qualifying support on September 23 and regained it a day later, moving its earliest activation from October 5 to about 21:25 UTC on October 8. A token issuer could assign payment and compliance duties to different operational accounts under that design—adjacent protocol color, not this tick’s primary headline.
Operational read for desks watching amendment dashboards. A brief dip below 80% is enough to erase nearly two weeks of countdown progress even when the same validators rejoin within a day. CoinDesk’s wrap puts the Batch regain at 30 of 35 trusted validators on September 25—above the bar again, but on a fresh clock. Until that two-week window completes without another dip, Sept. 29 is off the table and October 9 is only the earliest possible, not a guaranteed ship date.
Rejected near-echos for this tick. Solana Alpenglow on both public testnets with a 150 ms finality target is LN 9757. Bitget’s phased withdrawal calendar is LN 9755. OpenSea’s 3,000+ theft-linked NFT sell block is LN 9753. Bitcoin spot ETF’s $134.5M Sep 25 / seven-day ~$2.978B streak is a usable unused alternate parked for a later Ape Index slot. Phygital 59 still lacked a clean last-six-hour primary.
Why Dev & Protocol Pulse 57 plus Latest News 16 plus Editor’s Pick 13 (Sep 26 OC EP moves to 2/5). A documented BatchV1_1 support reset to earliest October 9 is unused protocol news inside the last-six-hour window. Author is Node Zero for desk 57. Publicize stays off.
What not to invent: that Batch activated on September 29, named asset-manager partners, that PermissionDelegation already live, or a guaranteed October 9 flip if support later dips again. Stick to CoinDesk / XRPL dashboard attributions for the 30/35 regain, 14:46 UTC October 9 earliest Batch clock, and October 8 PermissionDelegation earliest.
Bottom line: XRPL BatchV1_1’s activation clock restarted after a brief support dip—earliest go-live about October 9, 14:46 UTC if the 80% threshold holds. Unused Dev Pulse news for Sep 26 OC.
Disclaimer: This article is provided for informational and educational purposes only. It does not constitute financial, investment, legal, or trading advice. The NFT market is highly volatile, and past performance is not indicative of future results. Readers should conduct their own research and consult qualified professionals before making any decisions related to digital assets. The cover image for this article may have been created using artificial intelligence (AI).
