XRP Ledger v3.2.0 Faces New Bug Reports As July 29 Upgrade Deadline Nears

The XRP Ledger community is progressing work on multiple bug reports related to xrpld v3.2.0 with the goal of implementing the fixCleanup3_2_0 amendment on July 29. The problems, posted on the XRPLF GitHub, span from performance regressions to problems with synchronization, despite node operators’ ongoing migration to the latest release.

A Look At Newly Reported Issues On XRP Ledger v3.2.0

After upgrading from xrpld 3.1.3 to 3.2.0, it is reported that xrpld 3.2.0 is slowly lagging behind the XRP Ledger mainnet consensus. The nodes which were once updating the validated ledgers on the same hardware “now gradually fall behind the validated ledger.”

However, going back to the 3.1.3 version fixes the problem, according to the issue on GitHub. The reporter called it “a performance regression in 3.2.0.”

Another report claims that xrpld 3.2.0 on Windows 10 never progresses beyond the “connected” server state. Despite maintaining around 30 stable peers, loading a valid UNL with 35 trusted validators, and receiving validations and proposals, the node reportedly never reaches syncing or tracking.

But rather than joining the current ledger of the network, it continues to close its own ledgers since the network’s genesis. The reporter reported that this machine was previously able to run rippled without any problem and the problem only occurred after migration to xrpld.

One validator-related problem is that Ripple-backed XRP Ledger v3.2.0 version does not successfully download ledger data from peers on a mainnet validator. Moreover, it cannot move past “server_state: connected” to “syncing,” “tracking,” or “full” stage.

The reporter made the observation that the process of acquiring the ledger on xrpld 3.2.0 was slowed down relative to xrpld 3.1.3-1. It took around 13 minutes to complete from an empty datastore to full, so it is suspected a regression occurred.

Developers are also looking at a validator public keys report on the new XRP Ledger version. The service showed the public key of the new validator, but server_info still showed the public key of the validator that was migrated previously, resulting in a mismatch between the two.

Validator Issues Warning As July 29 Deadline Inches Closer

Meanwhile, XRPL validator Vet encouraged users to upgrade their XRP Ledger nodes to 3.2.0. He wrote on X, “Happy Hump Day to everyone, especially those who have upgraded their XRP Ledger nodes to 3.2.0!” He added, “In less than 1 Week all nodes running XRPL versions below 3.2.0 will experience service interruptions. Please update your nodes, remind exchanges and projects to update as well!”

According to XRP Ledger Explorer, 499 of 843 nodes (59.69%) are now running version 3.2.0. Whilst, 303 nodes (36.24%) remain on version 3.1.3. Adoption of validators has surged to 65.77% with 98 validators upgraded. The fixCleanup3_2_0 amendment currently has 30 of 35 trusted validators in support (85.71%), and is set to become active on 29 July 2026 at 09:57 UTC, as long as it stays above the 80% threshold.