XRP Ledger version 3.4.1 is now the minimum required version after the recent amendments were activated.

This release patched critical parts of the XRP Ledger.

The vulnerability report can be found here:
xrpl.org/blog/2026/vuln…
Public release notes:
github.com/XRPLF/rippled/…

xrpld 3.4.1 is being released with a Batch fix and stability improvements.

We’re asking validators and node operators to upgrade as soon as possible. There has been no impact to mainnet, and no loss of funds.

There is also a new fix amendment, fixBatchV1_2, which addresses a that does not pose a risk to funds.

The amendment is marked as Default Yes. Both Batch and the fix amendment are in the activation period and set to activate in 2 weeks. A detailed technical report will be shared after the fix amendment has been activated.

XRP Ledger version 3.4.0 is now available ✅

New amendments for voting:

- Lending Protocol v1.1 - closed-ended vaults and cash-basis accounting.
- fix Cleanup - bundled fixes.

Performance and Stability:

- Online delete now pauses on ledger history gaps, so nodes stay closer ocol hardening and faster MPT freeze checks.

Packages have moved to packages.xrplf.org with an XRPLF signing key. Nodes on 3.3.0 or earlier must update their repo config.

Release blog post:
xrpl.org/blog/2026/xrpl…

Permission Delegation on the XRP Ledger has passed an independent security review by @cantinasecurity and the XRPL quality assurance test suite.

All findings were fixed in v1.1 and verified by Cantina, and the QA team found no regressions across 5,088 tests.

The public report of the completed XRP Ledger Batch amendment audit is now available.

All findings have already been fixed in the Batch amendment that is currently up for vote. ✅

Batch is one of the most anticipated amendments on the XRP Ledger for both retail and .

Please update your XRPL nodes to 3.3.0!

Over 60% of $XRP Ledger nodes have already been updated to version 3.3.0.

This version includes, among other improvements, the feature amendments Batch, Dynamic MPT, Permission Delegation, Sponsor, and Confidential Transfer, as well as a fix bundle.

XRP Ledger version 3.3.0 is now available ✅

New amendments for voting:

1) Confidential Transfer - encrypted MPT balances and transfers.

2) Batch - wrap up to 8 transactions that execute atomically under four different modes.

3) Sponsor - sponsored fees and reserves.

4) give other accounts permissions to only send specific transaction types.

5) Dynamic MPT - issuer mutable MPT properties.

6) fix Cleanup - bundled fixes.

Performance and Stability:

- At least 10-15% lower memory usage, more in some configurations.

- Improved node sync.

Release notes:
github.com/XRPLF/rippled/…

The upcoming XRP Ledger features in XRPL 3.3.0 went through adversarial testing by the community.

Participants earned rewards by helping improve the amendments.

Check out the summary report below.

Impressive upgrade speed from the XRPL Community.

100% of all dUNL validators have upgraded to XRPL 3.2.1

37% of the total XRP Ledger network is already running version 3.2.1.

XRP Ledger 3.2.1 is now available.

This fixes the manifest flood observed on Friday, July 31. The XRPL continued closing ledgers normally throughout. A post-mortem will follow soon for the community.

Nodes previously accepted, stored and re-broadcast an unlimited number of validator keys. 3.2.1 adds four limits:

1) Size cap per manifest - any single manifest larger than expected is rejected.

2) Receive cap - incoming batches over the limit are discarded, instead of breaking the peer connection.

3) Send cap - the bulk manifest greeting sent to each new peer is now bounded.

4) Cache cap - once 100 unknown keys are held, new ones are refused.

We also no longer persist manifests from unknown keys to disk, so a flood cannot survive a restart.

Please update immediately by following these steps:

1) Update normally to XRPL 3.2.1

2) Wait 1–2 min, confirm xrpld is running, it does not need to be in status full or proposing.

3) Restart xrpld again - very important.

In 4 days fixCleanup3_2_0 amendment goes live.

Please remind your favorite project, exchange and developer to update their XRP Ledger nodes to 3.2.0 to continue service operations.

42% of the network is running XRPL 3.2.0 .

This version brings the name transition from rippled to xrpld, under the hood improvements and one fix amendment.

If you haven't upgraded yet, please update your XRP Ledger nodes to 3.2.0!

Migration Guide:
xrpl.org/docs/infrastru…

Updating to XRP Ledger 3.2.0 requires migration steps due to the name transition from rippled to xrpld.

Please follow the migration guide when updating your XRPL infrastructure and backup the relevant files mentioned.

Migration guide:
xrpl.org/docs/infrastru…

XRP Ledger version 3.2.0 is now available - update your nodes.

With one amendment bundling all fixes into one fixCleanup.

Release notes:
github.com/XRPLF/rippled/…

XRP Ledger 3.2.0 is coming soon!

The core software powering the XRPL is changing its name from rippled to xrpld.

This transition will require some updates for infrastructure operators. We're preparing a detailed playbook to help guide you through the upgrade process.

The fix amendment in XRPL 3.1.3 is now in 2 week activation period.

Please update your XRP Ledger nodes to 3.1.3 as soon as possible to prevent amendment blocking and service interruption of your users.

Release notes:
github.com/XRPLF/rippled/…