XRP Ledger developers have rolled out Version 3.2.1 to fix a manifest flood that hit network nodes on Friday, July 31. The update adds four new protections against unknown validator manifests, and reports showed the incident never stopped transaction processing.
XRP Ledger developers have shipped Version 3.2.1 to fix a manifest flood that struck network nodes on Friday, July 31. Developers confirmed the rollout in a post from the XRP Ledger Foundation. Ledgers kept closing normally throughout the incident, so the flood never disrupted transaction processing.
The bug traced back to how XRPL nodes handled validator manifests, though developers have not disclosed its root cause. Before the fix, nodes could accept, store, and rebroadcast an unlimited number of manifests from unknown validator keys. This behavior did not stop transactions from processing, but it did drive up unnecessary resource use across the blockchain.
As a result, the upgrade now rejects unusually large manifests and limits how many incoming manifest batches a node can process. It also caps the bulk manifest data shared with new peers and stops nodes from storing manifests from more than 100 unknown validator keys.
Developers also changed how unknown validator manifests get stored: they no longer save to disk. Therefore, any future flood of unwanted data clears out once a node restarts instead of lingering in the system.
Source: U.Today
Trading involves risk.
Risk Disclaimer
