XRP Ledger v3.2.0 Node Migration Triggers Pubkey Mismatch, Upgrade Rate Stalls At 30%
The XRP Ledger (XRPL) v3.2.0 upgrade has caused concerns among node operators after a critical flaw was discovered during node migration. The issue, filed on GitHub as report #7581, details a mismatch in public key information between the service log and node data.
According to the report, after migrating an existing validator to an RPC node running XRPL v3.2.0, the service log displayed the correct new validator pubkey, but the server continued operating with the old pubkey stored in wallet.db. The issue was reproducible by simply adding an existing validator token to an active RPC node and restarting the server.
The expected outcome is that both service logs and server_info should return the same validator pubkey. However, the reported result showed the public key of the migrated validator token in the service log while the server_info endpoint retained the older locally stored key. This flaw affects nodes running Ubuntu 22.04.
As a temporary measure, the operator suggested that logs should reflect the validator key actually in use by the server. Alternatively, logs could display both the derived and active keys to prevent confusion during migrations.
The report comes shortly after the launch of XRPL v3.2.0 on June 15, which rebranded the key server software from “rippled” to “xrpld” and introduced the fixCleanup3_2_0 amendment, now being voted on by validators.
Adoption of the latest version remains low. According to XRPScan, only 30% of nodes are running v3.2.0, while 61% still operate on v3.1.3. Support for the fixCleanup3_2_0 amendment is also low at 14.29%, despite backing from Ripple. Operators are expected to complete upgrades before the amendment is activated to avoid being placed in amendment-blocked status.