The XRP Ledger's BatchV1_1 upgrade now targets Oct. 9 activation—a minimum 10-day slip from the original Sept. 29 date after network validator support briefly fell below the required 80 percent threshold, automatically resetting the two-week countdown.
XRPL upgrades require sustained backing from more than 80 percent of trusted validators for two consecutive weeks. Any dip below that level wipes the timer, forcing a fresh two-week clock regardless of how fast votes return.
The Batch feature lets users submit up to eight transactions at once with an all-or-nothing guarantee: a tokenized asset purchase and its paired payment either both settle or neither does. No partial fills.
On-chain data from the XRPL amendment dashboard shows BatchV1_1 reclaimed support from 30 of 35 trusted validators on Sept. 25, hitting the threshold and kicking off a fresh countdown pointing to earliest activation around 14:46 UTC on Oct. 9.
Ayo Akinyele, RippleX's head of engineering, said various projects were already integrating Batch into development pipelines and that activation would let them move closer to production. Ripple plans to share details about asset manager collaborations once Batch goes live.
This is the second run at Batch. Developers pulled the initial version after finding a critical signature-checking flaw. The corrected BatchV1_1 shipped in August as part of ledger software version 3.3.0.
PermissionDelegationV1_1, a separate upgrade enabling account owners to delegate specific tasks without sharing signing keys, also hit a snag. A token issuer can now assign distinct payment processing and compliance duties to separate operational accounts, cutting operational risk and streamlining workflows.
PermissionDelegationV1_1 lost qualifying validator support on Sept. 23 and regained it one day later. That one-day lapse pushed its earliest activation from Oct. 5 to Oct. 8, with expected activation around 21:25 UTC.
