Headline: XRP Ledger inches closer to v3.2.0 upgrade as validator adoption passes 55%
The XRP Ledger moved another step toward activating its xrpld v3.2.0 upgrade after a majority of trusted validators began running the new software. Explorer data shows 84 trusted validators — 55.63% of the validator set — have upgraded to xrpld v3.2.0. In total, 353 network nodes (42.12% of all nodes) are now on the new release.
By contrast, xrpld v3.1.3 is still active on 58 trusted validators (38.41%) and 440 nodes (52.51%). On the XRP Ledger, trusted validators vote on protocol changes while regular nodes follow the trusted list. Per the network’s governance rules, an amendment needs support from more than 80% of trusted validators for two consecutive weeks to be activated — meaning roughly another quarter of validators must migrate before v3.2.0 is eligible for activation.
What’s in v3.2.0
Released as xrpld v3.2.0, the package bundles infrastructure upgrades, developer enhancements and bug fixes. One visible change is the official renaming of the server software from rippled to xrpld, following the XLS-0095 proposal. Starting June 15, the upgrade also introduced new configuration paths, server metadata, database directory locations and version naming conventions, so validator operators and node admins must update deployment scripts and server configs as part of migration.
Security fixes and the fixCleanup3_2_0 amendment
The release included a linked amendment, fixCleanup3_2_0, which bundles security-related fixes affecting Single Asset Vaults, the Lending Protocol, permissioned decentralized exchanges, Multi-Purpose Tokens (MPTs) and permissioned domains. It also adds invariant checks to prevent deleted accounts from leaving residual ledger data, improving ledger consistency, and enables access to protocol information and server definitions without running a full server — a convenience intended to simplify wallet, API and explorer integrations.
However, support for the fixCleanup3_2_0 amendment is still well below the activation threshold. Current network data put amendment backing at roughly 40%, far short of the >80% supermajority required. Ripple has publicly backed the amendment, and the Lending Protocol fixes have additional confidence after the protocol passed an independent security audit.
Operational issues to watch
Developers are monitoring migration-related issues reported by operators. A GitHub ticket (report #7581) describes a case where service logs showed the new validator public key but the running server continued to use the older key stored in the wallet database. The report attributes this to validator migration behavior rather than the protocol itself, underscoring that operators may need to adjust scripts or workflows during the transition.
Outlook
Adoption of xrpld v3.2.0 continues to climb, but the upgrade still needs broader validator buy-in and stronger support for the attached amendment before activation. Validator operators and node administrators should update their configurations and watch for migration reports as the network moves toward the required supermajority.
Read more AI-generated news on: undefined/news
