XRP Ledger’s Batch upgrade slips to Oct. 9 after validator support resets
The XRP Ledger’s Batch upgrade was postponed after validator support briefly dropped below the network’s required threshold, restarting its two-week activation countdown and pushing the earliest possible activation to Oct. 9 if backing remains. A separate PermissionDelegation upgrade also lost and then regained support, moving its earliest activation to Oct. 8.

Why It Matters
Amendments on the XRPL must maintain over 80% support from trusted validators for two consecutive weeks to activate, so short interruptions can delay features that developers and institutions are preparing to use — including Batch’s all-or-nothing grouped transactions and permission delegation for operational roles. These upgrades affect how payments, token transfers and delegated account operations could be executed on the ledger once live.
Key Facts
- Feature delayed: Batch (BatchV1_1) earliest new activation: Oct. 9, 14:46 UTC (if support holds)
- Validator support regained: BatchV1_1 had support from 30 of 35 trusted validators on Sept. 25
- Activation rule: XRPL amendments require support from more than 80% of trusted validators for two consecutive weeks
- Original schedule: Batch had been counting down since Sept. 15 and was expected to activate Sept. 29 before the reset
- Previous withdrawal: The original Batch implementation was withdrawn earlier due to a signature-checking flaw; corrected implementation shipped in August with XRPL software v3.3.0.
An XRP Ledger upgrade known as Batch has been pushed back after validator support momentarily fell below the level required to finalize activation, restarting the two-week countdown. The corrected amendment, BatchV1_1, regained backing from 30 of 35 trusted validators on Sept. 25; that reset sets its earliest possible activation at Oct. 9 around 14:46 UTC, provided support remains above the threshold for the subsequent two weeks. Batch would let users submit up to eight transactions together and includes an all-or-nothing option intended to ensure paired operations—such as a payment and the transfer of a tokenized asset—either both complete or neither does. Developers and some projects were already building around Batch, and RippleX engineers have said activation would move that work closer to production. This is the second attempt to introduce Batch after an earlier version was withdrawn before activation due to a critical signature-checking issue. The corrected implementation was included in the XRPL client release v3.3.0 in August. A separate amendment, PermissionDelegationV1_1, which would allow account owners to delegate specific tasks to other accounts without sharing signing keys, also lost qualifying support briefly. That amendment lost support on Sept. 23 and regained it on Sept. 24, moving its earliest activation from Oct. 5 to Oct. 8 around 21:25 UTC. XRPL validators are the operators that validate transactions and vote on such network changes, and any interruption in their consensus resets an amendment’s activation timer.
Keep Reading
Legacy Magic Eden Approvals Exploited as White Hats Rescue NFTs
AlphaFi Winds Down After Oracle Error, With Sui Foundation Support

U.S. SEC's steadiest crypto advocate, Hester Peirce, to depart next week

Bitcoin could soon get Zcash-style 'shielded' privacy without changing its rules
Original source: CoinDesk