Here’s a refined and more streamlined rewrite:

The latest software release is now favored by most validators, but it still lags behind version 3.1.3 in overall node distribution. Meanwhile, the bundled security amendment is advancing more slowly, as it requires a separate vote. For the upgrade to activate, it needs support from at least 80% of trusted validators.

The XRP Ledger’s new server version, v3.2.0, is built to reduce operating costs, improve stability, and attract institutional users. Although adoption is increasing, it has not yet overtaken v3.1.3 across the wider network, and its associated security fixes are still awaiting approval.

Of the roughly 833 active nodes that maintain and relay the ledger, about 43% are running v3.2.0, while 51% remain on v3.1.3, according to XRPSCAN.

The update was released on June 15.

While overall node adoption remains gradual, validators—the most influential participants in the network—have largely already upgraded.

The XRP Ledger operates on a trusted validator set known as the Unique Node List (UNL). For any upgrade or amendment to go live, it must secure consistent backing from more than 80% of these validators over a two-week period.

Within the default UNL of 35 validators, 31 are already running v3.2.0, or roughly 89%, surpassing the required threshold. This validator support—not total node count—is what ultimately determines whether the upgrade is complete.

Amendment Still Catching Up

A separate amendment included with the upgrade is progressing more slowly.

The proposal, fixCleanup3_2_0, is currently undergoing an on-ledger vote. It bundles several security improvements and upgrades to newer features such as single-asset vaults, permissioned decentralized exchanges, multi-purpose tokens (MPTs), and the lending protocol, which enables users to borrow against pooled funds.

It also introduces safeguards to prevent deleted accounts from leaving behind leftover data. However, support for this amendment remains significantly lower than for the software upgrade, highlighting that installing the update and approving amendments are two distinct steps.

Ripple, the company behind the XRP Ledger, has voted in favor of the fixCleanup3_2_0 amendment. Validators that fail to upgrade before it activates risk being disconnected from the network, entering an “amendment-blocked” state.