XRP Ledger Batch upgrade delayed to Oct. 9 after validator support resets
Batch upgrade moves to Oct. 9
An XRP Ledger upgrade called Batch, which was expected to activate on Sept. 29, has been delayed by at least 10 days. Validator support briefly fell below the required level, resetting the two-week activation period. The earliest possible activation is now Oct. 9 around 14:46 UTC, provided support remains high enough.
Batch would allow users to submit up to eight transactions together. Its all-or-nothing option could allow a payment for a tokenized asset and the transfer of that asset to happen as one operation, rather than allowing one side of the trade to complete without the other.
What changed on the ledger
- The corrected upgrade, called BatchV1_1, received support from 30 of 35 trusted validators on Sept. 25.
- XRP Ledger upgrades need support from more than 80% of trusted validators for two consecutive weeks.
- When support fell below that level, the time accumulated during the earlier approval period was reset.
Why validators vote on upgrades
Validators are operators that check transactions and vote on changes to the XRP Ledger. The approval process is designed to help the network decide when an upgrade has enough support to activate. The supplied report does not explain why validator support briefly fell below the threshold.
Retry follows an earlier technical issue
Batch is already in its second attempt. Developers withdrew the original version before activation because of a critical signature-checking flaw. A corrected implementation was released in August with version 3.3.0 of the software that runs the ledger.
RippleX engineering head Ayo Akinyele previously said that projects were being built with Batch in mind. He did not name the projects or provide launch dates.
A second upgrade also slips
The separate PermissionDelegationV1_1 upgrade also lost the support required to complete its approval period. It could activate as early as Oct. 8 around 21:25 UTC, according to the report.
PermissionDelegationV1_1 would allow an account owner to authorize another account to perform approved tasks without sharing the signing keys that control the funds. A token issuer could assign payment and compliance duties to separate operational accounts.
What remains unclear
Both activation dates are earliest possible dates. They depend on validators maintaining the required level of support for the full approval period. The source also does not provide the reason for the temporary drop in support or identify the projects RippleX said were being built around Batch.
Sources
Newisty Editorial Team covers technology, cryptocurrency, digital products, online platforms, developer tools and the wider digital economy. Our content is researched from official sources, company announcements, public documentation, market data and other primary or reputable sources. Articles are reviewed and edited before publication for clarity, accuracy and useful context.
Related Posts
Senate Clarity Act Procedural Vote Could Boost Ether, Solana, and XRP
UK government gives Bank of England new duty to support stablecoin innovation
