XRP Ledger v3.2.0 Node Migration Triggers Pubkey Mismatch, Upgrade Rate Stalls At 30%

The XRP Ledger (XRPL) v3.2.0 upgrade has again caused concerns among node operators, who highlighted a network defect. The scrutiny comes as node migration of validators resulted in discrepancy in public key information between the service log and node data.

XRP Ledger Migration Shows Critical Flaws

The above-mentioned issue was filed on GitHub under report #7581, “Service log file shows validator pubkey other than what is used.” The complaint states that the issue arose when they migrated an existing validator to an existing RPC node with XRP Ledger v3.2.0 in place.

After migration, the validator said, “the service log shows the correct new validator pubkey, however the actual server is running with the old pubkey stored in wallet.db.”

Moreover, the report explained that just adding an existing validator token to an active RPC node and restarting the server was enough to reproduce the behavior. Earlier, last week, other operators also flagged several bugs in the latest XRPL mainnet upgrade.

Under the expected outcome on XRP Ledger, the operator states that “both service logs and server_info should return the same validator pubkey.” The reported result, however, had the public key of the migrated validator token in the service log. Meanwhile, the older validator key stored locally remained in the server_info endpoint.

This flaw is affecting XRP Ledger version 3.2.0 for nodes running Ubuntu 22.04. As a temporary measure, the operator suggested that the logs should show the validator key, which is actually used by the server. On the other hand, the validator noted that the logs could present both the derived and active keys so as not to cause confusion during migrations.

XRPL v3.2.0 Adoption Remains Low

The report came out days after XRP Ledger v3.2.0 was launched which rebranded the key server software in the system from “rippled” to “xrpld” on June 15. In addition, it rolled out the fixCleanup3_2_0 amendment. It is now in the process of being voted on by the validators.

However, the most recent release was not well adopted, according to code data. As of this writing, around 30% of the nodes are running v3.2.0, per XRPScan. In the meantime, 61% of node operators are still running v3.1.3.

Support for the fixCleanup3_2_0 amendment with 14.29% of validators has also been low so far despite support from Ripple. Now, the operators are expected to have completed the upgrades before the amendment is activated to avoid the amendment-blocked status.