xrpld 3.4.1 emergency release: old servers block on 9 October
Serguey Asael Shinder2 min readVersion 3.4.1 of xrpld, the reference server for the XRP Ledger, was published on 25 September as an emergency release to fix security-sensitive issues in the protocol. It introduces a new amendment, fixBatchV1_2, with its default vote set to yes, along with other security and stability fixes.
The release notes give two headline changes from the version commit log: rejecting Batch inner transactions that arrive with the wrong wrapper, which is what fixBatchV1_2 does, and assorted integer-arithmetic hardening in the payment engine and ledger helpers. Because of the security sensitivity, the source code has not been published yet; it is to follow together with a retrospective. Signed packages are available, with the DEB and RPM packages now hosted at packages.xrplf.org under an XRP Ledger Foundation signing key.
The deadline is the practical point. According to the notes, fixBatchV1_2 has already gained support from a supermajority of validators and is expected to become enabled on 9 October 2026. If it activates then, servers that have not been updated to 3.4.1 will become amendment blocked - unable to keep in sync with the network. The XRPSCAN amendments dashboard on 27 September showed fixBatchV1_2 in its two-week activation period alongside BatchV1_1 and PermissionDelegationV1_1.
What it means
The fix and the feature it protects are timed together. BatchV1_1 - the second attempt at letting an account submit several transactions as one all-or-nothing unit - is on course for the same date, and the new amendment closes a gap in how its inner transactions are validated before that happens. Publishing binaries without source is unusual for an open-source server, and it asks operators to trust the build; the stated reason is to avoid pointing attackers at the flaw before most of the network has upgraded.
For anyone running an XRPL server - exchanges, wallets, validators, API providers - the action is simple and dated: upgrade before 9 October, or risk a server that stops following the ledger the day the amendment switches on.