XRP Ledger developers are working through multiple bug reports filed against xrpld v3.2.0 as the July 29 activation date for the fixCleanup3_2_0 amendment approaches. The reports, posted on the XRPLF GitHub, run from performance regressions to nodes that never finish syncing. 499 of 843 nodes (59.69%) now run 3.2.0, and validator support for the amendment is above the 80% threshold it needs.
The XRP Ledger community is progressing work on multiple bug reports related to xrpld v3.2.0, aiming to implement the fixCleanup3_2_0 amendment on July 29. The problems span performance regressions to synchronization failures, even as operators keep migrating their nodes to the latest release.
Reports point to a performance regression in 3.2.0
One report describes nodes that, after upgrading from xrpld 3.1.3 to 3.2.0, gradually fall behind the validated ledger on hardware that previously kept pace with mainnet consensus. Going back to 3.1.3 fixes the problem, and the reporter called it "a performance regression in 3.2.0."
Another report claims xrpld 3.2.0 on Windows 10 never progresses beyond the "connected" server state, despite roughly 30 peers available to sync with and 35 trusted validators. Rather than joining the network's current ledger, the node keeps closing its own ledgers going back to genesis. That machine ran rippled without problems before the migration to xrpld, according to the reporter.
Validators hit stalled ledger downloads and key mismatches
A separate issue affects a mainnet validator, where 3.2.0 does not successfully download ledger data from peers and cannot move past "server_state: connected" to "syncing," "tracking," or "full." The reporter observed that ledger acquisition ran slower than on xrpld 3.1.3-1, taking around 13 minutes from an empty datastore to full, and suspected a regression.
Developers are also examining a validator public keys report, where the service showed the new validator's key while server_info still returned the key of the previously migrated validator.
Adoption climbs as the amendment nears its activation window
XRPL validator Vet encouraged operators to upgrade, warning on X that in less than one week all nodes running versions below 3.2.0 will experience service interruptions and asking them to remind exchanges and projects to update as well.
According to XRP Ledger Explorer, 499 of 843 nodes (59.69%) now run version 3.2.0, while 303 nodes (36.24%) remain on 3.1.3. Validator adoption has reached 65.77% with 98 validators upgraded. The fixCleanup3_2_0 amendment holds 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.
Source: CoinGape
Trading involves risk.
Risk Disclaimer
