I want to explain what's happening with the XRP Ledger's latest upgrade clearly, because the numbers involved tell two different stories depending on which part of the network you're measuring, and both matter for different reasons.
XRP Ledger v3.2.0 was released to cut operating costs, improve network stability, and make the infrastructure more appealing for institutional use. That's the goal. The reality of how that rollout is progressing right now is more nuanced.
The Numbers That Actually Determine Activation
Here's the key distinction I want to make upfront. Of the approximately 833 active nodes on the XRP Ledger, the machines that store and relay the ledger, around 43% are running v3.2.0 while 51% are still on the previous version, v3.1.3. On a raw node count basis, the new version is still trailing.
But raw node count isn't what determines whether a network upgrade activates on the XRP Ledger. What matters is the Unique Node List, the trusted set of validators whose votes actually govern the network. For any software version or amendment to activate, it needs sustained support from more than 80% of validators on that list for two straight weeks.
Currently, 31 of the 35 validators on the default UNL are running v3.2.0. That's approximately 89%, comfortably above the 80% threshold. So despite the broader node network still running the older version, the validators that actually govern the protocol have largely already moved.
Why This Matters for Institutional Users
Version 3.2.0 was specifically designed with institutional operators in mind. Cheaper running costs and improved stability are exactly the properties that matter to financial firms building payment infrastructure on XRPL. The fact that the key validator set has crossed the 80% threshold is the meaningful milestone here, the broader node adoption will follow as operators update at their own pace.
Ripple, the payments company whose founders created the XRP Ledger, has fully upgraded its own validators to v3.2.0.
The Security Amendment That's Falling Behind
Here's the part of this upgrade picture I find most important to flag, and it's one that isn't getting enough attention. Bundled alongside v3.2.0 is a separate on-ledger vote called fixCleanup3_2_0, and it is polling significantly behind the software adoption rate.
This amendment is not the same as upgrading the software. It's a formal governance vote that packages security fixes and improvements for several of XRPL's newer features, including single-asset vaults, the permissioned decentralised exchange, multi-purpose tokens, and the lending protocol. It also adds internal checks designed to prevent deleted accounts from leaving behind stray data on the ledger.
Ripple has voted in favor of the amendment. But validators that fail to upgrade before it activates risk being cut off from the ledger entirely in what the network calls an amendment-blocked state, meaning they would no longer be able to participate in consensus.
What This Means Going Forward
The headline from today's data is that XRPL's validator set has cleared the threshold for v3.2.0. That's a real positive. The broader node adoption will catch up over time, this is a normal pattern for protocol upgrades on any distributed network.
The more urgent issue is the fixCleanup3_2_0 amendment. If validators don't move on that vote before it eventually activates, the consequences for lagging nodes are real and immediate. The software upgrade and the security amendment are two separate steps, and right now, the second step is noticeably behind the first.