The XRP Ledger community is reporting a growing number of software issues after the release of xrpld version 3.2.0 on June 15. Despite the update, only about 26% of network nodes have upgraded so far.
The new version introduced several improvements, including better performance, stronger security, lower memory usage, and a new name change from “rippled” to “xrpld.” However, developers and node operators have also discovered a number of bugs.
One of the biggest problems involves node synchronization. A node operator reported that a server running version 3.2.0 could connect to the XRP Ledger network but could not download ledger data or fully synchronize. When the operator switched back to version 3.1.3, the server worked normally again. The issue is still being investigated.
Another bug affects configuration files. Developers found that certain inline comments in configuration settings can cause the server to crash due to a parsing error.
Several other issues have also been reported, including problems with peer-to-peer communication, message compression, transaction relays, validator distribution, consensus routing, amendment processing, and ledger tracking.
Developers also identified a problem that may cause transactions to be sent to fewer network peers than intended. Other reports point to issues with validator information sharing, transaction routing logic, and possible risks during ledger validation.
Some of these problems have already been confirmed as bugs and assigned for review, while others are still under investigation.
Despite the growing list of reports, project maintainers say there has been no network-wide outage or major disruption. The XRP Ledger Foundation and contributors continue to review and address the issues through the project’s open-source development process.
