Updated: 2026-08-02
Ripple's Director of Engineering, Vijay Khanna, has notified $XRP Ledger node operators about the recent release of XRPL version 3.2.1, which contains an important fix for the network.
According to the company's employee, version 3.2.1 contains a fix that prevents a "manifest flood" type of attack.
On Friday, July 31st, a "manifest flood" was observed on the XRPL network, but it is now fixed in version xrpld 3.2.1.
Previously, nodes would accept, store, and relay an unlimited number of manifests from unknown validator keys. Version 3.2.1 adds four limitations:
- a manifest size limit, where any manifest exceeding the expected size is rejected;
- an inbound limit, where incoming packets exceeding the limit are dropped instead of disconnecting from the node;
- an outbound limit, where the welcome message with a packet of manifests sent to each new node is now limited;
- a fourth caching limit, where after storing 100 unknown keys, new ones are rejected.
Manifests are also no longer saved to disk from unknown keys, so a "flood" cannot persist after a restart.
Node operators are strongly advised to take the following steps: update XRPL to version 3.2.1 in normal mode, wait one to two minutes and ensure xrpld is running, and finally, restart xrpld.
XRPL 3.2.1 enhances the security of validator manifest propagation by rejecting oversized objects at earlier stages, limiting the processing of untrusted data and stored identifiers, limiting message size, limiting the forwarding of new untrusted identifiers, and preventing untrusted information from entering persistent storage.
end-content
