Two in three 'liquidity pulled' alerts are the same wallet putting it back
A treasury bot pings: LP removed, −$21,330,275, UNI/WBTC. Somebody pulls up a chart, somebody asks in the group chat whether the market maker left, and for the next hour the answer is a guess. The answer was sitting in the same API, one query away. 132 seconds later the same wallet put 99.8% of that money — the same 1,962,475.5391248302 UNI, to the last decimal — into UNI/WETH, one pool over. The…
A treasury bot detected a $21,330,275 liquidity removal in a UNI/WBTC pool. The wallet responsible quickly re-poured 99.8% of the funds, 1,962,475.5391248302 UNI, into the UNI/WETH pool. Alerts were triggered two-thirds of the time, as the same wallet returned the liquidity within six hours. The alert system works by fetching liquidity change data, filtering for significant events, and analyzing the movements of individual wallets.
The two primary types of liquidity events are rebalances and exits, with exits only considered valid if all follow-ups complete. Scam pools can skew results, so the system includes a guard against unrealistic liquidity values. In an 11-token, 3-chain watchlist, 66.6% of large liquidity removals resulted in partial or full re-addition by the same wallet.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
