The XRP Ledger's BatchV1_1 upgrade will not activate on its planned Sept. 29 date. The feature, intended to enable bundled transactions, now targets an earliest activation of Oct. 9 around 14:46 UTC—a 10-day slip.
Validator support for BatchV1_1 briefly fell below the critical 80 percent threshold required for XRPL amendments to proceed. Any lapse in support, even temporary, automatically resets the two-week activation countdown.
XRPL upgrades mandate that more than 80 percent of trusted validators must consistently support a proposed amendment for two consecutive weeks. On Sept. 25, the XRPL amendment dashboard showed BatchV1_1 regained support from 30 of 35 trusted validators, marking the start of a fresh two-week countdown.
BatchV1_1 allows users to submit up to eight transactions as a single unit. Its all-or-nothing functionality prevents partial completion in operations like tokenized asset purchases, ensuring the buyer receives the asset only if payment is successful. This is the second attempt to introduce the Batch feature. Developers had previously withdrawn the original version after discovering a critical signature-checking flaw. The corrected BatchV1_1 implementation shipped in August with version 3.3.0 of the ledger's software.
Ayo Akinyele, RippleX's head of engineering, said projects are already building with Batch functionality in mind. "Some projects are already being built with Batch in mind, so activation would allow that work to move closer to production," Akinyele said.
A separate XRPL upgrade, PermissionDelegationV1_1, also experienced a similar delay. This feature enables account owners to delegate specific tasks without sharing their primary signing keys, allowing businesses to assign distinct payment or compliance duties to operational accounts. PermissionDelegationV1_1 lost its qualifying validator support on Sept. 23, then regained it a day later, shifting its earliest activation from Oct. 5 to Oct. 8 around 21:25 UTC.
