XRP Ledger's v3.2.0 server software update rolled out on June 15 and has achieved the adoption threshold among validators required for network upgrades. However, adoption across the broader node network remains incomplete. Of approximately 833 active nodes on the ledger, about 43% are running v3.2.0, while 51% remain on the older v3.1.3 version, according to XRPScan data. The upgrade was designed to lower operating costs, improve stability, and make the network more appealing to institutional users. Validators — a trusted subset of 35 nodes on the default Unique Node List (UNL) that approve changes to the ledger's official record — have shown stronger adoption, with 31 validators (89%) already running the new software, comfortably exceeding the 80% threshold the network requires. The XRP Ledger is the blockchain behind XRP and relies on a distributed network of computers called nodes to store transaction history and relay information across the system.
Validators Clear Threshold, Nodes Lag Behind
The v3.2.0 software update functions as a new version of the software that node computers run, similar to an iOS or Android update on a phone. Not every node updates instantly, and for a period, older and newer versions operate side by side. A node is one of the computers that stores a copy of the ledger's transaction history and helps pass information around the network.
Raw node numbers do not determine whether an upgrade takes hold across the network. That responsibility belongs to validators on the Unique Node List (UNL), a smaller group of trusted nodes that provide final approval on what enters the ledger's official record. There are 35 validators on the default UNL, and 31 of them (approximately 89%) have moved to the new upgrade. This comfortably clears the 80% threshold the network requires. The threshold must be sustained for two consecutive weeks before a change is considered locked in.
Security Amendment Awaits Separate Vote
Bundled with the software but moving on a separate track is an amendment called fixCleanup3_2_0. Unlike the software rollout itself, an amendment is a formal on-ledger vote. Validators must actively vote it in, and it requires the same 80% supermajority to pass.
The fixCleanup3_2_0 amendment packages several security fixes for newer features on the ledger, including single-asset vaults (a mechanism to pool funds), permissioned decentralized exchanges (trading platforms with access controls), multi-purpose tokens, and the lending protocol that allows users to borrow against tokenized assets. It also adds checks designed to prevent deleted accounts from leaving residual data behind.
Ripple has voted in favor of the amendment. However, a validator upgrading its software and that same validator voting the amendment through are two separate actions. Currently, only the software upgrade is close to completion.
Validator Upgrade vs. Node Adoption Gap
Validators that do not upgrade before the amendment carries the risk of entering an amendment-blocked state. This state essentially locks them out of participating in the network, similar to how an outdated app can stop functioning once it falls too far behind on required updates.
That risk keeps the slower node-level adoption worth monitoring even though validator numbers appear solid. For now, the upgrade has the support it needs where it counts, but the security fixes accompanying it are still waiting for the rest of the network to catch up.
FAQ
What is the XRP Ledger v3.2.0 software upgrade?
The v3.2.0 software upgrade is a new version of the server software that XRP Ledger nodes run. It rolled out on June 15 and was designed to lower operating costs, improve network stability, and make the ledger more appealing to institutional users. The upgrade functions similarly to an operating system update on a phone, and not all nodes update simultaneously.
Why does the XRP Ledger require an 80% validator adoption threshold?
The XRP Ledger requires an 80% adoption threshold among validators on the default Unique Node List (UNL) to lock in network upgrades. Validators are a trusted subset of 35 nodes that approve changes to the ledger's official record. Once 80% of validators adopt an upgrade and sustain that level for two consecutive weeks, the change is considered locked in. As of the source data, 31 of 35 validators (89%) have adopted v3.2.0, exceeding the required threshold.
