XRP Ledger v3.2.0 Gain Momentum Ahead of Activation

XRP Ledger upgrade nears activation as validator adoption rises

XRP Ledger's v3.2.0 rollout is gaining traction as the network prepares for the scheduled activation of the fixCleanup3_2_0 amendment on July 29, 2026. The release — which renames the core server from "rippled" to "xrpld" and delivers a package of maintenance fixes for vaults, lending, and permissioned DEX functionality — is now running on the majority of tracked validators and a clear majority of nodes. With amendment support already above the 80% approval threshold, the clock is counting down but operators running older software must update to avoid being amendment-blocked when the new rules go live.

Adoption metrics: validators and nodes

According to XRPL Explorer tracking, v3.2.0 is installed on 66% of tracked validators and on 481 nodes, representing 57.33% of the 825 observed network nodes. The older v3.1.3 remains in service on 42 validators (28% of tracked validators) and on 323 nodes (38.41% of observed nodes). These figures show steady migration toward the new release since its June rollout, but a meaningful minority of operators still run legacy software.

Why adoption and amendment approval differ

On the XRP Ledger, installing updated software and voting for an amendment are related but distinct steps. Deploying v3.2.0 gives a node operator the ability to run the updated code, but amendments require explicit validator support: the fixCleanup3_2_0 proposal must receive at least 80% backing from trusted validators for two consecutive weeks before its consensus-level rules become effective on mainnet. While most tracked validators already run v3.2.0, only affirmative votes by the validator set advance the amendment through XRPL's governance process.

Amendment status and timeline

XRPL governance data shows fixCleanup3_2_0 has secured 85.71% support, with 30 validators voting in favor and five opposing the change. That puts the proposal comfortably above the required 80% threshold, with an approval buffer of 5.71 percentage points. With the condition satisfied, the amendment is scheduled to activate on July 29, 2026 at 09:57 UTC — provided validator support remains at or above 80% for the remainder of the waiting period. If support dips below the threshold during the two-week countdown, the timer will reset and the process must restart.

Call to node operators: update before activation

XRPL validator operators such as Vet have urged node operators to update to v3.2.0 ahead of activation to keep infrastructure compatible with the amended protocol. Nodes running unsupported versions risk becoming amendment-blocked: once new consensus rules apply, servers that do not recognize the amendment cannot reliably determine the valid ledger state and may be excluded from consensus.

What v3.2.0 changes and why they matter

Rather than introducing user-facing products, fixCleanup3_2_0 is a maintenance-focused update addressing correctness and robustness across core XRPL features. The official release notes outline fixes for:

• Single Asset Vaults: corrections to rounding and accuracy that affect how deposited assets and vault shares are calculated.
• Lending Protocol: accounting fixes to ensure correct balances and operations in lending flows.
• Permissioned DEX and Permissioned Domains: bug patches that resolve issues discovered after those features were first deployed.
• Multi-Purpose Tokens and other ledger constructs that required cleanup.

These consensus-level corrections prevent subtle accounting errors and improve the reliability of higher-level applications built on XRPL.

Server rename and migration implications

v3.2.0 also implements XLS-0095 by renaming the XRPL core server executable from "rippled" to "xrpld." The change is more than cosmetic: operators migrating from v3.1.3 must update configuration filenames (for example, from rippled.cfg to xrpld.cfg), adjust file paths, service definitions, scripts, package references, and server metadata. XRPL migration documentation aims to preserve existing node data while guiding operators through the renaming and reconfiguration steps.

Infrastructure cleanup and longer-term dev goals

Beyond the immediate fixes, v3.2.0 retires amendments that have been active for more than two years and advances a modularization effort to split the libxrpl codebase into smaller, more maintainable components. These behind-the-scenes improvements are designed to simplify future maintenance, speed development cycles, and reduce the surface area for bugs.

Network activity and developer ecosystem

The timing of these infrastructure upgrades coincides with an uptick in innovative use cases on XRPL. Ripple-backed t54.ai reported more than 1 million AI-driven payments processed via the x402 protocol and launched an "AI Hub" bringing agents, developer tools, payment services, and technical resources together. The AI Hub — built with support from Ripple developers and the XRP Ledger Foundation — highlights growing demand for payments, autonomous agents, and developer tooling on XRPL.

What to watch before July 29

With eight days remaining before the scheduled amendment activation, validator voting continues to keep fixCleanup3_2_0 on track. The immediate priority for the XRPL community is clear: node operators still running older releases should upgrade to v3.2.0 now to ensure uninterrupted participation in consensus and to adopt the fixes that prevent accounting and permissioning issues. If validator backing remains at or above 80% through the countdown, the maintenance rules in fixCleanup3_2_0 will become binding and apply network-wide on July 29.

For developers, validators, and enterprises building on the ledger, the v3.2.0 upgrade reinforces XRPL's focus on secure, predictable upgrades and continued support for payments, permissioned features, and emerging uses like AI-driven transactions.