Key Highlights
- XRP Ledger Operations released xrpld 3.4.1 with a fix for a minor issue related to the Batch feature.
- Validators and node operators are advised to upgrade promptly to maintain consistent network participation.
- The fixBatchV1_2 amendment is marked “Default Yes” and is currently in its activation period alongside the Batch amendment.
The XRP Ledger Operations team has released xrpld version 3.4.1. The update includes a fix related to the Batch feature and additional stability improvements. Validators and node operators have been asked to upgrade as soon as possible.
According to the official announcement on September 25, there has been no impact to the XRP Ledger mainnet and no loss of funds. The update comes just over a week after xrpld 3.4.0 was released on September 17. The previous release introduced new amendments and several protocol fixes, with operators also advised to upgrade their servers.
New fixBatchV1_2 amendment added
Alongside the software update, developers have introduced a new amendment called fixBatchV1_2. According to XRP Ledger Operations, the amendment addresses a minor issue in Batch and the problem does not pose a risk to user funds.
Developers have not yet published the full technical details of the issue. A detailed technical report is expected after the fix amendment has been activated.
The Batch feature allows multiple XRP Ledger transactions to be grouped and processed together. The current BatchV1_1 amendment replaced an earlier Batch implementation after a critical signature-validation flaw was discovered before that version reached mainnet. XRP Ledger documentation describes BatchV1_1 as the replacement implementation under the XLS-56 standard.
The Crypto Times previously reported that BatchV1_1 had entered its activation period after receiving sufficient validator support, with activation at the time expected on September 29.
The latest XRPL Operations update now says both Batch and fixBatchV1_2 are in an activation period and are set to activate in about two weeks.
The release focuses on resolving the identified Batch-related issue and improving the overall stability of the reference server implementation. Operators running XRP Ledger servers are advised to apply the update promptly to maintain consistent network participation.
Prior release context
Prior to the 3.4.1 update, version 3.4.0 of xrpld was made available. That release introduced two new amendments, retired one existing amendment, and delivered multiple bug fixes together with build improvements.
One of the new amendments, LendingProtocolV1_1, extended the functionality of Single Asset Vaults and the Lending Protocol. It added support for closed-ended vaults and implemented cash-basis accounting. Closed-ended vaults operate under a defined lifecycle consisting of three phases: subscription, investment, and redemption.
These phases govern when assets may be deposited, when loans may be originated, and when assets may be redeemed. Following activation of the amendment, new loan brokers may be created only against closed-ended vaults. Cash-basis accounting alters the recognition of interest so that income is recorded only when payments are received, rather than recognizing all scheduled interest at the moment of loan origination.
The second amendment, fixCleanup3_4_0, consolidated a collection of amendment-gated corrections. These included application of the asfDisallowIncomingTrustline blocker to OfferCreate transactions, exclusion of deleted domain offers from certain invariants, adjustments to AMMClawback behavior regarding rounding and reserve checks, and enforcement of MPT-related invariants, refinements to NFT offer handling, recycling of escrow owner reserves, introduction of distinct signing hash prefixes for counterparty and sponsor signatures, and various precision and rounding corrections for vault operations.
Additional refinements addressed freeze, authorization, credential, and destination handling within Single Asset Vaults and the Lending Protocol.
In the same release, the fixAMMOverflowOffer amendment was retired and thereby became a permanent component of the protocol. The xrpld DEB and RPM packages were relocated to packages.xrplf.org and are now distributed under an XRPLF signing key. Operators running XRP Ledger servers were previously instructed to upgrade to version 3.4.0 to maintain service continuity.
Network activity background
Separately, data from a public dashboard tracking settlement activity on the XRP Ledger showed that agent payments had surpassed 4 million transactions as of September 5, 2026. The all-time transaction total stood at 4,023,081. Cumulative settled amounts were recorded at 5,753.43 XRP and 3,789.44 RLUSD, with 148 registered merchants.
Daily payment volumes fluctuated over the observed period. A 7-day average of 155,103 transactions was noted, with activity increasing in late August and early September, including several days exceeding 200,000 payments.
The xrpld 3.4.1 release continues the process of maintaining and updating the reference implementation used by validators and node operators on the XRP Ledger.
Also Read: Jumper Announces JUMP Token Sale Starting September 29
