XRP Ledger node operators are being told to upgrade to xrpld v3.2.1, a hotfix released July 31, 2026, that tackles validator manifest flooding. The issue caused high memory and bandwidth usage on affected nodes, though it did not disrupt consensus or transaction processing. The Ripple development team says quick action is needed to reduce the window between problem discovery and network-wide mitigation.
Why the hotfix was needed
Validator manifests are messages that help identify and manage validator keys on the XRPL. In this case, a flood of those manifests overwhelmed some nodes, eating up memory and bandwidth. The problem was a node-resource issue, not a consensus failure — the network kept validating transactions normally. But operators who didn't upgrade risked degraded performance or even node crashes if the flooding continued.
What operators must do
The upgrade requires a double restart after installing the hotfix. That means operators need to restart their node once after applying the patch, then restart it again to fully activate the fix. The process is straightforward but must be done carefully to avoid downtime. The team emphasized that this is a stability hotfix, not a feature release, so the priority is getting it deployed quickly.
Why not wait for the next release?
XRPL has two upgrade tracks: v3.2.1 (the stability hotfix) and v3.3.0 (which will include new features and amendments). Some operators might be tempted to skip the hotfix and wait for the bigger update. But the developers warn that the flooding issue could worsen if left unpatched, and the v3.3.0 release timeline is separate. Running both tracks in parallel is possible, but the hotfix is the only way to address the immediate resource drain.
No impact on consensus
Despite the memory and bandwidth strain, the XRPL's consensus mechanism and transaction processing continued without interruption. That's a key distinction: the network remained functional, but individual nodes were at risk. The hotfix is a preventive measure to keep the entire network healthy. Operators who have already upgraded report normal resource usage returning.
The next step is for all operators to apply the hotfix as soon as possible. The development team has not announced a deadline, but given the potential for resource exhaustion, the window for action is narrow.
