The transition to version 3.2.0—which rebranded the server software from "rippled" to "xrpld"—was intended to deliver 30% to 40% memory reductions and improved performance. Instead, GitHub repositories are filling with reports of nodes failing to synchronize with the network, often remaining stuck in a "connected" state. Operators found that downgrading to version 3.1.3 restored functionality, highlighting a specific instability in the new build.
Beyond synchronization, the legacy configuration parser has proven problematic, crashing servers when it encounters inline comments in configuration files. Further investigation by project contributors revealed deeper flaws affecting transaction relay calculations, validator list distribution, and consensus routing. Specifically, nodes are currently failing to send validator information to outbound peers, and transaction relay logic is inadvertently limiting the number of connected peers.
While maintainers have confirmed several of these bugs, they emphasize that the network has avoided a total outage. The XRP Ledger Foundation continues to review reports involving resource charging mechanisms and potential integer overflow risks, though no timeline for a corrective patch has been established.
Comments (0)
No comments yet. Be the first!