Liquidity disappears far faster than most people think—a pool withdrawal is just one transaction, one block. On Solana it takes under a second, and on Ethereum about 12 seconds. Once it's gone, by the time price charts or community chatter reach you, the pool may already be drained down to scraps.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Follow these three steps to equip yourself with a "radar" that spots liquidity withdrawals early.
Prerequisite: Choose Your Monitoring Tool
The core of on-chain alerts is real‑time monitoring of a pool's net reserve changes. An ordinary large swap only shifts one token up and the other down, leaving the total value nearly unchanged. A liquidity withdrawal, however, shrinks reserves of both tokens together—a signature that cannot be faked.
You have two paths:
No‑code path: Use a ready‑made monitoring platform like ChainBot and subscribe to an "LP withdrawal" bot directly.
DIY path: Use the open‑source LiquidityRadar tool by CoinPaprika – no API key needed, deployable for free.
Definition of done: You have chosen at least one path – either you've registered on a platform or you've pulled the tool's code.
Step 1: Set a "Dual‑Threshold" Monitoring Rule
The core rule is to fire an alert only when both absolute amount + percentage conditions are met simultaneously—filtering out small‑value noise while catching large withdrawals without fail.
What to do: Create a separate monitoring rule for the new token / small‑cap pool you care about.
How to do it:
Don't use the default monitoring list (usually major pairs). You must add the contract address of your target token to the monitoring list.
Set two parameters:
minUsd: Absolute floor amount. Recommended: $10,000. Changes below this are ignored.
pctThreshold: Percentage threshold. Recommended: 20%–30%. This means alert when a single withdrawal exceeds this proportion of the pool's total, no matter if the pool is $1M or $10K.
Core logic: The alert triggers only when "withdrawn amount > $10,000" AND "withdrawn percentage > 20%" are both true.
Definition of done: You've entered both threshold parameters for the specified small‑cap pool in your monitoring tool.
Common failure reason: Monitoring metrics like "24‑hour volume decay" instead. Volume decline is a slow signal; a pool withdrawal is sudden. The two are on completely different threat levels. Substituting the latter with the former is like using a thermometer to detect an earthquake.
Step 2: Distinguish "JIT Liquidity" from a Real Withdrawal
Once the monitoring tool is deployed, false alarms are the biggest headache. In crypto markets, especially in large pools of major tokens, there is an operation called "JIT (Just‑In‑Time) liquidity": bots add massive liquidity in the same block before a large trade to capture fees, then remove it in the very next block after the trade.
What to do: If an alert comes from a major‑pair pool, don't panic immediately—check whether it's a JIT operation.
How to do it:
Quick check: If the monitored pool is a major pair (e.g., ETH/USDC), and you see a large withdrawal (maybe millions of dollars) but the amount flows back within a few consecutive blocks, it's very likely a JIT bot.
Set avoidance parameters: You can set a lower bound on withdrawal percentage. JIT operations are large in absolute terms but usually represent a tiny fraction of a giant total pool. Research shows JIT activity accounts for only about 4% in major pools. If the withdrawal percentage is below 15%–20%, it's basically noise from those bots and can be ignored.
Manual pattern check: If an alert comes from a pool that only went live a few hours ago with a total market cap under a few hundred thousand dollars, it is almost impossible for JIT bots to be present. In that case, over 90% of the time the alert is a genuine withdrawal signal.
Definition of done: You clearly understand that alerts from "new/small pools" require immediate reaction, while "low‑percentage alerts from large pools" are likely noise.
Step 3: Deploy "24/7" Continuous Monitoring
Running a script locally is limited by your computer being on or off. To truly have a warning system, you need a persistent server to watch for you.
What to do: Deploy the monitoring tool to the cloud so it runs 24 hours a day and pushes messages.
How to do it:
One‑click deployment (recommended): Use the open‑source LiquidityRadar, which supports one‑click deployment to Cloudflare Workers (free tier works). It comes with a public status page and can be configured with webhook notifications.
Configure notification channels: Set the WEBHOOK_URL in the tool to point to your Discord, Telegram, or Feishu bot. Once an alert triggers, a message will be pushed to your phone instantly. The ChainBot platform natively supports channels like Slack/Pushover.
Definition of done: You have completed the deployment and successfully received your first test notification from the monitoring program (confirming the notification channel works).
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
How to Confirm Everything Works Correctly?
After deployment, do a final verification: temporarily set the "withdrawal percentage" threshold to 1% in your monitoring list. Then, make a small withdrawal from a pool where you have a tiny LP position or a low‑liquidity pool. Check whether you receive an alert notification on your phone within one minute.
If you receive it, the entire chain (on‑chain → monitoring node → cloud → your phone) is connected. Then set the threshold back to 20%, and your early‑warning system is live.
