XRP Ledger pushes v3.2.0 rollout as amendment deadline nears

<a href="https://bbg-news.com/xrp-usd/">XRP</a> Ledger pushes v3.2.0 rollout as amendment deadline nears

The XRP Ledger is nearing a major upgrade! Over two-thirds (66%) of its validators – a total of 99 – are now using the latest version, v3.2.0. If this trend continues, the upgrade is expected to activate on July 29th.

Summary

  • XRP Ledger v3.2.0 now runs on 66% of tracked validators and 57.33% of nodes.
  • The fixCleanup3_2_0 amendment holds 85.71% support ahead of its July 29 activation.
  • The update fixes vault, lending, and permissioned DEX issues while renaming rippled to xrpld.

Recent data from XRPL Explorer shows that 481 nodes – over 57% of the XRP Ledger network – are now running version 3.2.0. While this represents growth since the software’s release in June, a significant number of network operators are still using the older version.

Currently, 42 validators – or 28% of those we’re tracking – are still running version 3.1.3. Plus, 323 out of the 825 nodes we’ve observed (about 38.41%) are also using this older software version.

Updating the software and changing the core rules on the XRP Ledger are handled differently. Installing version 3.2.0 simply provides the newest improvements, but a rule change needs approval from at least 80% of network validators for two weeks to become active.

The proposed update, fixCleanup3_2_0, has received enough votes to pass. Current data from the XRP Ledger shows 85.71% approval, with 30 validators supporting the change and 5 against it.

Now that we have enough support, the update will go live on July 29, 2026, at 9:57 AM UTC. We need at least 80% support to continue counting down to activation; if support drops below that level, the countdown will reset and start over after two weeks.

Validator backing keeps the amendment on schedule

Vet, a validator on the XRP Ledger, is advising node operators to update their software *before* the upcoming changes take effect. This will ensure their systems continue working correctly with the updated rules. If they don’t use supported software versions, their servers could be unable to process transactions and verify the ledger once the new rules are activated.

This update, version 3.2.0, isn’t about adding new features; it focuses on improving existing ones within the XRPL network. It includes important fixes for areas like Single Asset Vaults, the Lending Protocol, the Permissioned decentralized exchange, Multi-Purpose Tokens, and Permissioned Domains – all functions users are already familiar with.

This update improves calculations for Single Asset Vaults, fixing potential inaccuracies with deposits and shares. It also includes changes to the Lending Protocol to ensure correct accounting, and resolves issues discovered in the Permissioned DEX and Permissioned Domains after they were first launched.

Amendment voting lets validators choose whether to approve major changes to the network. While most validators are already using the latest software (v3.2.0), these changes won’t actually take effect on the main network until the voting period finishes successfully.

In early July, Crypto.news reported that fixCleanup3_2_0 was nearing activation because it had received over 80% approval from the network. Currently at 85.71%, there’s a comfortable margin of 5.71%, but according to XRPL rules, this level of support needs to be maintained until the planned activation date.

XRPSCAN shows that a change called ‘fixCleanup3_2_0’ was proposed with version 3.2.0 of the software. While updating to this version doesn’t automatically register a vote for the change, network operators still need to ensure their systems are compatible to run it.

Version 3.2.0 prepares XRPL infrastructure for new activity

The latest version, v3.2.0, released in June, has updated the name of the core software that powers the XRP Ledger. It’s now called “xrpld” instead of “rippled.” This change is based on a technical proposal called XLS-0095, which aims to better connect the software’s name with the XRP Ledger itself.

This update involves more than just a name change for the program. If you’re upgrading from version 3.1.3 of XRPL, you’ll also need to update your configuration file from ‘rippled.cfg’ to ‘xrpld.cfg’, and adjust any related settings and deployment instructions.

Node operators might also have to update things like database locations, software dependencies, automated scripts, service settings, and server information. The XRPL documentation offers a step-by-step migration guide that helps keep your existing node data intact while updating the way servers are named.

The latest update to the XRP Ledger, version 3.2.0, focuses on improving its underlying structure. Beyond a name change, this release removes older features that haven’t been used in over two years and continues the process of breaking down the software’s code into more manageable parts. This will simplify future updates and maintenance.

I’ve been watching some interesting developments on the XRPL recently. It’s not just about the network upgrades, but also how people are actually *using* it. I saw that t54.ai, which is backed by Ripple, announced they’ve already processed over a million AI-powered payments using the x402 protocol. They’ve also launched an AI Hub, which looks like a cool place for developers and payment services to build new things. It’s encouraging to see real-world applications being tested and built on the ledger.

t54.ai reports that this platform was created with help from Ripple’s development team and the XRP Ledger Foundation. It’s a central resource gathering AI projects, automated tools, developer resources, payment solutions, and technical information – all designed to support teams creating applications for the XRPL network.

As a crypto investor, I’m watching the upcoming XRP Ledger update closely. Voting by validators is looking good with only eight days to go, which means the fixCleanup3_2_0 update is still on track. Now it’s up to those of us running older versions of the software to update – if enough of us do, the changes will automatically activate on July 29th, improving the network’s maintenance.

2026-07-21 19:25