XRPL Validators Rally Behind Latest Upgrade, Though Node Adoption Still Trails v3.1.3 - Crypto Economy

TL;DR:

• XRPL v3.2.0 launched on June 15 to reduce operating costs, improve stability and support institutional use, but broader node adoption still trails v3.1.3.
• Around 43% of roughly 833 active nodes run v3.2.0, while 51% remain on v3.1.3, despite 89% default UNL validator support.
• The separate fixCleanup3_2_0 amendment still needs stronger voting support, even though Ripple has voted in favor, creating a slower consensus track for security fixes and newer features.

The XRP Ledger’s latest server upgrade is gaining support where it counts most, but broader network adoption still tells a more uneven story. Version 3.2.0, released on June 15, is designed to reduce operating costs, improve stability and make the ledger more attractive for institutional use. Yet across roughly 833 active nodes, about 43% are running v3.2.0, while 51% remain on v3.1.3. That gap creates an odd split: validators are moving faster than the wider node base, so the upgrade looks strategically accepted but operationally unfinished, especially for infrastructure operators still running older code today.

Validator support clears the key threshold, but amendments lag

The validator picture is more decisive. XRPL relies on a trusted validator set known as the Unique Node List, or UNL, and upgrades need sustained support from more than 80% of that list for two straight weeks to activate. On the default UNL of 35 validators, 31 are already running v3.2.0, equal to about 89%. That matters because raw node count does not decide activation. The governance-weighted signal is already strong, even if the broader network has not yet converged around the new software version across relaying infrastructure and public nodes still catching up gradually.


The complication is that the upgrade comes with a separate on-ledger amendment, fixCleanup3_2_0, and that vote is moving slower than the software rollout. The amendment bundles security fixes and improvements for newer XRPL features, including single-asset vaults, permissioned decentralized exchanges, multi-purpose tokens and the lending protocol. It also adds internal checks intended to stop deleted accounts from leaving stray data behind. The security package still needs explicit consensus, which makes validator software adoption and amendment approval two related but distinct milestones for the network’s next functionality layer and security posture before activation can safely proceed.

Ripple has voted in favor of fixCleanup3_2_0, but the amendment is still polling well below the adoption level seen for v3.2.0 itself. Validators that fail to upgrade before the amendment activates risk being cut off from the ledger in an amendment-blocked state, a technical safeguard that can quickly become an operational problem. For XRPL, the next phase is coordination discipline, because institutional-facing upgrades only matter if validators, nodes and amendment votes align without leaving critical participants behind during rollout, particularly as newer features expand the ledger’s enterprise ambitions and adoption narrative for institutional users now.