HumidiFi Halts Trading After Internal Network Incident Hits Platform Funds
Key Takeaways
- •HumidiFi halted trading on August 22 after an internal network incident affected a portion of its own systems, while stating that customer funds and third-party assets were not impacted.
- •The platform operates as a proprietary automated market maker, meaning its own capital rather than deposited user funds bore the financial damage from the incident.
- •No timeline for resuming trading has been provided, and the size of the platform's loss has not been disclosed.
- •The incident is HumidiFi's third operational disruption in about eight months, following a Sybil attack on its WET token presale in December 2025 and a January 2026 website outage.
- •Since launching in mid-2025, HumidiFi peaked at 30 to 40 percent of Solana's spot DEX volume and processed over $1 billion in daily trading at its height.

HumidiFi, one of Solana's busiest decentralized exchanges, switched off trading on August 22 after an internal network incident compromised a portion of its own systems. The platform moved quickly to clarify that the damage stayed in-house: customer funds and third-party assets were not affected.
For a venue that has processed peak daily volumes exceeding $1 billion, even a temporary trading halt carries real weight, especially on Solana where traders often expect fast routing and uninterrupted execution.
What Happened and What Is Known
HumidiFi describes itself as a proprietary automated market maker, meaning it supplies its own capital as liquidity rather than relying on public pools. It operates less like Uniswap and more like a professional trading desk that also happens to be a venue.
That structure is both an advantage and a liability in this situation. Because HumidiFi's own funds are on the line rather than deposited user capital, the incident's financial damage is contained to the platform itself.
The team paused trading while it investigates the scope of the incident. No timeline for resumption was provided at the time of the announcement. HumidiFi has not disclosed the size of the loss, leaving traders and token holders without a figure for the platform's exposure.
A Young Platform With a Rough Operational Record
HumidiFi launched in mid-2025 and scaled rapidly. At its peak, the platform captured between 30 and 40 percent of Solana's total spot DEX volume, a remarkable market share for an exchange that had been live for only a few months. Cumulative trading volume climbed into the $100 billion to $150 billion range within its first year.
In December 2025, a Sybil attack targeted the presale for the platform's native WET token. A Sybil attack occurs when one actor creates many fake identities to game a distribution, effectively allowing a single bad actor to accumulate tokens intended for thousands of separate participants. HumidiFi responded by canceling the original sale and relaunching with a new audited contract.
Then in January 2026, the platform's website went dark, disrupting access for users trying to trade or check positions. The team resolved the outage by switching to a new domain.
The August 22 incident is the third notable operational disruption in roughly eight months, adding another test for a platform that has grown quickly enough for reliability to matter as much as scale.
The WET Token and the Market Context
HumidiFi's WET token sits at the center of its governance and staking ecosystem. Total supply is capped at 1 billion tokens, with a circulating supply of roughly 170 million to 230 million as of mid-August 2026. The platform's assurance that user funds are safe matters because it gives holders a reason to remain patient rather than panic.
Solana's DEX landscape has alternatives. Platforms like Raydium and Orca have operated for longer and carry more institutional familiarity.
The proprietary AMM model is also relevant here. Platforms that use their own capital to provide liquidity can offer tighter spreads and more predictable execution, but they are also more exposed to internal treasury losses than venues that rely on external liquidity providers. The August 22 incident illustrates that tradeoff clearly: users were protected, but the house took a hit.