XRP Ledger Moves Closer to xrpld v3.2.0 Upgrade

XRP Ledger is getting closer to rolling out the xrpld v3.2.0 upgrade. So far, 84 trusted validators have adopted the latest software version, representing 55.63% of the network's validator set. While this marks significant progress, the upgrade still requires support from more than 80% of validators, maintained for two consecutive weeks, before it can be officially activated.

According to data from XRP Ledger Explorer, version 3.2.0 is also running on 353 nodes, accounting for 42.12% of the network. Meanwhile, the older 3.1.3 release remains in use by 58 validators (38.41% of the validator set) and 440 nodes, which represent 52.51% of the network.

On XRP Ledger, trusted validators are responsible for approving protocol changes, while the remaining nodes follow their consensus. At the current adoption rate, roughly one-quarter of validators still need to upgrade to version 3.2.0 before the amendment process can move forward.

The new release introduces infrastructure improvements, developer-focused enhancements, and several bug fixes. One of the most notable changes is the official renaming of the core server software from rippled to xrpld, following the XLS-0095 proposal.

Since June 15, configuration paths, database locations, server metadata, and version naming conventions have all changed. As a result, validator and node operators are required to update their configurations and deployment scripts before completing the migration.

The update also includes the fixCleanup3_2_0 amendment, which delivers security improvements for Single Asset Vaults, the Lending Protocol, permissioned decentralized exchanges, Multi-Purpose Tokens, and permissioned domains. It also introduces mechanisms to prevent unnecessary data from remaining after accounts are deleted and makes it easier to access protocol information without running a full server.

However, the amendment has not yet received enough support to be activated. It is currently backed by approximately 40% of validators. Ripple has publicly endorsed the proposal, and the XRP Ledger Lending Protocol recently completed an independent security audit successfully.

Developers are also continuing to monitor issues reported during the validator migration process. One GitHub report describes a case where the logs displayed a validator's new public key while the server continued using the older key stored in the wallet database. According to the developers, this is a migration-related issue rather than a flaw in the protocol itself.