XRPL 3.2.0 Drops, Bugs Drop Harder: Node Operators Report Sync, Config Crashes 🐛

Node operators have flagged significant bugs in the XRP Ledger's newly released core server software "xrpld" version 3.2.0, publishing issue reports on the project's GitHub repository within days of the June 15 launch. The upgrade had introduced performance enhancements, memory optimizations, security improvements, and a rebranding of the server software from "rippled" to "xrpld." Developers and the XRP Ledger Foundation are reviewing the reports, several of which remained pending as of the latest updates.

The most prominent complaint came from a node operator who reported that version 3.2.0 failed to sync with the network. According to the GitHub issue, posted on June 18, the software remains in a "connected" server state and does not download any ledger data, even though the same machine was able to fully sync when running version 3.1.3. The sync issue report is still listed as pending.

A second bug report, filed shortly after release, described a configuration parser crash. The report stated that configuration files containing inline comments can cause the server to crash during parsing, producing a "BadLexicalCast" error. Developers identified the cause as the legacy configuration parser failing to strip comments from inputs before processing. The XRP Ledger codebase is maintained publicly on GitHub, and community members have continued to file additional memory usage concerns tied to the new build. Token $XRP trades on numerous global exchanges, though the bug reports do not affect on-ledger settlement or consensus, which are handled separately from the reference server implementation.