The XRP Ledger development team has released xrpld 3.2.1, an urgent software update designed to address a manifest flood issue observed on July 31 while introducing new safeguards to strengthen the network against similar events in the future.
According to XRP Ledger Operations, the incident did not interrupt normal network operations, with the blockchain continuing to close ledgers throughout the event. However, developers are urging all node operators to upgrade immediately and complete a required restart process to fully apply the fixes.
The update follows an incident in which nodes accepted, stored, and rebroadcast an unlimited number of manifests from unknown validator keys, creating unnecessary network overhead without affecting consensus or ledger production.
XRPL 3.2.1 Adds Multiple Security Safeguards
The new release introduces four key protections aimed at limiting how unknown validator manifests are processed.
The first change adds a size cap that automatically rejects any manifest larger than the expected limit. A second receive cap prevents oversized batches of incoming manifests from disrupting peer connections by discarding excess data instead of terminating communication.
Developers have also implemented a send cap, limiting the number of manifests transmitted when new peers connect to the network. In addition, a new cache cap restricts nodes to storing manifests from a maximum of 100 unknown validator keys, refusing any additional entries beyond that threshold.
Related: XRP Ledger Adds Privacy, Delegation, and Atomic Transactions in Major Network Upgrade
Another important improvement is that manifests from unknown validator keys are no longer written to disk. This prevents large volumes of unwanted data from persisting after a node restart, reducing the potential impact of future flooding attempts.
The XRP Ledger Operations team confirmed that a full post-mortem detailing the incident will be published for the community in the coming days.
Node Operators Encouraged to Upgrade Immediately
To ensure the protections are fully activated, developers have outlined a specific upgrade procedure. Operators should first install xrpld 3.2.1 through the normal update process and wait one to two minutes to confirm the server is running, even if it has not yet reached full synchronization or validator status.
A second restart is then required, which developers describe as an essential final step for clearing previously stored manifests and completing the upgrade process.
Related: XRPL Ecosystem Guide: What’s Being Built on the XRP Ledger Today
The official release notes describe version 3.2.1 as a hotfix focused primarily on addressing the manifest flood issue. The update also reminds operators that Ripple rotated the GPG signing key earlier this year, meaning systems that have not yet trusted the new key may encounter issues with automatic package upgrades.
Although the July 31 incident did not affect ledger finality or transaction processing, the release demonstrates the XRP Ledger development team’s continued focus on proactively strengthening network resilience. By introducing stricter validation limits and reducing unnecessary resource consumption, xrpld 3.2.1 aims to improve the stability of node operations while preserving the decentralized network’s performance as adoption continues to grow.
About The Author
