XRP Ledger’s Batch V1.1 upgrade now faces a later activation date after validator support briefly fell below the network’s required threshold. The change had been moving toward activation after gaining enough backing to start a two-week countdown.
The Batch feature would allow users to group as many as eight XRP Ledger transactions into a single operation. Transactions could then execute atomically, meaning they either all succeed or all fail.
The feature could support several payment and asset-transfer applications, including delivery-versus-payment transactions. It could also allow exchanges, wallets and marketplaces to combine customer payments with related service fees.
Validator Support Resets the Clock
XRP Ledger requires at least 80% support from its trusted validator set for an amendment to activate. That support must remain at the required level throughout a 14-day activation period.
CoinDesk reported on Sept. 19 that Batch V1.1 had support from 30 of 35 tracked validators. That level was enough to begin the activation countdown, which initially pointed to Sept. 29.
However, validator support later dropped below the required threshold. That interruption stopped the countdown and forced the network to begin a fresh 14-day period after support recovered.
The reset now puts the earliest potential activation date at Oct. 9, although the date remains conditional on continued validator backing.
Security Review Preceded the Relaunch
Batch V1.1 represents a redesigned version of an earlier amendment that was withdrawn before reaching the live network. Developers discovered a critical signature-validation flaw in the original version during testing.
The revised implementation underwent additional security work before returning to the validator voting process. CoinDesk reported that developers addressed multiple issues involving signatures, authorization checks and potential server crashes.
The renewed vote highlights the role of XRP Ledger’s validator governance process. Even after an amendment reaches the required support level, validators can change their votes during the activation window.
For businesses considering Batch, the delay means production plans tied to the feature may need to wait until the network completes the renewed activation period.
