Developers of the XRP Ledger released xrpld 3.4.1 on September 25 as an emergency update to address what they described as “security-sensitive issues.” According to the official release notes, the new fixBatchV1_2 amendment has already achieved validator supermajority support and is expected to activate on October 9 if that support remains above the required threshold.
The rollout matters for node operators well beyond a routine upgrade. Nodes that have not upgraded to version 3.4.1 by activation could become amendment blocked, meaning they would no longer stay synchronized with the network.
The security amendment is tied to BatchV1_1, XRPL’s replacement for an earlier Batch implementation that was abandoned after developers discovered a critical bug. Batch transactions allow several operations to be grouped together, with structures where every transaction succeeds or the entire operation fails. The original Batch upgrade had already been delayed from September into October after validator support briefly fell below the required level and reset the two-week countdown.
XRPL’s documentation confirms BatchV1_1 replaces the original Batch amendment and specifically fixes the critical bug found in that earlier implementation. The Batch rollout now depends on both continued validator support and server operators updating their software.
One unusual aspect of the emergency release is that developers have not yet published the source code covering the security-sensitive fixes. XRPL said the code will be disclosed later alongside a retrospective explaining the issue. The published changelog confirms a fix rejecting Batch inner transactions using the wrong wrapper, plus additional integer-arithmetic hardening in the payment engine and ledger helpers.
Officials did not report stolen funds or a mainnet attack, and the update appears preventative rather than a response to an exploit. Activation also remains conditional: XRPL protocol changes require sustained validator backing rather than unilateral activation by Ripple.
