The recent upgrade of the XRP Ledger’s xrpld software to version 3.2.0 has led to a surge in bug reports, revealing synchronization failures, configuration errors, and networking issues. Despite these flaws, only 26% of network nodes have adopted the update, and no widespread network outages have been reported.
According to developer reports on the project’s GitHub repository, the most critical issue involves a node that remains stuck in a ‘connected’ state after upgrading, unable to synchronize with the ledger. Downgrading to version 3.1.3 resolved the problem. Another bug causes the server to crash when parsing configuration files with inline comments, due to a legacy parser that fails to handle certain fields correctly.
Additional problems have been identified in transaction relay calculations, which may reduce the number of peers receiving transactions. A separate flaw in the resource charging mechanism records only the highest fee, discarding earlier fee data. Validator list distribution is also affected, as information is only sent to inbound peers, excluding outbound connections.
Issues with consensus logic include a potential unsigned integer overflow risk in ledger sequence validation and inconsistent transaction routing flags. Broken proposal node identifiers tied to ephemeral keys have also been reported. In ledger tracking, logic gaps could leave nodes in an indeterminate state for extended periods.
Project maintainers have confirmed several bugs and assigned them for review. The XRP Ledger Foundation continues to investigate, but so far, no network-wide disruption has occurred.