The XRP Ledger's highly anticipated Batch transaction upgrade has been postponed from its original September 29 activation date after validator support temporarily dipped below the network's required 80% threshold, resetting the two-week approval period. The earliest possible activation date is now October 9, though that timeline remains conditional on sustained validator consensus.
The amendment, formally designated BatchV1_1, had maintained sufficient validator support since September 15 and was approaching its activation countdown. However, on September 25, the countdown was reset when enough validators temporarily withdrew their support. This reset was not a sign of validators abandoning the upgrade; rather, it was a coordinated vote change by XRP Ledger community participants following the release of xrpld version 3.4.1, which introduced a new amendment called fixBatchV1_2 to address a security-sensitive issue affecting Batch.
The XRP Ledger Foundation described version 3.4.1 as an emergency release addressing security-sensitive protocol issues, while confirming there had been no impact on mainnet or loss of user funds. By synchronizing the two amendments, Batch and its accompanying fix can activate together rather than enabling the original feature before the corrective measure.
XRP Ledger amendments must maintain support from more than 80% of trusted validators for two consecutive weeks before becoming permanently enabled. If support falls below that threshold at any point, the accumulated approval period is erased and the countdown begins anew. BatchV1_1 regained support from 30 of 35 trusted validators on September 25 at approximately 14:46 UTC, above the minimum 29 votes required. If support holds, activation could occur around 14:46 UTC on October 9. However, October 9 is not guaranteed—another drop below the threshold would reset the clock again.
The accompanying fixBatchV1_2 amendment has also reached supermajority support and is expected to activate on October 9. XRPL has urged server operators to upgrade to version 3.4.1 before then, warning that incompatible servers could become amendment-blocked and stop maintaining synchronization with the network. A separate amendment, PermissionDelegationV1_1, also had its activation period reset and could now activate as early as October 8 if validator support remains sufficient.
Batch represents a significant evolution for how complex operations are executed on the XRP Ledger. The feature allows users to combine up to eight inner transactions into a single Batch transaction, including transactions originating from multiple accounts. Different execution modes determine how those transactions behave, with the most notable being an all-or-nothing structure that requires every component to succeed or the entire batch to fail. This capability could support delivery-versus-payment transactions involving tokenized assets, where a payment and corresponding asset transfer are executed together, preventing scenarios where one side completes while the other fails.
The current BatchV1_1 implementation is itself a revised version of an earlier Batch amendment that was withdrawn after developers identified a critical signature-validation issue before activation. The corrected implementation subsequently shipped with xrpld 3.3.0. The latest delay therefore reflects the XRP Ledger's amendment safeguards working as designed, rather than a conventional hard-fork postponement. For users, no immediate action is required; node operators, however, have been explicitly advised to install xrpld 3.4.1. The next key date is now October 9, with activation remaining conditional on sustained validator consensus through the full two-week window.
