The XRP Ledger community reported a growing list of software issues following the release of xrpld version 3.2.0 on June 15, even as only 26% of the network’s nodes upgraded to the new software.
summary
- The recent XRP Ledger upgrade to xrpld generated multiple bug reports, including node synchronization failure.
- Developers have identified issues affecting transaction postings, validator distribution, consensus routing, and ledger tracking.
- Despite ongoing investigations, maintainers reported no network-wide outages and the node was only 26% authorized.
According to reports published In the XRP Ledger project’s GitHub repository, developers and node operators identified synchronization failures, configuration parsing issues, and several networking-related errors after the latest server software update was rolled out.
the He releases It provided performance improvements, security improvements, and memory improvements, and officially renamed the XRP Ledger server software from “ripple” to “xrpld.”
Many errors appeared after xrpld was released
Among the more serious reports, a node operator on GitHub stated that a server running xrpld version 3.2.0 failed to sync with the XRP Ledger network.
According to the issue report, the server remained stuck in an “online” state and did not download ledger data, while the same device was successfully synced when downgrading to version 3.1.3. The case, which was filed 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 originated from the legacy configuration parser, which failed to properly strip comments in some single-valued fields and resulted in a “BadLexicalCast” error.
GitHub logs show additional bug reports were submitted within days of release. Project maintainers have classified many of them as confirmed errors and assigned them for review. Reported issues include peer-to-peer communication behavior, message compression handling, resource charging rules, modification handling, message parsing policies, and consensus-related routing logic.
While moderators continue to investigate those reports, issues emerged shortly after community discussions highlighted the expected 30% to 40% memory reductions and other performance gains associated with the upgrade.
Developers identify networking and validation concerns
In addition to synchronization and parser issues, XRP Ledger developers have documented several technical flaws affecting contract operations and transaction publishing.
According to issue reports on GitHub, developers have identified an issue with transaction migration accounting that could cause transactions to be migrated to fewer peers than intended. Separate reports describe a resource charge mechanism that records only the highest charges observed while ignoring historical charge data.
Additional outcomes include distribution of a validation checklist. According to the developers, auditor information is currently only sent to internal peers, excluding external peers from the process.
Many reports also focus on verification and consensus logic. The developers flagged the risk of unsigned integer overflow during ledger chain validation and documented discrepancies involving transaction routing flags. Another issue report highlighted broken suggestion node IDs associated with temporary keys.
In ledger tracking systems, developers have reported logic gaps that can leave nodes in an undefined state for long periods. Some of these results have already been classified as errors, while others remain under review by the project leaders.
The XRP Ledger Foundation and project contributors continue to evaluate issues reported throughout the open source network development process. According to current GitHub reports, none of the identified bugs caused a network-wide outage or outage, and investigations into the reported flaws are ongoing.
