XRP Ledger’s Batch Upgrade Slips From September 29 to…

The XRP Ledger's long-awaited Batch transaction upgrade will no longer activate on September 29 after validator support temporarily fell below the network's required threshold, resetting its two-week approval period and pushing activation to October 9 at the earliest.The amendment, formally called BatchV1_1, had maintained sufficient validator support since September 15 and was approaching activation. That countdown was reset on September 25 when enough validators temporarily withdrew their support.The reset was not simply the result of validators abandoning the upgrade. XRP Ledger community participants coordinated the vote change after developers released xrpld version 3.4.1, which introduced a new amendment called fixBatchV1_2 addressing an issue affecting Batch.The XRP Ledger Foundation describes version 3.4.1 as an emergency release addressing security-sensitive protocol issues. It said there had been no impact on mainnet or loss of user funds.Synchronizing the amendments means Batch and its accompanying fix can activate together rather than enabling the original feature before the corrective amendment.

Two-Week Countdown Starts Again

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 two-week countdown begins again when a qualifying majority returns.BatchV1_1 regained support from 30 of 35 trusted validators on September 25 at approximately 14:46 UTC, above the minimum 29 votes required with the current validator set.If support remains above 80% without interruption, the amendment can therefore activate around 14:46 UTC on October 9.October 9 is consequently not a guaranteed activation date. 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 Brings Atomic Multi-Transaction Execution

Batch represents a significant change to how complex operations can be executed on 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. Most notably, an all-or-nothing structure can require every component to succeed or cause the entire batch to fail.That capability could support delivery-versus-payment transactions involving tokenized assets. A payment and corresponding asset transfer, for example, could be executed together, preventing a situation in which 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 XRP Ledger's amendment safeguards rather than a conventional hard-fork postponement.Validators can alter their votes while an amendment remains pending, and the network automatically requires another uninterrupted two-week supermajority whenever support falls below the threshold.For users, no immediate action is required simply because the activation date moved. Node operators, however, have been explicitly advised to install xrpld 3.4.1.The next key date is now October 9, but activation remains conditional on sustained validator consensus through the full two-week window.