XRP Ledger Releases xrpld 3.4.1 With Batch Fix
The XRP Ledger network released xrpld 3.4.1, which adds stability improvements and fixes an issue in the Batch feature through the fixBatchV1_2 amendment. Developers said mainnet was not affected and no user assets were lost, while the fix has 94.29% support and does not require a manual vote. Ripple and community members temporarily switched some votes to align the activation of Batch and its fix, since amendments need over 80% validator support for two weeks.
xrpld 3.4.1 brings stability upgrades and a targeted correction for the Batch function via fixBatchV1_2. Developers stated that the main network was not impacted and users did not lose funds. The fix already has default backing, so no manual validator vote is needed; XRPScan shows 94.29% support.
Batch, or XLS 56, lets multiple accounts execute XRPL transactions atomically in one ledger closure. Because amendments require over 80% validator approval for two weeks, Ripple and community members briefly shifted some votes from Yes to No to synchronize Batch and its fix. Batch and fixBatchV1_2 are now expected around October 9, 2026; permission delegation around October 8.
The release may mainly affect XRP holders, validators, node operators, and developers relying on the ledger. Smoother Batch activation could improve confidence in multi-account transactions and network reliability, while the temporary vote changes may prompt observers to watch validator coordination. If timelines hold, users may see no direct change, but exchanges and payment services could benefit from fewer operational surprises.