Key facts
- 66% of XRP Ledger validators are running the v3.2.0 software update.
- The fixCleanup3_2_0 amendment has received 85.71% validator support.
- The fixCleanup3_2_0 amendment is currently in a two-week activation period.
- The fixCleanup3_2_0 amendment is set to activate on July 29, 2026, if validator support stays above 80%.
The XRP Ledger's latest software update, version 3.2.0, is seeing increasing adoption among validators, with 66% of the trusted validator set now running the release. This migration is occurring as the network prepares for a critical amendment known as fixCleanup3_2_0.
The upgrade tracker indicates that 99 validators are currently on v3.2.0, representing 66% of the total validator set. Additionally, 481 nodes, or 57.33% of all 825 nodes, are running the latest version. However, older software versions, such as 3.1.3, are still in use by 42 validators (28%) and 322 nodes (38.38%).
XRP Ledger amendments require over 80% validator support, sustained for two consecutive weeks, to be enacted. The current statistics show that v3.2.0 adoption needs an additional 25 percentage points to reach this threshold. Version 3.2.0 introduces technical enhancements, infrastructure improvements, and developer-focused fixes, including a significant change under XLS-0095, which renames the server software from 'rippled' to 'xrpld'. Node operators are advised to update their configurations, deployment scripts, and database directories.
The fixCleanup3_2_0 amendment itself has already surpassed the necessary voting threshold, currently holding 85.71% validator support, with 30 validators voting in favor and six against. This amendment is now in a mandatory two-week activation process, scheduled to conclude on July 29, 2026, at 09:57 UTC, provided that validator support remains above 80% throughout the countdown. The amendment is described as an enhancement to existing features, aimed at resolving accuracy and rounding issues within Single Asset Vaults and Lending Protocols, as well as fixing problems related to the Permissioned DEX and Permissioned Domains.