XRPL v3.2.0 reaches 66% validator adoption ahead of July 29 amendment deadline

Adoption across the network

The latest figures indicate that XRPL operators have continued installing v3.2.0 since its June rollout, though a significant share of the network remains on older software. Version 3.1.3 is still used by 42 validators, representing 28% of tracked validators. At the node level, 323 of the 825 observed nodes, or 38.41%, are still on that prior release.

Software rollout and amendment approval are distinct on XRPL. Running v3.2.0 gives operators access to the newest fixes, but consensus-level changes only become binding if an amendment wins enough validator support and maintains it for the required period.

Amendment support stays above threshold

The amendment tied to this release, fixCleanup3_2_0, has already cleared the voting bar. XRPL governance data shows 85.71% support, with 30 validators voting in favor and five against. Under XRPL rules, amendments need backing from at least 80% of trusted validators for two consecutive weeks before they can take effect.

Based on current voting, fixCleanup3_2_0 is scheduled to activate on July 29, 2026 at 09:57 UTC. That timeline is not final unless support remains at or above the 80% threshold throughout the countdown. If backing drops below that level, the two-week timer would restart.

Compatibility risks for operators

XRPL validator Vet has called on node operators to upgrade before the amendment activates. Operators who continue using unsupported versions risk becoming amendment-blocked once the new rules go live. In that situation, servers may no longer be able to determine the valid state of the ledger under the updated protocol.

The approaching date therefore matters not only for validator voting but also for infrastructure compatibility. Even with the amendment currently on track, mainnet behavior will not change until the waiting period concludes successfully.

What v3.2.0 changes

The v3.2.0 release is framed as a maintenance and cleanup update rather than a major product launch. According to the official release notes, it includes fixes affecting Single Asset Vaults, the Lending Protocol, the Permissioned decentralized exchange, Multi-Purpose Tokens, and Permissioned Domains.

For Single Asset Vaults, the update addresses accuracy and rounding issues tied to the way deposits and shares are calculated. Changes to the Lending Protocol correct related accounting behavior. The Permissioned DEX and Permissioned Domains also receive fixes for problems identified after their earlier rollout.

The release includes an operational change as well: the core server software is being renamed from “rippled” to “xrpld.” That shift requires configuration updates and may require operators to adjust directories, scripts, and server metadata as they move from rippled.cfg to xrpld.cfg.

More broadly, v3.2.0 is described as part of an ongoing maintenance effort. It retires amendments that have been active for more than two years and continues work on splitting the libxrpl codebase into smaller modules intended to make future development easier.

With the amendment vote still above the required threshold and the activation date nearing, attention is now split between validator support and software adoption. The proposal remains on course for July 29, but only if backing holds through the end of the countdown and more operators complete their upgrade in time.