- fixBatchV1_2
Technical context pending.
XRP Ledger · Software
xrpld / rippled versions of the XRP Ledger
The latest stable release on GitHub is xrpld 3.4.1, released on Oct 10, 2026. The server is the reference server software that ships new amendments and fixes bugs; since version 3.2.0 its official name is xrpld. This page lists the latest releases with their UTC date and reported amendment introductions, which do not prove activation.
- Latest on GitHub
- xrpld 3.4.1
- released Oct 10, 2026
- Stable releases
- 12
- of 15 listed versions
- Open for voting
- 8
- in voting or in the two-week majority period
Latest stable release on GitHub
What is new in xrpld 3.4.1?
Amendments reported as introduced with this version; availability is separate from activation.
- fixBatchV1_2
Technical context pending.
History
Release history
The latest server versions with UTC release date, status and reported amendment introductions.
- LendingProtocolV1_1
Closed vaults with fixed schedules and payment-based interest accounting extend the lending protocol.
- fixCleanup3_4_0
The bundled fix for xrpld 3.4.0 corrects edge cases in vaults, lending, AMMs, the permissioned DEX, escrow, sponsorship, and delegation.
- DynamicMPT
Issuers can update or permanently lock an MPT issuance's metadata, TransferFee, and certain capabilities.
- Sponsor
Third parties can cover an account's transaction fees and reserves.
- ConfidentialTransfer
ConfidentialTransfer encrypts confidential MPT balances and hides ConfidentialMPTSend amounts while allowing issuer and optional auditor inspection.
- PermissionDelegationV1_1
Accounts can delegate selected transaction permissions to other accounts while keeping their own keys private.
- fixCleanup3_3_0
The bundled fix for xrpld 3.3.0 corrects edge cases in vaults, lending, AMMs, the permissioned DEX, checks, and pseudo-accounts.
- BatchV1_1
The corrected Batch version processes two to eight transactions as one batch.
No new amendment. xrpscan lists no amendment that was first introduced with this version.
- fixCleanup3_2_0
A bundled fix hardens vaults, lending, the permissioned DEX, and MPTs.
- fixCleanup3_1_3
A bundled fix addresses bugs involving NFTs, domains, vaults, and lending.
No new amendment. xrpscan lists no amendment that was first introduced with this version.
No new amendment. xrpscan lists no amendment that was first introduced with this version.
No new amendment. xrpscan lists no amendment that was first introduced with this version.
- LendingProtocol
The XRPL lending protocol represents fixed-term, unsecured loans funded by vault pools.
- SingleAssetVault
A Single Asset Vault pools one asset from multiple depositors in a ledger object.
- fixBatchInnerSigs
Inner batch transactions are no longer incorrectly marked as directly signed; the amendment was disabled in rippled 3.1.1 and BatchV1_1 carries the fix.
No new amendment. xrpscan lists no amendment that was first introduced with this version.
No new amendment. xrpscan lists no amendment that was first introduced with this version.
- fixTokenEscrowV1
MPT escrows correctly account for the issuer's locked balance after the transfer fee.
- fixAMMClawbackRounding
AMMClawback corrects rounding discrepancies for the final LP token holder.
- fixIncludeKeyletFields
Ledger entries include the fields that determine their object ID.
- fixPriceOracleOrder
Asset pairs in price oracles keep the same order during creation and updates.
- fixMPTDeliveredAmount
Direct MPT payments receive complete DeliveredAmount metadata.
- fixDirectoryLimit
The fixed page limit for ledger directories is removed.
No new amendment. xrpscan lists no amendment that was first introduced with this version.
Pipeline
What is coming next?
Reported in server software; a source introduction does not establish that a stable release is published. Activated once more than 80 percent of trusted validators have agreed for two weeks.
A Single Asset Vault pools one asset from multiple depositors in a ledger object.
23 of 35 yes votes; minimum: 29 (current 65%; support >80%)
Closed vaults with fixed schedules and payment-based interest accounting extend the lending protocol.
22 of 35 yes votes; minimum: 29 (current 62%; support >80%)
The XRPL lending protocol represents fixed-term, unsecured loans funded by vault pools.
22 of 35 yes votes; minimum: 29 (current 62%; support >80%)
ConfidentialTransfer encrypts confidential MPT balances and hides ConfidentialMPTSend amounts while allowing issuer and optional auditor inspection.
21 of 35 yes votes; minimum: 29 (current 60%; support >80%)
Issuers can update or permanently lock an MPT issuance's metadata, TransferFee, and certain capabilities.
16 of 35 yes votes; minimum: 29 (current 45%; support >80%)
Third parties can cover an account's transaction fees and reserves.
10 of 35 yes votes; minimum: 29 (current 28%; support >80%)
Reward shares in cross-chain transactions are always rounded down.
10 of 35 yes votes; minimum: 29 (current 28%; support >80%)
XLS-38 defines asset bridges between XRPL-based networks.
4 of 35 yes votes; minimum: 29 (current 11%; support >80%)
The full pipeline including drafts is in the XRPL amendment overview.
Terms
Release or amendment: what is the difference?
Two terms that are often confused but describe different things.
A server release is a version of the server software. It ships the code for new features and bug fixes, but on its own it does not yet change any network rule.
An amendment is the on-ledger rule itself. Its code ships in a server version and only becomes active once more than 80 percent of trusted validators have agreed for two weeks. In short: the release ships the code, the amendment switches the rule on.
You can find the live status of every rule in the XRPL amendment overview.
FAQ
Common questions
Answered briefly; the sources follow in the next section.
What is the current XRP Ledger server version?
What is the difference between a server release and an amendment?
How often is a new server version released?
Transparency
Source and methodology
Release records come from GitHub; amendment introductions are independently attributed to xrpscan.
The version data comes from the official GitHub releases of XRPLF/rippled. The mapping of which amendment came with which version uses the introduced field from the xrpscan amendment API.
An RSS feed for new releases and amendment votes is not available yet.
Source response: Nov 16, 2026, 19:53 UTC · cached reads; no guaranteed refresh time · English editorial update: Oct 5, 2026