The XRP Ledger's Batch V1.1 upgrade is now on track for a later activation date after validator support briefly slipped below the the network requires to approve an amendment. The change had been advancing toward activation after securing enough backing to trigger a two-week countdown.

If adopted, Batch would let users bundle up to eight XRP Ledger transactions into a single operation that executes atomically — either every transaction succeeds, or all of them fail. That all-or-nothing execution removes the risk of a partial sequence completing, such as a payment settling while its paired service fee fails to process. The feature could serve a range of payment and asset-transfer use cases, including delivery-versus-payment settlement. It could also enable exchanges, wallets, and marketplaces to pair customer payments with related service fees in one step.

Validator Support Resets the Countdown

Under XRP Ledger governance, an amendment needs at least 80% support from the network's trusted validator set to activate, and that level must hold throughout a 14-day activation window. The bar is deliberately demanding: momentary majorities are not enough, and once activated, amendments become part of the ledger's protocol going forward.

CoinDesk reported on Sept. 19 that Batch V1.1 had secured backing from 30 of 35 tracked validators — enough to start the countdown, which at the time pointed to a Sept. 29 activation. Support subsequently fell below the required threshold, halting the timer. Once backing recovered, the network had to begin a fresh 14-day period, pushing the earliest possible activation date to Oct. 9. That date remains conditional on validators maintaining their support, and another dip below 80% during the window would pause the timer again until backing recovers.

Security Work Preceded the Relaunch

Batch V1.1 is a rebuilt version of an earlier amendment that was withdrawn before reaching the live network after developers uncovered a critical signature-validation flaw during testing. Before returning to the validator vote, the revised implementation underwent additional security review. CoinDesk reported that developers fixed multiple issues involving signatures, authorization checks, and potential server crashes.

The renewed vote underscores how XRP Ledger's validator governance operates: even after an amendment reaches the required support level, validators can revise their votes during the activation window. For businesses planning around Batch, the delay means production timelines tied to the feature may need to wait until the network completes the renewed activation period.