XRPL v3.2.0 Hits a 3.2.0-Sized Snag Just 2 Days Before the July 29 Deadline 🐛

The XRP Ledger community is working through multiple bug reports tied to xrpld v3.2.0 as the July 29 activation window for the fixCleanup3_2_0 amendment approaches, with issues ranging from performance regressions to synchronization failures logged on the XRPLF GitHub. One reporter who upgraded from xrpld 3.1.3 to 3.2.0 said the newer release is "slowly lagging behind the XRP Ledger mainnet consensus," with nodes that previously kept pace on the same hardware now "gradually fall behind the validated ledger." Downgrading back to version 3.1.3 resolved the issue, which the reporter described as "a performance regression in 3.2.0."

A separate report describes an xrpld 3.2.0 node on Windows 10 that never advances past the "connected" server state. The node maintained around 30 stable peers, loaded a valid UNL containing 35 trusted validators, and received validations and proposals, yet it failed to reach syncing or tracking. Instead of joining the current network ledger, the node continued closing its own ledgers from the network's genesis, even though the same machine had previously run rippled without issue.

The accumulating reports come as node operators continue migrating to v3.2.0 ahead of the July 29 amendment target, and the community is coordinating fixes through the XRPLF GitHub repository. Each of the three figures cited in the bug reports — the 3.1.3 and 3.2.0 version numbers, the 30-peer count, and the 35 trusted validators in the UNL — reflects the conditions described by the individual reporters rather than any official benchmark. The fixCleanup3_2_0 amendment remains the scheduled activation tied to the v3.2.0 release cycle. Community developers are continuing to triage the open issues on GitHub as the deadline draws near.