XRP Ledger Upgrade Hits 89% — but a Critical Security Vote Stalls

The XRP Ledger upgrade to version 3.2.0 is moving faster among the validators who actually matter for activation than the overall node count suggests — but a separate security amendment is lagging well behind, and that gap carries real consequences for anyone still running older software.

Key takeaways

• XRP Ledger released v3.2.0 server software on June 15, designed to cut operating costs and improve stability for institutional users.
• 43% of active nodes run v3.2.0, while 51% still run the older v3.1.3, according to XRPSCAN data.
• 31 of 35 validators on the Unique Node List have upgraded, representing 89% — clearing the 80% threshold required for activation.
• A companion amendment, fixCleanup3_2_0, bundles security fixes and feature improvements but is polling far below the software upgrade rate.
• Validators that skip the upgrade before the amendment activates risk being cut off from the ledger in an amendment-blocked state.

XRP Ledger Releases Version 3.2.0 Software

The new software, which rolled out on June 15, is built to make the network cheaper to run, more stable, and more attractive for institutional participants. Those goals matter because the XRP Ledger has been actively expanding its feature set — adding a lending protocol, single-asset vaults, permissioned decentralized exchanges, and multi-purpose tokens — features that demand a more robust technical foundation.

By raw node count, however, v3.2.0 hasn’t yet taken over. Of approximately 833 active nodes on the network — the machines that store and relay the ledger — about 43% are running v3.2.0, while 51% remain on v3.1.3, according to XRPSCAN data. That split might look like slow uptake, but it’s not the whole story.

Why node count isn’t the deciding metric

Not all nodes are equal in the XRP Ledger’s architecture. The network runs on a trusted set of validators known as the Unique Node List (UNL), and it’s that list — not the broader node population — that determines whether a software version or amendment officially activates. The activation rule is precise: more than 80% of UNL validators must run the new version continuously for two straight weeks.

On that measure, the picture looks considerably stronger. Of the default UNL’s 35 validators, 31 have already moved to v3.2.0, putting validator adoption at roughly 89% — well above the required threshold. That figure is what the network watches, and it signals the upgrade is functionally on track.

Validator Upgrade Momentum and Network Activation Criteria

The 89% figure among UNL validators is meaningful precisely because it clears the bar. But clearing the software threshold and fully completing the upgrade are still two different things when an accompanying amendment is involved.

The two-week sustained support requirement exists to prevent premature or unstable activations. Once those two weeks of majority support are logged and held, the upgrade locks in. The validator community — which includes entities whose continued participation underpins network consensus — has moved quickly relative to the general node pool, suggesting that the parties with the most at stake took the new version seriously from the start.

The Voting Lag on fixCleanup3_2_0

The more pressing concern is what’s happening — or not happening — with the fixCleanup3_2_0 amendment. Unlike a routine software push, this is a formal on-ledger vote, a separate governance step that requires its own majority to pass. And right now, it’s polling far below the software adoption rate.

What the amendment actually covers

The fixCleanup3_2_0 amendment isn’t cosmetic. It bundles security fixes and targeted improvements for several of the network’s newer features: single-asset vaults, permissioned decentralized exchanges, multi-purpose tokens (MPTs), and the lending protocol. It also introduces internal checks specifically designed to prevent deleted accounts from leaving behind orphaned data on the ledger — a housekeeping fix with real implications for long-term data integrity.

Ripple’s position and the risk of waiting too long

Ripple, the payments company whose founders built the XRP Ledger, has already cast its vote in favor of fixCleanup3_2_0. But Ripple’s support alone doesn’t move the needle to activation. The broader validator set needs to follow.

The stakes for non-upgraded validators are concrete. Any validator that fails to upgrade before the amendment activates risks entering what the network formally calls an amendment-blocked state — effectively cut off from the ledger. That’s not a theoretical warning. It’s a built-in mechanism that forces nodes to stay current or lose the ability to participate in consensus.

The gap between software adoption and amendment voting reveals something worth understanding about how blockchain upgrades actually work in practice. Installing new server software is a technical action operators can take unilaterally. Voting an amendment through is a governance step that requires coordination across an entire validator community. Those two timelines don’t always move in sync, and when they diverge — as they have here — the network enters a transitional window where security improvements are in the queue but not yet live. The longer that window stays open, the longer the newer features on the XRP Ledger operate without the full set of protections fixCleanup3_2_0 is designed to provide.

FAQ

What is the current adoption rate of the XRP Ledger v3.2.0 upgrade?

About 43% of active network nodes are running v3.2.0, while 51% remain on the older v3.1.3. Among validators on the Unique Node List, adoption is significantly higher at 89% — 31 of 35 validators have upgraded.

What threshold must be met for the XRP Ledger v3.2.0 upgrade to activate?

Over 80% of validators on the Unique Node List must run the new version continuously for two straight weeks. With 89% of UNL validators already on v3.2.0, that threshold has been cleared.

What is the fixCleanup3_2_0 amendment, and how does its voting status compare to the software upgrade?

fixCleanup3_2_0 is a formal on-ledger amendment that packages security fixes and improvements for newer XRP Ledger features including lending, vaults, decentralized exchanges, and multi-purpose tokens. Its adoption currently lags well behind the v3.2.0 software upgrade rate, making it a separate and slower process.

What are the risks for validators who do not upgrade before the amendment activates?

Validators that fail to upgrade before fixCleanup3_2_0 activates risk being placed in an amendment-blocked state, cutting them off from the ledger and preventing them from participating in network consensus.

Article produced with the assistance of artificial intelligence and reviewed by the editorial team.