The XRP Ledger community has reported a growing list of software issues after the June 15 release of xrpld version 3.2.0, even as only 26% of network nodes have upgraded to the new software. Summary XRP Ledger’s latest xrpld upgrade has triggered multiple bug reports, including node synchronization failures. Developers identified issues affecting transaction relays, validator distribution, consensus routing, and ledger tracking. Despite ongoing investigations, maintainers report no network-wide disruption and only 26% node adoption. According to reports published on the XRP Ledger project’s GitHub repository, developers and node operators have identified synchronization failures, configuration parsing problems, and several networking-related bugs following the rollout of the latest server software update. The release introduced performance improvements, security enhancements, memory optimizations, and officially renamed the XRP Ledger server software from “rippled” to “xrpld.” Several bugs have surfaced after the xrpld rollout Among the most serious reports, a node operator stated on GitHub that a server running xrpld version 3.2.0 failed to synchronize with the XRP Ledger network. According to the issue report, the server remained stuck in a “connected” state and did not download ledger data, while the same machine successfully synchronized when downgraded to version 3.1.3. The issue, submitted on June 18, remains open at the time of writing. Elsewhere in the repository, another developer reported that configuration files containing inline comments could cause the server to crash during parsing. According to the report, the issue stemmed from the legacy configuration parser, which failed to properly strip comments in certain single-value fields and triggered a “BadLexicalCast” error. GitHub records show additional bug reports filed within days of the release. Project maintainers have categorized several of them as confirmed bugs and assigned them for review. Reported issues include peer-to-peer communication behavior, message compression handling, resource charging rules, amendment processing, message parsing policies, and consensus-related routing logic. While maintainers continue investigating those reports, the issues emerged shortly after community discussions highlighted expected memory reductions of 30% to 40% and other performance gains associated with the upgrade. Developers identify networking and validation concerns Beyond the synchronization and parser-related problems, XRP Ledger developers have documented several technical flaws affecting node operations and transaction propagation. According to issue reports on GitHub, developers identified a transaction relay calculation problem that may cause transactions to be relayed to fewer peers than intended. Separate reports describe a resource charging mechanism that records only the highest fee observed while discarding earlier fee data. Additional findings involve validator list distribution. According to developers, validator information is currently sent only to inbound peers, leaving outbound peers excluded from the process. Several reports also focus on validation and consensus logic. Developers flagged a potential unsigned integer overflow risk during ledger sequence validation and documented inconsistencies involving transaction routing flags. Another issue report highlighted broken proposal node identifiers associated with ephemeral keys. In ledger tracking systems, developers reported logic gaps that could leave nodes in an indeterminate state for extended periods. Some of those findings have already been classified as bugs, while others remain under review by project maintainers. The XRP Ledger Foundation and project contributors continue to assess the reported issues through the network’s open-source development process. According to the current GitHub reports, none of the identified bugs have caused a network-wide outage or disruption, and investigations into the reported flaws remain ongoing.
