XRP Ledger 3.2.1 fixes manifest flood affecting nodes
In brief
- XRP Ledger Version 3.2.1 released to fix manifest flood affecting nodes on July 31
- Upgrade limits manifest batches, rejects oversized manifests, caps unknown validator key storage at 100
- Incident caused no transaction disruption; ledgers continued closing normally throughout
The Problem
A manifest flood is a condition where XRP Ledger nodes receive an excessive volume of validator manifests. Before the update, XRPL nodes could accept, store, and rebroadcast an unlimited number of manifests from unknown validator keys, leaving them vulnerable to resource exhaustion and network noise.
The problem was tied to how XRPL nodes handled validator manifests—specifically, the lack of safeguards against bulk or malformed data. Developers identified the issue after it surfaced on Friday but worked to contain damage without sacrificing ledger stability.
The Fix
Version 3.2.1 introduces multiple constraints. The network now rejects unusually large manifests, limits the number of incoming manifest batches that can be processed, places a cap on the bulk manifest data shared with new peers, and prevents nodes from storing manifests from more than 100 unknown validator keys.
Additionally, unknown validator manifests will no longer be saved to disk, meaning any flood of unwanted data clears after a node restart. This design prevents attackers from poisoning node storage with junk manifests.
The team has yet to disclose what triggered the flood or whether it was accidental or deliberate. What matters now: the network's resilience held, and developers moved to plug the gap.
