XRPL developers released xrpld 3.4.1 on Sept. 25 as an emergency update addressing what they described as “security-sensitive issues.” The official release notes say the new fixBatchV1_2 amendment has already reached validator supermajority support and is expected to activate on Oct. 9 if that backing remains above the required threshold. For server operators, the date matters for more than gaining a new feature. Nodes that have not upgraded to version 3.4.1 when fixBatchV1_2 activates could become amendment blocked, meaning they would no longer remain synchronized with the network. Batch Is Arriving With Another Security Fix The security amendment sits directly beside 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, including structures where every transaction succeeds or the entire operation fails. Coinpaper previously explained how the Batch upgrade was pushed from September into October after validator support briefly fell below the required level and reset its two-week countdown. The official XRPL amendment documentation confirms that BatchV1_1 replaces the original Batch amendment and specifically fixes a critical bug discovered in that earlier implementation. The Full Security Issue Is Still Not Public One unusual part of the emergency release is that developers have not yet published the source code covering the security-sensitive fixes. XRPL says the code will be disclosed later together with a retrospective explaining the issue. The published changelog currently confirms a fix rejecting Batch inner transactions using the wrong wrapper, along with additional integer-arithmetic hardening in the payment engine and ledger helpers. That does not mean the XRP Ledger suffered an exploit. The official announcement does not report stolen funds or a mainnet attack, and the update appears preventative. The activation itself also remains conditional. XRPL protocol changes require sustained validator backing rather than unilateral activation by Ripple, a process Coinpaper explains in its guide to XRPL governance .
