TLDR
- XRP Ledger launched core server upgrade xrpld v3.2.0 on June 15, promising 30–40% memory reduction
- Community builders flagged a pair of bugs on GitHub internal days of liberate
- One node failed to sync after upgrading, whereas working elegant on the outdated version
- Bugs encompass configuration parser errors, transaction relay flaws, and validator distribution components
- Handiest 26% of nodes trust upgraded; no network-wide outage has been reported
The XRP Ledger neighborhood has raised a pair of worm stories after the June 15 liberate of xrpld version 3.2.0, basically the most modern update to the network’s core server instrument.
🚨XRP News: XRP Ledger 3.2.0 Upgrade Station
🔸Ripple voted in desire of fixCleanup3_2_0 amendment
🔸26% nodes updated with XRP Ledger (XRPL) v3.2.0 liberateFull activation requires sustained 80% enhance from validators over two weeks.@XRPLOperations @Vet_X0 urging validators… pic.twitter.com/Zm2KLjWqBH
— Rednirav (@CryptoRednirav) June 19, 2026
The upgrade was expected to convey performance enhancements and a 30% to 40% reduction in memory utilization. It additionally renamed the server instrument from “rippled” to “xrpld” and incorporated security enhancements.
On the replacement hand, builders and node operators started posting components to the mission’s GitHub repository quickly after the liberate.
Sync Failure and Parser Errors
One node operator reported that a server working version 3.2.0 failed to download any ledger files after upgrading. The server stayed in a “linked” recount nonetheless may maybe per chance per chance no longer sync. The identical hardware had synced without components on version 3.1.3. That file was filed on June 18 and remains open.
A separate file discovered that inline feedback in configuration files can reason the server to break on startup. The legacy parser fails to strip feedback from definite fields, producing a “BadLexicalCast” error.
Mission maintainers trust confirmed numerous of these as bugs and flagged them for assessment.
Transaction and Validator Concerns
Builders additionally flagged a flaw in how transactions are relayed to mates. A calculation error limits how many mates gain a transaction, which may consequence in under-relaying.
The resource charging system was additionally flagged. It finest files the wonderful fee and drops earlier ones, which builders divulge is wrong habits.
A validator list distribution command was additionally reported. Validator files is at point to despatched finest to inbound mates, leaving out outbound connections. This creates an imbalance in how validator files is shared across the network.
Builders flagged a likelihood of unsigned integer overflow at some stage in ledger sequence tests. Reviews additionally pointed to inconsistent routing flags for transactions and damaged node identifiers when the use of ephemeral keys.
Yet another file described a common sense gap in ledger tracking that can scramble away a node in an unknown recount and not using a definite path to recovery.
The keep Issues Stand
As of now, no longer indisputably one of many reported bugs trust resulted in a network-wide outage. The XRP Ledger Foundation and open-supply contributors are reviewing all filed stories thru the mission’s GitHub repository.
Handiest 26% of nodes trust upgraded to version 3.2.0 to this point. The closing nodes are serene working older versions.
The XRP Ledger Foundation has no longer issued a public assertion or patch as of the time of writing. All identified components remain under lively assessment.
