Nikolas Sargeant
TL;DR
-
The XRP Ledger’s BatchV1_1 upgrade will not activate on September 29 after validator support briefly fell below the required threshold.
-
Support returned on September 25, restarting the mandatory two-week countdown.
-
The earliest possible activation is now October 9 at about 14:46 UTC, if support holds.
-
Batch would let users submit up to eight transactions together, including trades that complete entirely or not at all.
The XRP Ledger’s planned Batch upgrade has been delayed by at least 10 days after a brief drop in validator support reset the network’s activation countdown.
BatchV1_1 regained backing from 30 of 35 trusted validators on September 25, according to the XRPL amendment dashboard.
That began a new two-week waiting period, making October 9 at approximately 14:46 UTC its earliest possible activation time. The date depends on support remaining above the required threshold.
Batch Could Link Payments and Asset Transfers
Batch would allow users to submit up to eight transactions in one operation. An all-or-nothing option could help with tokenized asset trades: a buyer’s payment and the asset transfer would either both succeed or both fail.
Ayo Akinyele, RippleX’s head of engineering, previously told CoinDesk that projects were already being developed with Batch in mind. He said Ripple would share more about its work with asset managers after the feature went live, but did not name partners or provide launch dates.
XRPL amendments must maintain support from more than 80% of trusted validators for two consecutive weeks before activation. If support drops below that level, the countdown starts again when sufficient backing returns.
Batch had been on track for activation after its countdown began on September 15. The current version is the second attempt to introduce the feature. Developers withdrew an earlier version before activation after finding a critical flaw in its signature checks, then released the corrected implementation with XRPL software version 3.3.0 in August.
Delegated Permissions Upgrade Also Slips
A separate amendment, PermissionDelegationV1_1, has also been delayed after losing qualifying validator support on September 23. It regained support the following day, shifting its earliest possible activation from October 5 to October 8 at about 21:25 UTC.
That feature would let an account owner authorize another account to perform specified actions without handing over the keys that control its funds. A business, for example, could assign payment and compliance tasks to separate operational accounts.
