The XRP Ledger is edging closer to a major software upgrade after a surge in validator adoptions, but it still needs broader backing before the changes can be activated.
What’s happening
- As of now, 84 trusted validators — 55.63% of the validator set — are running xrpld v3.2.0, according to XRP Ledger Explorer. The release is also deployed on 353 network nodes (42.12% of nodes).
- By contrast, xrpld v3.1.3 remains active on 58 trusted validators (38.41%) and 440 nodes (52.51%).
Why it matters
Trusted validators on the XRP Ledger are the entities that approve protocol amendments; ordinary nodes then follow those decisions. Under ledger governance, an amendment needs support from more than 80% of trusted validators for two consecutive weeks to be eligible for activation. At the current pace, roughly another quarter of validators must switch to v3.2.0 before the upgrade can approach that activation threshold.
What’s in xrpld v3.2.0
Released as xrpld v3.2.0, the package brings infrastructure updates, developer improvements and bug fixes. One headline change is the official renaming of the main server software from rippled to xrpld (per XLS-0095). Starting June 15 the update also changed configuration paths, server metadata, database directory locations and version naming conventions. That means validator operators and node admins need to update deployment scripts and server configurations as part of the migration.
The fixCleanup3_2_0 amendment
The xrpld release was paired with the fixCleanup3_2_0 amendment, which bundles several security-related fixes impacting Single Asset Vaults, the Lending Protocol, permissioned decentralized exchanges, Multi-Purpose Tokens (MPTs) and permissioned domains. It also introduces new invariant checks to prevent deleted accounts from leaving residual ledger data, improving ledger consistency. Another practical change lets developers and services read XRPL protocol information and server definitions without operating a full server — simplifying integrations for wallets, APIs, explorers and other automated tools.
Adoption hurdles and security context
Despite growing software adoption, support for the fixCleanup3_2_0 amendment itself sits at roughly 40% — well below the supermajority required for approval. Ripple has publicly backed the amendment, and the XRP Ledger Lending Protocol recently cleared an independent security audit, which bolsters confidence in the lending-related fixes included in the proposal.
Operational issues to watch
Developers are monitoring migration-related issues. A tracked GitHub report (#7581) describes a case where the service log showed the new validator public key while the running server continued using an older key stored in the wallet database. The discrepancy appears to stem from migration behavior rather than the protocol itself, highlighting an operational edge case node operators should address as adoption grows.
Bottom line
xrpld v3.2.0 adoption is accelerating and introduces meaningful security and developer improvements, but the upgrade and its attached amendment still need broader validator support and some operator housekeeping before they can be fully activated.
Read more AI-generated news on: undefined/news
