Particle.news

XRP Ledger Tops 55% Validator Upgrade but Security Amendment Lacks Supermajority

Activation of the bundled security fixes is stalled because the network still needs over 80% validator backing for two consecutive weeks before the amendment can turn on.

Overview

  • About 84 trusted validators, or roughly 55.6% of the validator set, have installed xrpld v3.2.0 and the release runs on about 42% of all network nodes, showing clear but incomplete uptake.
  • The v3.2.0 package officially renames the core server from rippled to xrpld and moves configuration and database paths, so operators must update deployment scripts and file locations to complete migration.
  • The fixCleanup3_2_0 amendment bundles security fixes for Single Asset Vaults, the Lending Protocol, permissioned decentralized exchanges, Multi-Purpose Tokens and new invariant checks to stop residual ledger data.
  • Amendment support sits at roughly 40%, far below the more-than-80% supermajority the ledger requires for two consecutive weeks, so the changes cannot activate yet.
  • Developers are tracking migration problems that operators must fix—for example, GitHub issue #7581 reports a validator key mismatch between logs and the running server—and those operational gaps must be closed before exchanges and DeFi services can rely on the upgrade.