DeFi Protocol Liquidity Monitoring: Alerts and Dashboards

A protocol with $50M TVL without DeFi liquidity monitoring is not saving on tools—it's blind risk management. When 30% of liquidity exits a pool in 4 hours due to a whale withdrawal, the team has two options: find out via a liquidity alert and act, or learn from a tweet that users can't swap due to high slippage. We offer a turnkey solution in 3-5 days: from on-chain data collection to alert systems in Telegram and PagerDuty. Our track record: 5+ years in DeFi, 20+ monitoring implementations for protocols with TVL from $10M to $500M. We guarantee alert delivery within 10 seconds—50x faster than polling DeFi Llama API. Pricing starts at $500 for basic monitoring; full solution from $2000. Contact us—we'll evaluate your project for free in 1 day.

Which Metrics to Monitor and Why It's Non-Trivial

Liquidity Concentration in Uniswap v3

In Uniswap v2, total liquidity is a clear metric: reserve0 * reserve1 = k, larger k means better slippage. In Uniswap v3, liquidity is concentrated in ticks. A pool may have $10M TVL, but if 95% is concentrated in a ±2% range around the current price, a price move outside that range drops effective liquidity by a factor of 20.

Correct monitoring: not just totalValueLocked, but activeLiquidity—liquidity in the active range around the current price. Metric from the Uniswap v3 subgraph:

query ActiveLiquidity { pool(id: "0x...") { liquidity sqrtPrice tick ticks(where: { liquidityNet_not: "0" }, orderBy: tickIdx) { tickIdx liquidityNet } } } 

From this data we build a depth chart: how much liquidity is available at ±1%, ±5%, ±10% price moves.

Whale Withdrawal Detection

A large LP can withdraw liquidity in one go, collapsing depth on a specific market. For a protocol that depends on liquidity in certain pools (e.g., stablecoin pool for redemption), this is a critical risk.

We monitor Burn events (Uniswap v3) and RemoveLiquidity (Curve, Balancer) via WebSocket subscription. If a single LP withdraws >10% of total liquidity—alert immediately.

Monitoring Stack

Data Collection

Three layers of sources:

On-chain events (realtime). ethers.js WebSocket subscription to Sync, Swap, Mint, Burn events of target contracts. Latency—seconds from transaction confirmation. Requires own node or WSS from Alchemy/Infura with eth_subscribe support.

The Graph subgraphs (1-5 minute delay). Useful for aggregated metrics—hourly/daily TVL, volume, fees. For historical data and trends. Official subgraphs for Uniswap, Curve, Balancer, Aave, Compound are available in The Graph Explorer.

DeFi Llama API (10-60 minute delay). Useful for cross-protocol TVL comparisons and overall picture. Not suitable for real-time alerts.

Storage and Visualization

TimescaleDB (PostgreSQL extension)—optimal for time-series liquidity data. Partitioning by time, hypertables for automatic archiving of historical data.

Grafana + TimescaleDB datasource—standard stack for dashboards. Preconfigured panels for:

• Real-time pool TVL
• Depth chart (available liquidity at given slippage)
• Volume/liquidity ratio (stress indicator)
• Top LP providers and their share

Alert System

PagerDuty or OpsGenie for critical alerts—push notification to phone, regardless of time of day. Telegram bot for informational notifications.

Tenderly Alerts—alternative for on-chain events without own infrastructure: configure triggers via UI, webhook to Discord/Slack/Telegram.

APY Calculation and Monitoring

APY in DeFi is variable: depends on volume (trading fees), token emissions (liquidity mining rewards), and base rate (for lending).

Formula for LP APY in Uniswap v3:

dailyFees = pool.volumeUSD24h * feeTier / 1_000_000 feeAPR = (dailyFees / pool.tvlUSD) * 365 

With TVL $1M and daily volume $2M on a pool with fee 0.05% (500): dailyFees = $1000, feeAPR = 36.5%. But this is on total TVL. An LP with a concentrated position in the active range earns proportionally more based on their effective liquidity.

We monitor APY per pool with alerting on sharp drops—a signal of reduced trading activity or volume moving to a competing pool.

How to Detect a Large Liquidity Withdrawal?

Detailed above: track Burn/RemoveLiquidity events, set thresholds and notification channels. Use Tenderly or your own indexer for automation.

Implementation Process

Our implementation follows these steps:

1. Inventory of contracts and metrics (1 day)
2. Setup data collection (WebSocket + TimescaleDB) (1-2 days)
3. Create Grafana dashboard (1 day)
4. Configure alerts (Telegram, PagerDuty) (1 day)
5. Team training and handover (1 day)

What's Included

• Architecture documentation for monitoring
• Configured Grafana dashboard with key metrics
• Alert system with thresholds and notification channels
• Scripts for data collection and integration with new pools
• Team training (1-2 hours)
• Support for 1 month after implementation

Time Estimates

Basic monitoring for one protocol (TVL, events, alerts)—3-5 days. Comprehensive monitoring for multiple protocols with depth charts, APY tracking, and custom dashboard—up to 2 weeks. Pricing is determined individually based on number of protocols and integration complexity.

const { ethers } = require("ethers");
const provider = new ethers.providers.WebSocketProvider(process.env.WSS_URL);
const poolContract = new ethers.Contract(POOL_ADDRESS, UNISWAP_V3_POOL_ABI, provider);

poolContract.on("Burn", (owner, tickLower, tickUpper, amount, amount0, amount1) => {
  console.log(`Burn: owner ${owner}, amount ${amount}`);
  // Check share of total liquidity
  checkWhaleWithdrawal(owner, amount);
});