XRP Ledger upgrade exposes multiple software bugs as adoption lags
The XRP Ledger community is grappling with a wave of software issues after the June 15 release of xrpld v3.2.0 — the update that officially renames the server from “rippled” to “xrpld” and promises performance, security, and memory gains. So far just 26% of network nodes have upgraded, and developers and node operators have reported a variety of problems on the project’s GitHub since the rollout.
What’s gone wrong
- Synchronization failures: One operator reported that a server running xrpld v3.2.0 became stuck in a “connected” state and did not download ledger data. The same machine synced normally after being downgraded to v3.1.3. That issue was filed on June 18 and remained open at the time of reporting.
- Configuration parser crash: Config files with inline comments can crash the server during parsing. The legacy configuration parser failed to strip comments in certain single-value fields, triggering a “BadLexicalCast” error.
- Networking and consensus bugs: Multiple reports describe peer-to-peer communication problems, message compression handling issues, message parsing policy quirks, and consensus-related routing logic concerns.
- Transaction propagation and resource charging: Developers flagged a relay calculation defect that may send transactions to fewer peers than intended, plus a resource charging mechanism that only preserves the highest observed fee while discarding earlier fee records.
- Validator and validation issues: Validator list distribution currently appears to be sent only to inbound peers, excluding outbound peers. Other reports document a potential unsigned integer overflow risk during ledger sequence validation, inconsistencies in transaction routing flags, and broken proposal node identifiers tied to ephemeral keys.
- Ledger tracking gaps: Some ledger-tracking logic can leave nodes in an indeterminate state for extended periods.
Scope and status
Project maintainers have labeled several reports as confirmed bugs and assigned them for review; others remain under investigation. These findings surfaced even as the community expected 30–40% memory reductions and other performance improvements from the upgrade. According to current GitHub notes, none of the reported issues have caused a network-wide outage or disruption. The XRP Ledger Foundation and contributors are continuing to assess and remediate the problems through the network’s open-source development process.
Why it matters
Upgrades to core node software are critical to network health and decentralization. With just a quarter of nodes upgraded and several edge-case bugs reported, operators are proceeding cautiously while maintainers work through fixes. The outcome of these investigations will determine whether the performance and security gains touted in v3.2.0 can be realized safely across the network.
Developers and node operators are tracking the ongoing discussion and fixes on the XRP Ledger GitHub repository.
Read more AI-generated news on: undefined/news
