XRP Ledger’s Big Upgrade Has a Problem — Here’s What Developers Found

TLDR

XRP Ledger released core server upgrade xrpld v3.2.0 on June 15, promising 30–40% memory reduction Community developers flagged multiple bugs on GitHub within days of release One node failed to sync after upgrading, while running fine on the previous version Bugs include configuration parser errors, transaction relay flaws, and validator distribution issues Only 26% of nodes have upgraded; no network-wide outage has been reported

---

The XRP Ledger community has raised multiple bug reports after the June 15 release of xrpld version 3.2.0, the latest update to the network’s core server software.

XRP News: XRP Ledger 3.2.0 Upgrade Status
Ripple voted in favor of fixCleanup3_2_0 amendment
26% nodes updated with XRP Ledger (XRPL) v3.2.0 release

Full activation requires sustained 80% support from validators over two weeks.@XRPLOperations @Vet_X0 urging validators… pic.twitter.com/Zm2KLjWqBH

— Rednirav (@CryptoRednirav) June 19, 2026

The upgrade was expected to bring performance improvements and a 30% to 40% reduction in memory usage. It also renamed the server software from “rippled” to “xrpld” and included security improvements.

However, developers and node operators began posting issues to the project’s GitHub repository shortly after the release.

Sync Failure and Parser Errors

One node operator reported that a server running version 3.2.0 failed to download any ledger data after upgrading. The server stayed in a “connected” state but could not sync. The same hardware had synced without issues on version 3.1.3. That report was filed on June 18 and remains open.

A separate report found that inline comments in configuration files can cause the server to crash on startup. The legacy parser fails to strip comments from certain fields, producing a “BadLexicalCast” error.

Project maintainers have confirmed several of these as bugs and flagged them for review.

Transaction and Validator Issues

Developers also flagged a flaw in how transactions are relayed to peers. A calculation error limits how many peers receive a transaction, which could result in under-relaying.

The resource charging system was also flagged. It only records the highest fee and drops earlier ones, which developers say is incorrect behavior.

A validator list distribution problem was also reported. Validator information is currently sent only to inbound peers, leaving out outbound connections. This creates an imbalance in how validator data is shared across the network.

Developers flagged a risk of unsigned integer overflow during ledger sequence checks. Reports also pointed to inconsistent routing flags for transactions and broken node identifiers when using ephemeral keys.

Another report described a logic gap in ledger tracking that can leave a node in an unknown state with no clear path to recovery.

Where Things Stand

As of now, none of the reported bugs have caused a network-wide outage. The XRP Ledger Foundation and open-source contributors are reviewing all filed reports through the project’s GitHub repository.

Only 26% of nodes have upgraded to version 3.2.0 so far. The remaining nodes are still running older versions.

The XRP Ledger Foundation has not issued a public statement or patch as of the time of writing. All known issues remain under active review.

The post XRP Ledger’s Big Upgrade Has a Problem — Here’s What Developers Found appeared first on CoinCentral.