In XRP information right now, the XRP Ledger launched xrpld 3.2.1 on July 31 after a validator manifest flood was detected hitting nodes that very same day, with Ripple Director of Engineering Vijay Khanna issuing an pressing name on August 1–2 for all node operators to improve instantly.
The ledger continued closing usually all through the incident, with no confirmed fund losses and no consensus failure, however unpatched nodes stay uncovered to resource-exhaustion threat till operators full the two-step improve course of.
This information dropped as XRP USD fell 1.5% from $1.10 to $1.06 over the previous 24 hours, with every day buying and selling quantity of $791M. This follows a worrying pattern through which Ripple has crashed -4% over the previous seven days.
XRPL Node operators,
Please improve to three.2.1 asap. It has a hotfix that stops the manifest flood assault. https://t.co/MaB2UhMXwD— Vijay Khanna (@vjkhannaripple) August 1, 2026
XRP Information: What the Manifest Flood Really Did
The assault exploited a structural hole in how XRPL nodes dealt with validator manifests: earlier than the patch, nodes would settle for, cache, and rebroadcast a vast variety of manifests tied to unknown validator keys with no ceiling on quantity or storage.
An attacker might generate junk manifests at scale, forcing nodes to burn reminiscence, disk area, and bandwidth processing knowledge they might by no means act on.
The mechanism is nearer to a denial-of-service useful resource drain than a consensus assault; the community’s transaction processing was by no means disrupted, however the publicity was actual for any operator operating unprotected infrastructure.
The event crew confirmed the issue was particularly tied to how XRPLF nodes dealt with validator manifests, although as of publication the basis trigger and full exploitation particulars haven’t been publicly disclosed.
A technical autopsy is forthcoming from XRPL Operations, which ought to make clear attacker conduct, visitors volumes, and any extra hardening steps.
For these monitoring broader blockchain safety vulnerabilities and assault vectors, the manifest flood suits a sample the place unbounded auxiliary knowledge channels change into leverage factors even when consensus logic holds.
Pressing XRPL Replace: Node Operators Instructed to Set up Vital Repair
Ripple engineering director Vijay Khanna is urging XRP Ledger node operators to improve to **xrpld model 3.2.1**, which features a hotfix designed to forestall a manifest flood assault noticed on the community.…— Crypto Michael
Dinarian888 (@Dinarian888) August 2, 2026
Uncover: The Finest Crypto to Diversify Your Portfolio
4 Safeguards Launched within the Hotfix
The hotfix introduces 4 discrete protections concentrating on completely different factors within the manifest dealing with pipeline. Outsized manifests at the moment are rejected outright earlier than full decoding. Incoming manifest batches per community message are capped.
The amount of manifest knowledge shared with new friends is restricted. And the unknown-key manifest cache is hard-capped at 100 entries, stopping unbounded development from unrecognized validator identities.
Past these 4 caps, unknown validator manifests are now not written to disk. That change means any pre-patch flood knowledge is cleared on restart moderately than persisting in storage, which is exactly why the improve requires a selected two-step sequence.
Firstly, set up 3.2.1, let the server run for one to 2 minutes, then carry out a second restart to purge any manifests retained from earlier than the patch. Skipping the second restart leaves stale flood knowledge in place. Operators must also confirm their methods belief Ripple’s present GPG signing key, rotated February 18, 2026, or computerized upgrades might fail silently.
Commerce XRP on Bybit and Get a Probability to Win Our $1,000 USDT Airdrop
Who Must Act and Why It Issues Now
$XRP's momentum fades, however the bullish construction holds agency: value is drifting again into 6YR help that guided all breakouts since 2020 — every green-arrow marked beforehand triggered enlargement; compression inside a falling wedge is setting the stage for a serious repricing
pic.twitter.com/Es1Mae0poz
—
ChartNerd
(@ChartNerdTA) August 3, 2026
In different XRP information, exchanges, custodians, pockets again ends, knowledge suppliers, and any enterprise operating its personal XRPL server should full the node improve. Unusual XRP holders don’t want to maneuver funds or change keys.
The urgency is compounded by improve adoption lag: xrpld v3.2.0, the bigger June 15 launch that renamed the reference server and required infrastructure config change, unfold quicker amongst validators than throughout the broader node community, that means a cohort of operators should be operating older variations that at the moment are doubly uncovered.
The community safety response right here was operationally sound: a focused hotfix, clear operator directions, and a pending autopsy that indicators the crew is treating this as a proper safety incident moderately than routine upkeep.
Within the broader XRP ecosystem, the incident comes because the ledger scales; the community added practically 490,000 new accounts within the first half of 2026, per supplementary knowledge from Coinpaper, pushing complete accounts previous 8.4 million.
That development trajectory makes strong infrastructure hardening a structural necessity, not an edge-case concern. Institutional developments, together with Aviva’s tokenized liquidity fund on XRPL and rising enterprise adoption, elevate the stakes for any operator nonetheless delaying the patch.
Uncover: The Finest Token Presales
The publish XRP Information: xrpld 3.2.1 Hotfix Patches Manifest Flood Draining XRPL Node Assets appeared first on Cryptonews.