Here’s a clean, concise rewrite with improved flow:
The newest software version is now widely used by validators, though it still trails v3.1.3 in total node share. At the same time, the bundled security amendment is moving more slowly because it requires a separate vote. For the upgrade to activate, it must secure backing from at least 80% of trusted validators.
The XRP Ledger’s latest server update, v3.2.0, is designed to lower operating costs, enhance stability, and strengthen its appeal to institutional users. While adoption is increasing, it has yet to surpass v3.1.3 across the broader network, and its accompanying security fixes remain under review.
Out of around 833 active nodes that maintain and relay the ledger, roughly 43% are running v3.2.0, while about 51% continue to operate on v3.1.3, according to XRPSCAN data.
The update was released on June 15.
Although overall node adoption is gradual, validators—the network’s most critical participants—have largely already upgraded.
The XRP Ledger relies on a trusted validator set called the Unique Node List (UNL). For any upgrade or amendment to take effect, it must receive sustained support from more than 80% of these validators over a two-week period.
Within the default UNL of 35 validators, 31 are already using v3.2.0, or about 89%, surpassing the required threshold. This level of validator support, rather than total node count, determines whether the upgrade is effectively complete.
Amendment Progress Remains Slower
A separate amendment included with the upgrade is still lagging behind.
The proposal, known as fixCleanup3_2_0, is currently undergoing an on-ledger vote. It introduces 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 allows users to borrow against pooled funds.
It also adds safeguards to prevent deleted accounts from leaving behind residual data. However, support for this amendment remains well below that of the software upgrade, underscoring that updating nodes and approving amendments are two distinct processes.
Ripple, the company behind the XRP Ledger, has backed the fixCleanup3_2_0 amendment. Validators that fail to upgrade before it goes live risk being cut off from the network, entering what is known as an “amendment-blocked” state.
