XRP Ledger’s v3.2.0 software has reached 66% validator adoption, with 99 validators now running the release as the network approaches a July 29 amendment activation. Summary XRP Ledger v3.2.0 now runs on 66% of tracked validators and 57.33% of nodes. The fixCleanup3_2_0 amendment holds 85.71% support ahead of its July 29 activation. The update fixes vault, lending, and permissioned DEX issues while renaming rippled to xrpld. According to recent XRPL Explorer data, 481 nodes, or 57.33% of the tracked network, have installed v3.2.0. The figures show that the latest software has gained ground since its June rollout, although a sizeable share of operators remain on the previous release. Version 3.1.3 still runs on 42 validators, equal to 28% of the validator set covered by the tracker. Another 323 nodes, representing 38.41% of the 825 observed nodes, also continue to use the older software. Software adoption and amendment approval are separate processes on the XRP Ledger. Installing v3.2.0 gives operators access to the latest fixes, while an amendment requires support from at least 80% of trusted validators for two consecutive weeks before its rules can take effect. The fixCleanup3_2_0 amendment has already crossed that voting threshold. XRP Ledger governance data shows 85.71% support, with 30 validators voting in favor and five opposing the proposal. Having secured the required backing, the amendment is scheduled to activate on July 29, 2026, at 09:57 UTC. Support must remain at or above 80% throughout the countdown; otherwise, the network’s two-week timer will restart. Validator backing keeps the amendment on schedule XRPL validator Vet has urged node operators to update their software before activation so their infrastructure remains compatible with the amended protocol. Operators using unsupported versions can become amendment-blocked once new rules go live, preventing their servers from determining the valid state of the ledger. Unlike a feature release built around new user-facing products, fixCleanup3_2_0 combines maintenance changes for functions already available on XRPL. The official v3.2.0 release announcement identifies fixes covering Single Asset Vaults, the Lending Protocol, the Permissioned decentralized exchange, Multi-Purpose Tokens, and Permissioned Domains. For Single Asset Vaults, the package addresses accuracy and rounding issues that can affect how deposited assets and shares are calculated. Lending Protocol changes correct related accounting behavior, while the Permissioned DEX and Permissioned Domains receive fixes for problems found after their earlier implementation. Amendment voting allows validators to decide whether those consensus-level changes should become binding across the ledger. Even though v3.2.0 is already running on most tracked validators, the amendment will not alter mainnet behavior until the waiting period ends successfully. Crypto.news reported earlier in July that fixCleanup3_2_0 had entered its final activation window after approval moved above 80%. The current 85.71% reading leaves a buffer of 5.71 percentage points, but XRPL rules still require support to hold until the scheduled activation time. XRPSCAN’s amendment tracker lists fixCleanup3_2_0 as a proposal introduced through version 3.2.0. Its status also means operators must install compatible software even though running the release does not automatically count as an affirmative amendment vote. Version 3.2.0 prepares XRPL infrastructure for new activity Released in mid-June, v3.2.0 has also changed the name of the XRP Ledger’s core server software from “rippled” to “xrpld.” The rename follows XLS-0095, a technical proposal intended to align the server’s identity more directly with the XRP Ledger. The change affects more than the executable’s name. Under XRPL’s migration instructions, operators moving from version 3.1.3 must update the configuration file from rippled.cfg to xrpld.cfg, along with related paths and deployment settings. Node operators may also need to revise database directories, package references, scripts, service definitions, and server metadata. XRPL documentation provides a migration process designed to preserve existing node data while replacing the former server naming conventions. Beyond the rename, the XRP Ledger development team describes v3.2.0 as a cleanup and maintenance release. The software retires amendments that have remained active for more than two years and continues work to divide the libxrpl codebase into smaller modules, which can make future development and maintenance easier. Those infrastructure changes arrive while projects are testing new payment uses on the ledger. Ripple-backed t54.ai recently reported that XRPL had processed more than 1 million AI-driven payments through the x402 protocol and launched an AI Hub for agents, developers and payment services. According to t54.ai, the hub was developed with support from Ripple developers and the XRP Ledger Foundation. It collects AI projects, autonomous agents, developer tools, payment services and technical resources in one place for teams building XRPL applications. With eight days remaining before the scheduled amendment date, validator voting has kept fixCleanup3_2_0 on course. The remaining task falls to node operators still running older software, as the July 29 activation will apply the maintenance rules across the XRP Ledger if approval stays above the required level.
