XRP Ledger urges node upgrade after manifest flood

Ripple Director of Engineering Vijay Khanna urged XRP Ledger node operators on Aug. 2 to install xrpld version 3.2.1 after developers observed a validator manifest flood on July 31. Summary July 31 manifest flooding prompted xrpld 3.2.1 while XRP Ledger continued closing ledgers normally throughout. Four safeguards now cap manifest size, message batches, outbound sharing and unknown-key cache growth network-wide. Operators should upgrade, verify xrpld is running, then restart again to clear persisted manifests safely. The hotfix limits how nodes process, store and share data received from unknown validator identities. The XRP Ledger continued closing ledgers normally during the event, according to XRP Ledger Operations. The available evidence therefore points to pressure on node resources and peer-to-peer communications rather than a confirmed loss of funds, altered transactions or failure of ledger consensus. Developers have not published a CVE identifier or financial-loss estimate connected to the incident. XRPL 3.2.1 limits the manifest flood route Validator manifests are cryptographically signed records that connect a validator’s stable master identity to the temporary key it u...