WETH/Forever Base Pool Loses All $53k Liquidity
The WETH/Forever trading pair on the Base network experienced a total loss of real liquidity, falling from a high of $53,605 down to just one dollar. This drastic reduction indicates that nearly all funds were removed or drained immediately following the initial deployment phase detected in June 2026.
A specific liquidity pool on the Base network has effectively ceased to function as a viable trading venue. The pair involving Wrapped Ether and Forever tokens saw its available capital vanish almost entirely within a short window of time.
The Event Details
Monitoring data reveals that this particular contract, identified by address 0xedbb6757e2a791892ca8ea3a20a7d6f1e0e356c9, reached a peak liquidity level of $53,605 before the event occurred. The first signs of this anomaly were detected on June 14, 2026, at approximately 23:26 UTC.
What the Numbers Mean
The current status shows a drawdown from peak liquidity that is mathematically described as 100%. In practical terms for an investor or trader, this figure means there are no meaningful funds left to swap against. The pool balance has collapsed from its maximum value down to exactly $1.
This drastic shift implies that the entire depth of the market was removed instantly. For a user attempting to enter a trade today, they would find an empty order book where significant volume once existed. A health score assigned to this entity is currently 20 out of 100, reflecting its poor standing despite standard risk flags showing no immediate on-chain anomalies.
Implications for Traders
- The deployer wallet associated with the event holds address 0xa0967c45bfe6b1156bb6d51e8b50cf1c6b98d2fd.
- Any expectation of returning liquidity based on historical highs is unfounded given the current state.
The rapid transition from a healthy pool to one with negligible value suggests an intentional removal of assets rather than organic market decay. Users should treat such metrics as indicators that the specific contract address 0xedbb6757e2a791892ca8ea3a20a7d6f1e0e356c9 is no longer operational for standard trading purposes.