Ripple Update: Fewer Than Half of XRPL Nodes Adopt xrpld v3.2.0

About 89% of UNL validators are currently running xrpld v3.2.0, but support for the fixCleanup3_2_0 amendment stands at just 48.57%, well below the 80% threshold required for activation on the XRP Ledger.

Nearly a month after the release of xrpld v3.2.0—the rebranded version of Ripple’s core server software—data from XRPScan indicates that only 357 out of 828 XRPL nodes (around 43%) have upgraded. Meanwhile, 426 nodes (51%) are still operating on the older v3.1.3 version.

This situation reflects more than just a gradual rollout. It highlights a structural pattern in XRPL governance, where validator consensus progresses much faster than the broader node ecosystem. Ultimately, the network’s readiness is determined by validator adoption rather than overall node participation.

At the same time, XRP has declined by 3.5% over the past 24 hours, falling below the $1.10 level again. It is currently trading at $1.09, with a daily trading volume of $1.54 billion.

With this decline, the $1.10 level has once again turned into resistance. Until XRP manages to reclaim and close above this level on the weekly chart, it is likely to remain a barrier to any sustained upward movement.

When evaluating XRPL node adoption, the more critical metric is not the overall 43% upgrade rate, but the fact that 89% of Unique Node List (UNL) validators—31 out of 35—are already running v3.2.0.

The XRP Ledger requires at least 80% UNL participation to consider a software version widely adopted. This means xrpld v3.2.0 is effectively already treated as the standard. Additionally, around 61% of validators using Ripple-maintained software have upgraded, according to the same dataset.

For non-UNL nodes, upgrading is still optional at this stage. However, the incentive to upgrade increases once related amendments go live. Nodes that lag behind risk losing connectivity to the network, a scenario previously seen during the v3.1.3 / Cleanup31_ upgrade cycle in late May 2026.

The v3.2.0 update officially transitions the core server branding from “rippled” to “xrpld,” in line with the XLS-0095 specification. It also reduces memory usage by 30% to 40% across nodes, lowering infrastructure costs for institutional operators.

In addition, the release enhances security, improves developer tools, and boosts network efficiency, building on earlier fixes and updates to permissioned domains and vault systems introduced in v3.1.3.

Meanwhile, the fixCleanup3_2_0 amendment remains the more urgent governance factor. So far, it has received only 17 out of 35 validator votes, equating to 48.57% support—far short of the 80% (28 votes) required for activation.

Under XRPL governance rules, support must also stay above 80% continuously for two weeks before activation can occur. Any drop below this level resets the countdown.

If approved, fixCleanup3_2_0 will introduce fixes affecting single-asset vaults, the native lending protocol, multi-purpose tokens, permissioned domains, and the permissioned decentralized exchange (DEX).

These components were originally introduced during XRPL’s 2026 amendment cycle, which included features like the Permissioned DEX (XLS-81), Token Escrow (XLS-85), Permissioned Domains (activated April 2, 2026), and the Vault Lending Protocol (XLS-65/66). As such, fixCleanup3_2_0 is designed to refine and stabilize existing features rather than introduce entirely new functionality.

For node operators and institutional participants, the key issue is no longer whether xrpld v3.2.0 has sufficient validator backing—it clearly does. The real focus now is whether support for fixCleanup3_2_0 can rise from 48.57% to the required 80%, and whether the remaining nodes will upgrade before the amendment is activated.

The validator voting trajectory is likely the more important signal for DeFi infrastructure participants on XRPL, given that the amendment impacts core systems such as vaults, lending, token standards, and permissioned trading mechanisms.

As the amendment progresses, node operators who have yet to upgrade to v3.2.0 face a shrinking window, with increasing pressure to update before network compatibility risks begin to materialize.

About The Author

ctleditor

See author's posts