XRP Ledger Batch Upgrade Activation Moves to October 9
XRP Ledger validators have reset the activation timer for the Batch amendment, moving its projected launch from September 29 to October 9 to align with a software fix included in the new xrpld 3.4.1 release.
The Batch amendment is designed to let users group multiple transactions for processing together. Validators had previously reached the required voting threshold, starting the two-week activation period, but the subsequent release of a fix for the feature prompted validators to reset the schedule.
According to XRP Ledger contributor Hussein Zangana, known as Vet, he coordinated with Ripple and community validators to temporarily change enough Batch votes from yes to no. The amendment then fell below the required support threshold, restarting its activation clock before validators could restore their support.
XRP Ledger Batch Amendment Reset for New Fix
XRP Ledger amendments require support from more than 80% of trusted validators for two consecutive weeks before they can activate.
If support drops below that level during the voting period, the activation timer resets. Validators can subsequently restore their support, beginning a new activation period once the required threshold is maintained.
In the case of Batch, the reset was intended to bring its activation schedule into line with the fixBatchV1_2 amendment included in xrpld 3.4.1.
The change means the planned Batch activation and its associated fix can proceed on the same timetable rather than activating under separate schedules.
xrpld 3.4.1 Includes Batch Security Fix
The xrpld 3.4.1 release introduces fixBatchV1_2 with its default validator vote set to yes.
According to the release notes, the amendment prevents Batch inner transactions from using an incorrect wrapper. The software release also contains additional changes addressing security and network stability issues.
Developers have characterized version 3.4.1 as an emergency release addressing security-sensitive protocol issues. The source code for the specific fix has not yet been published, while developers plan to provide a retrospective explaining the issue at a later stage.
As a result, the available release information provides only limited detail about the underlying vulnerability or technical problem addressed by fixBatchV1_2.
Validators Urged to Upgrade Before October 9
The XRP Ledger Foundation has urged server operators to install xrpld 3.4.1 before fixBatchV1_2 reaches final approval.
Servers that continue running older software could lose synchronization with the XRP Ledger if the amendment receives the required validator support and activates on October 9.
The projected date remains subject to the validator voting process. Batch must maintain support above the required threshold throughout the activation period for October 9 to remain valid.
Permission Delegation Has Also Seen a Voting Reset
The Batch amendment is not the only XRP Ledger upgrade whose activation schedule has recently changed.
The separate PermissionDelegationV1_1 amendment also briefly fell below the support level required to keep its activation timer running. Its projected activation date subsequently moved to October 8, one day before the projected Batch and fixBatchV1_2 activation.
The resets leave the two upgrades on closely aligned schedules while validators and server operators prepare for the associated software changes.
Writer: Marcus RenfieldCrypto Market Analyst & Onchain WriterMarcus Renfield covers cryptocurrency markets with a focus on onchain data, Bitcoin price action, and emerging market narratives. His writing examines how capital flows, network activity, and broader market structure influence short- and medium-term trends.He aims to provide clear, data-informed analysis for readers seeking a deeper understanding of crypto market dynamics.