XRP Ledger nears v3.2.0 upgrade as 55% of validators adopt

The XRP Ledger moved closer to activating its xrpld v3.2.0 upgrade after 84 trusted validators, or 55.6% of the network, adopted the latest software version, XRPL Explorer data shows.

"The service log shows the correct new validator pubkey, however the actual server is running with the old pubkey stored in wallet.db," a GitHub issue tracked under report #7581 stated, highlighting migration challenges as node operators update configuration paths and deployment scripts.

Of the network's 838 nodes, 353 (42.1%) have upgraded to v3.2.0, while v3.1.3 remains active on 58 validators (38.4%) and 440 nodes (52.5%). The protocol requires support from more than 80% of trusted validators for two consecutive weeks before an amendment can activate. The attached fixCleanup3_2_0 amendment, which includes security fixes for Single Asset Vaults, the Lending Protocol, permissioned DEXs and Multi-Purpose Tokens, has secured roughly 40% support.

Successful activation of v3.2.0 would mark the official transition from rippled to xrpld under the XLS-0095 proposal, changing configuration paths, server metadata and database directory locations. The XRP Ledger Lending Protocol recently passed an independent security audit, adding confidence to the amendment's fixes, while Ripple's public support has strengthened expectations for eventual approval.

The upgrade introduces infrastructure improvements, bug fixes and developer enhancements across the XRP Ledger. Beginning June 15, the transition impacted configuration paths, server metadata, database directories and version naming conventions, requiring validators and node operators to update their deployment scripts.

The fixCleanup3_2_0 amendment adds new invariant checks designed to prevent deleted accounts from leaving residual ledger data, improving ledger consistency. It also allows developers to access XRP Ledger protocol information and server definitions without running a full server, streamlining integrations for wallets, APIs, blockchain explorers and automated tools.

With validator adoption at 55.6%, the network needs roughly another quarter of the validator set to migrate before the upgrade can move toward activation. Developers continue monitoring the validator migration issue reported in GitHub #7581, where the service log displays the correct new public key while the running server retains the older key stored in the wallet database.

This article is for informational purposes only and does not constitute investment advice.