Headline: XRP Ledger’s xrpld 3.2.0 rollout surfaces multiple node bugs as adoption remains low
The XRP Ledger community has begun uncovering a string of software issues after the June 15 release of xrpld version 3.2.0 — an upgrade that officially renames the server software from “rippled” to “xrpld” and promises security, performance and memory improvements. As of writing, just 26% of network nodes have upgraded, and developers and node operators are filing several bug reports on the project’s GitHub repository.
What went into 3.2.0
- The update introduced performance and memory optimizations (community discussions projected 30–40% memory reductions), security enhancements, and other server improvements alongside the name change.
Problems reported after the rollout
Multiple issues have been raised by maintainers, node operators and contributors. Key reports logged on GitHub include:
- Synchronization failure: One operator reported a server running xrpld 3.2.0 stuck in a “connected” state without downloading ledger data. The same machine synchronized normally after reverting to v3.1.3. That issue was submitted on June 18 and remains open.
- Configuration parser crash: Configuration files with inline comments can trigger crashes during parsing. The legacy parser failed to strip comments in certain single-value fields, causing a “BadLexicalCast” error.
- Transaction relay shortfalls: A relay calculation bug may cause transactions to be relayed to fewer peers than intended, potentially affecting transaction propagation.
- Resource charging bug: The fee-recording mechanism reportedly only retains the highest fee observed and discards earlier fee data, which could distort resource accounting.
- Peer/validator distribution gap: Validator list information is being sent only to inbound peers, leaving outbound peers uninformed.
- Consensus and validation concerns: Reports flag an unsigned integer overflow risk during ledger sequence validation, inconsistencies in transaction routing flags, and broken proposal node identifiers tied to ephemeral keys.
- Networking and message handling: Additional issues cover peer-to-peer communication behavior, message compression handling, message parsing policies, and consensus-related routing logic.
- Ledger-tracking gaps: Some logic gaps could leave nodes in indeterminate states for extended periods.
Project status and impact
- Several reports have already been classified as confirmed bugs and assigned to maintainers for review; others remain under investigation.
- The XRP Ledger Foundation and contributors are addressing the findings through the project’s open-source workflow.
- According to the current GitHub records, none of the reported issues have caused a network-wide outage or disruption so far.
Why it matters
The xrpld 3.2.0 release targets important resource and performance gains, but the newly reported defects underscore the challenges of rolling out major node software upgrades across a distributed network. With only a quarter of nodes upgraded, the community is watching closely as maintainers triage and patch the problems to avoid fragmentation or degraded node behavior as adoption increases.
Developers and node operators are encouraged to follow the GitHub issue tracker for updates and to report any additional anomalies they encounter during testing or production deployments.
Read more AI-generated news on: undefined/news
