Here’s a sharper and more concise rewrite:
The latest software release has gained strong traction among validators, but it still lags behind version 3.1.3 in overall node distribution. Meanwhile, the included security amendment is progressing more slowly, as it requires a separate vote. For the upgrade to go live, at least 80% of trusted validators must support it.
The XRP Ledger’s new server update, v3.2.0, is built to cut operating costs, boost stability, and improve its appeal to institutional users. Adoption is rising, but it hasn’t yet overtaken v3.1.3 across the wider network, and its related security enhancements 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 data.
The update was released on June 15.
While node-level adoption appears gradual, most validators—the network’s key decision-makers—have already upgraded.
The XRP Ledger relies on a trusted validator set known as the Unique Node List (UNL). For any upgrade or amendment to activate, it must secure sustained backing from more than 80% of these validators over a two-week period.
Within the default UNL of 35 validators, 31 are already on v3.2.0, or roughly 89%, surpassing the required threshold. This validator support—not overall node count—is what ultimately determines whether the upgrade is finalized.
Security Amendment Lags Behind
A separate amendment bundled with the upgrade is still trailing in progress.
The proposal, fixCleanup3_2_0, is undergoing an on-ledger vote rather than being automatically applied. It includes multiple security fixes and enhancements for newer features such as single-asset vaults, permissioned decentralized exchanges, multi-purpose tokens (MPTs), and the lending protocol, which allows 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 the software upgrade, highlighting that installing the update and approving amendments are two separate steps.
Ripple, the company behind the XRP Ledger, has voted in favor of the fixCleanup3_2_0 amendment. Validators that do not upgrade before it is activated risk being disconnected from the network, entering an “amendment-blocked” state.
