Breaking: XRP Ledger v3.2.0 Full Upgrade Inches Closer As Validator Adoption Hits 55%
The XRP Ledger (XRPL) continues to move toward a full xrpld v3.2.0 upgrade with over 55% of all trusted validators currently running the latest v3.2.0 version. This surge follows as the network votes on an attached fixCleanup3_2_0 amendment.
Why Is The XRP Ledger v3.2.0 Validator Adoption Important?
The XRPL Explorer data indicates that 55.63% of the validator set (84 validators) are running v3.2.0. Of the network nodes, 353 (42.12%) have been upgraded to the latest software. By comparison, v3.1.3 remains active on 58 validators (38.41%) and 440 nodes (52.51%).

On the XRP Ledger, trusted validators can approve protocol changes and normal nodes will follow trusted validators. A network upgrade requires the approval of over 80% of trusted validators for continuosly two weeks. Now, the update needs only 25% more validators to migrate to the new server for successful implementation of v3.2.0.
XRP Ledger’s version 3.2.0 includes infrastructure improvements, bug fixes and developer enhancements throughout the network. One of the most significant changes is the official renaming of the main server software from rippled to xrpld, under the XLS-0095 proposal.
Starting June 15, the XRP Ledger upgrade impacted configuration paths, server metadata, database directories and version naming change. This means validators (and node operators) need to update their configurations and deployment scripts.
A Look At The Critical Lending Protocol Amendment
The release also introduces the fixCleanup3_2_0 amendment. It contains multiple security related fixes for Single Asset Vaults, Lending Protocol, permissioned decentralized exchanges (DEXs), Multi Purpose Tokens (MPTs) and permissioned domains.
It further adds new invariant checks to make sure that deleted accounts don’t leave ledger artifacts, thus enhancing ledger consistency and reliability. Furthermore, it has introduced a feature allowing for users to get XRP Ledger protocol information and server definitions without running a server. In addition, it focuses on streamlining integration for wallets, APIs, blockchain explorers and automated tools.
Meanwhile, the support for the fixCleanup3_2_0 amendment is at 40% which is far short of what is needed to activate it. Nonetheless, Ripple’s support for the amendment has induced optimism. Also, the XRP Ledger lending protocol even passed a crucial audit, which adds to the confidence in the fixCleanup3_2_0 upgrade.
However, GitHub report (#7581) raises concerns about validator migration issues. The report reads that “the service log shows the correct new validator pubkey, however the actual server is running with the old pubkey stored in wallet.db.”
For those looking for staking rewards, visit our page on Crypto Staking Platforms.











