XRP Ledger Nears Governance Threshold as Validators Rally Behind xrpld v3.2.0

More than half of the trusted validators securing the XRP Ledger have now adopted its latest software release, xrpld v3.2.0, moving the network a step closer to a protocol upgrade that requires broad operator consensus before it can take effect. According to data from XRP Ledger Explorer, 84 trusted validators, or 55.63% of the validator set, are currently running the new version, alongside 353 nodes, representing 42.12% of the wider network.

The figures mark a notable shift in operator sentiment, though the network’s governance rules set a considerably higher bar for activation than a simple majority. Under the XRP Ledger’s amendment process, any protocol change must secure support from more than 80% of trusted validators for two consecutive weeks before it can be formally activated, meaning roughly another quarter of the validator set still needs to migrate.

By comparison, the previous release, version 3.1.3, remains in use on 58 validators, or 38.41% of the set, and on 440 nodes, equivalent to 52.51% of the network. Trusted validators approve protocol changes on the XRP Ledger, while ordinary nodes follow the decisions reached by the trusted validator list, giving the migration figures a direct bearing on how quickly the upgrade can proceed.

A rebrand and a security overhaul

The xrpld v3.2.0 package brings more than incremental maintenance. Its most visible change is the formal renaming of the network’s core server software from rippled to xrpld, implemented under the XLS-0095 proposal. From 15 June, the transition altered configuration paths, server metadata, database directory locations and version-naming conventions, obliging validator operators and node administrators to update their deployment scripts and server configurations to complete the migration.

Attached to the release is a separate amendment, fixCleanup3_2_0, which according to the release documentation addresses security issues across several newer XRP Ledger features, including Single Asset Vaults, the Lending Protocol, permissioned decentralised exchanges, Multi-Purpose Tokens and permissioned domains. The amendment also introduces new invariant checks intended to stop deleted accounts from leaving residual data on the ledger, a fix aimed at improving overall ledger consistency.

Separately, the update allows developers and users to retrieve XRP Ledger protocol information and server definitions without running a full server, a change designed to ease integration for wallets, APIs, blockchain explorers and other automated services that rely on the network’s infrastructure.

Amendment support still trails activation threshold

Despite the rising uptake of the software itself, support for the fixCleanup3_2_0 amendment lags well behind the level needed for activation. Network data cited by XRP Ledger Explorer puts current backing for the amendment at roughly 40%, half the 80% threshold required under the network’s consensus rules.

The gap underscores a distinction that matters for institutions monitoring the network’s governance: adopting the underlying xrpld software is a separate step from voting in an amendment that changes ledger rules. Developers are continuing to monitor validator migration as the process unfolds, with the pace of adoption likely to determine how quickly the security fixes bundled into fixCleanup3_2_0 can be brought into force.

Read more: Ripple Wins Full MiCA Licence in Luxembourg as XRP ETF Inflows Hit Eight Weeks