A freshly filed bug report shows XRP Ledger's v3.2.0 software logging one validator key while running another, as roughly 30% of nodes adopt the rebranded server. Key Points: A node operator
A freshly filed bug report shows XRP Ledger's v3.2.0 software logging one validator key while running another, as roughly 30% of nodes adopt the rebranded server.
- A node operator reported that v3.2.0 logs a migrated validator's new key while the server still runs the old one.
- The flaw appears on Ubuntu 22.04 when an existing validator token is added to a live RPC node.
- Adoption of the upgrade sits near 30%, with most operators still on the prior build.
The defect, filed under issue #7581 on the project's GitHub tracker, appears after an operator migrates an existing validator onto an already running RPC node and then restarts the service. The service log reports the migrated validator's new identity, while the server_info endpoint keeps returning the older key that sits in the local wallet.db file. The two records no longer agree.
Reproducing the split takes little effort. The operator says adding an existing validator token to an active node and restarting the server triggers it on Ubuntu 22.04, a sequence common during routine migrations.
Also Read:Is The Anthropic Perp Sell-Off A Warning For Pre-IPO Crypto Bets?
Validator identity sits at the center of how the XRP Ledger agrees on each new ledger. A node's proposals carry weight only when other servers trust its key through their unique node lists, so a stale or mismatched identity can confuse anyone reviewing the machine. A confused log can slow that trust.
So far the mismatch has caused no outage. Even so, it lengthens a run of defects that developers have flagged since the mid-month release, from sync failures to a configuration parser crash.
The reporter proposed a fix, asking that the service logs print the key the server actually uses, or show the derived and active keys together. No maintainer has been assigned to the report yet. Several earlier filings have already been confirmed as bugs and queued for review, while others stay open as contributors weigh them.
Uptake of the release stays slow. About 30% of nodes now run version 3.2.0, while most operators remain on the prior 3.1.3 build, according to public network data.
The rollout began on Jun. 15, when the update renamed the core software from rippled to xrpld and pledged memory savings of 30% to 40%. Operators have since reported sync breaks, relay miscalculations, and now the key mismatch across the fresh build, with no patch issued so far. Stragglers also risk an amendment-blocked state once validators ratify fixCleanup3_2_0, the cleanup change that Ripple has already supported in the ongoing vote.
Read Next:Mane City Mobile Lands On iOS And Android In 100+ Countries
