XRP Ledger Set for Major Upgrade with Increasing Validator Support
The XRP Ledger is on the verge of activating the xrpld v3.2.0 upgrade, as more than 55% of trusted validators have embraced the new software version.
Summary
- With validator adoption for xrpld v3.2.0 exceeding 55%, the network is nearing the activation of this upgrade.
- This release introduces infrastructure enhancements, security updates, and officially renames the network’s server software from rippled to xrpld.
- The fixCleanup3_2_0 amendment has gained 40% support as developers look into ongoing validator migration challenges.
According to data from XRP Ledger Explorer, 84 trusted validators—comprising 55.63% of the validator set—are now operating on xrpld v3.2.0. This software version has also been implemented on 353 network nodes, representing 42.12% of all nodes. In comparison, version 3.1.3 still operates on 58 validators, which constitutes 38.41% of the validator set, and on 440 nodes, making up 52.51% of the network.
On the XRP Ledger, trusted validators play a pivotal role in approving protocol changes, while standard nodes comply with the directives set by the trusted validator pool. According to network governance rules, a protocol amendment requires over 80% support from trusted validators for two consecutive weeks to activate.
Currently, about another quarter of the validator set must transition to v3.2.0 for the upgrade to advance toward activation.
Latest release introduces infrastructure and security innovations
The software package released as xrpld v3.2.0 features infrastructure improvements, developer enhancements, and bug fixes throughout the XRP Ledger. Notably, it officially changes the primary server software name of the network from rippled to xrpld, in line with the XLS-0095 proposal.
Starting on June 15, the upgrade modified configuration paths, server metadata, database directory locations, and version naming conventions. Consequently, validator operators and node managers must adjust deployment scripts and server settings before completing the migration.
In conjunction with the software release, developers have introduced the fixCleanup3_2_0 amendment. Per the documentation, this amendment includes security fixes related to Single Asset Vaults, the Lending Protocol, permissioned decentralized exchanges, Multi-Purpose Tokens (MPTs), and permissioned domains.
The proposal also introduces new invariant checks aimed at preventing deleted accounts from leaving residual ledger data, thereby improving ledger consistency. Furthermore, the update allows developers and users to access XRP Ledger protocol information and server definitions without requiring a full server, making integrations for wallets, APIs, blockchain explorers, and other automated services easier.
Amendment voting still has a way to go
Although the adoption of the software by validators continues to rise, support for the related fixCleanup3_2_0 amendment remains significantly below the activation threshold. Current network data reveals that the amendment has reached only about 40% support, which is insufficient for approval.
Ripple has openly supported the amendment, enhancing confidence in the proposed changes. Additionally, the XRP Ledger Lending Protocol recently passed an independent security audit, providing further assurances regarding the lending fixes encompassed in the amendment.
Meanwhile, developers are monitoring reported issues arising during validator migrations. A GitHub issue, referenced as report #7581, outlines a scenario where the service log appropriately displayed the new validator public key, while the running server continued to use the old public key stored in the wallet database.
This discrepancy is linked to validator migration behavior rather than the protocol itself, highlighting an operational challenge that node operators should address as the adoption of xrpld v3.2.0 continues.