XRP Ledger Nodes Face Performance Issues Ahead of July 29 Upgrade Deadline
The XRP Ledger community is facing new bug reports as the July 29 deadline to implement the fixCleanup3_2_0 amendment approaches. Despite node operators' efforts to migrate to the latest release, issues have emerged with synchronization and performance regressions.
One problem reported on GitHub is that xrpld v3.2.0 nodes are slowly lagging behind the XRP Ledger mainnet consensus after upgrading from version 3.1.3. Going back to the previous version fixes the issue, suggesting a performance regression in 3.2.0.
Another report claims that xrpld v3.2.0 on Windows 10 never progresses beyond the 'connected' server state, failing to sync or track despite having peers and trusted validators. A Ripple-backed validator also faces issues downloading ledger data from peers on mainnet.
Developers are addressing these problems in time for the July 29 deadline, which is crucial for maintaining network stability. With only a week left before the upgrade deadline, node operators are urged to update their nodes to avoid service interruptions.