The XRP Ledger is navigating a fresh upgrade timeline after validator support for its Batch amendment briefly dipped below the required threshold, resetting the network's two-week activation countdown. According to the XRPL amendment process, an amendment must maintain support from more than 80% of trusted validators continuously for two weeks before it can go live.
The BatchV1_1 upgrade will no longer activate on Sept. 29 as previously expected. Support had fallen below 80%, but on Sept. 25 it regained backing from 30 of 35 trusted validators. If that support holds, the earliest activation is now around Oct. 9 at 14:46 UTC. Even a short dip below the threshold wipes out the accumulated countdown, and when support returns, the full two-week period begins again.
In parallel, developers are urging node operators to upgrade to xrpld 3.4.1. The Sept. 25 release fixes a minor issue with the Batch feature and adds stability improvements. Developers said the issue did not affect the mainnet or cause any loss of user funds. The update also introduces the fixBatchV1_2 amendment, which is entering its activation period alongside the Batch amendment. XRP Ledger Operations plans to publish a technical report after activation, with full technical details still undisclosed.
The Batch feature would allow users and applications to package between two and eight transactions into one batch. The specification supports four execution modes: All or Nothing, Only One, Until Failure and Independent. The most notable is All or Nothing, enabling an operation where every step succeeds together or the entire batch fails. Developers could transfer a tokenized asset and payment in the same operation, reducing the risk that only one side completes. XRPL documentation also highlights examples involving NFT minting, offers, platform fees and multi-account swaps.
The upgrade also carries an important security history. BatchV1_1 replaces an earlier Batch implementation that developers withdrew before activation after discovering a critical authorization flaw. The corrected version was incorporated into the later xrpld release and entered the amendment process separately.
