DeFi Liquidity Monitoring Bot Development

Uniswap v3 made liquidity management an active endeavor. An LP position in the $1800-$2200 range on ETH/USDC worked fine for a week — until the price went out of range, and the position stopped earning fees, converting entirely to one asset. Without monitoring, such a situation can go unnoticed for days. That's direct loss from missed fees and impermanent loss. Each hour of inaction can cost tens of dollars. We develop liquidity monitoring bots that solve this: subscription to on-chain events, real-time Telegram notifications — delivered up to 50x faster than manual checks. Order a custom bot — from a basic solution for one pool to a multi-chain system with historical metrics. Our experience: 5+ years in blockchain development, 30+ DeFi projects. Each project comes with a quality guarantee and technical documentation.

Why Liquidity Monitoring is Critical?

A few hours delay in rebalancing can cost hundreds of dollars in lost profit, especially in volatile markets where price can move 10-15% in an hour. For a $50k position, just 2 hours out-of-range can mean $200 in missed fees — that's $1,200 over a month. An automated Telegram alert gives you a 30-60 minute head start to decide. Reducing impermanent loss through timely actions can reach 20-30%.

What Really Needs Monitoring in DEX Pools

Uniswap v3: Position Activity and Out-of-Range Events

Each Uniswap v3 position is defined by (tokenId, tickLower, tickUpper). The pool stores the current tick — logarithmic price. As soon as currentTick < tickLower or currentTick > tickUpper the position is out of range, fees stop accruing.

The Swap event in the pool emits a new tick. The bot subscribes to Swap via WebSocket (eth_subscribe("logs", {address: poolAddress, topics: [Swap.topic]})), decodes the tick from the event data, and compares it to tickLower/tickUpper of all tracked positions. Latency from event to notification: 100-500ms, sufficient for LP notification.

Additionally, tracking Mint and Burn events is useful — they show when large LPs enter or leave a range, often preceding price movements.

Curve: Pool Imbalance and De-Peg Monitoring

In Curve StableSwap pools, the pool is considered balanced when asset shares are close to target (usually equal). With a strong imbalance (e.g., 90% USDT and 10% USDC in 3pool), swap slippage sharply increases and effective APY for LPs drops.

Metric to monitor: deviation of current balances from ideal. Call get_balances() + compare with total_supply() / N. If one asset exceeds 70% — alert. This happened with 3pool during depegging events (USDC briefly traded at $0.87 on Curve).

The Graph for Historical Data

We use the Uniswap v3 The Graph subgraph (subgraph id: 5zvR82QoaXYFyDEKLZ9t6v9adgnptxYpKpSbxtgVENFV) for real-time TVL and volume monitoring. A GraphQL query every 60 seconds returns pool.totalValueLockedUSD, pool.volumeUSD, pool.feesUSD. This is sufficient for large pools (>$10M TVL). For small pools with rapid changes, direct WebSocket events are more reliable.

How the Monitoring Bot Works

A typical monitoring system consists of three components:

The event listener subscribes via WebSocket to pools from a configurable list. When an event is received, it decodes data via ABI and publishes to a queue (Redis Pub/Sub or in-memory queue).

The state aggregator reads the queue, updates pool state (current tick, balances, TVL), and checks alert conditions. Periodic polling (every 30-60 seconds) for metrics that don't emit events (e.g., accumulated fees via NonfungiblePositionManager.collect).

The alert dispatcher deduplicates alerts (one alert per 5 minutes per position), formats the message, and sends via Telegram or webhook. For production systems — PagerDuty with severity levels.

Calculating Accumulated Fees Without a Transaction

Current accumulated fees of an LP position can be computed off-chain without calling collect (which costs gas). Formula from the Uniswap v3 whitepaper using feeGrowthInside:

fees0 = liquidity * (feeGrowthInside0 - feeGrowthInside0Last) / 2^128
fees1 = liquidity * (feeGrowthInside1 - feeGrowthInside1Last) / 2^128

feeGrowthInside is obtained from pool tick data via static calls — not a transaction. Showing users real-time accumulated fees helps in rebalancing decisions.

Stack and Integrations

We use viem (TypeScript) for on-chain interaction — typed calls, built-in ABI decoder, multicall support for batching. The Graph for historical data and aggregated metrics. Redis for state persistence across restarts and deduplication. Telegram Bot API as the primary notification channel.

For multi-chain monitoring (Ethereum + Arbitrum + Optimism), parallel WebSocket connections feed one aggregator. Uniswap v3 is deployed on all three chains; pool addresses differ but ABI is identical.

Notification Channel Comparison

What's Included in the Work

• Repository with bot source code.
• Deployment and configuration documentation.
• Telegram bot for receiving alerts.
• 1 month of technical support after launch.
• Optional: Grafana metrics dashboard, PagerDuty integration.

Our team has delivered 30+ DeFi monitoring solutions with 5+ years of blockchain expertise, ensuring a quality guarantee on every project.

Process and Pricing

Configuration (1 day). List of pools, positions, thresholds for alerts.

Development (3-5 days). Event listener + state aggregator + Telegram/webhook integration. Test on testnet (Sepolia with forked Uniswap v3 state via Foundry vm.createFork).

Deployment. VPS with at least 2 CPU / 4GB RAM, dedicated full node or Alchemy/QuickNode WebSocket endpoint. Monitoring the bot via pm2 + health check endpoint.

How to Set Up Monitoring in 5 Steps

1. Specify pool and position addresses in the configuration file.
2. Set thresholds for out-of-range and imbalance.
3. Launch the event listener with a WebSocket provider.
4. Connect the Telegram bot via BotFather.
5. Test alert on testnet — then deploy to mainnet.

Timeline and Cost Estimates

Basic bot (one DEX, Telegram alerts): 3-5 days, starting from $500. Multi-chain system with historical metrics and dashboard: 2-3 weeks, starting from $2,000. Project cost is calculated individually based on complexity, number of chains, and required integrations. The bot quickly pays for itself by preventing impermanent loss losses — often saving $1,200/year or more for a $50k position. For pools with large liquidity, savings can be thousands of dollars per month. Contact us — we will help you choose the optimal configuration for your scenario. Get a consultation — we will prepare a commercial proposal within 1 business day.

DeFi Protocol Development

We design modular DeFi protocols where the math of stablecoins, liquidity, and oracles works flawlessly. Mango Markets is a stress test: the attacker manipulated the spot price through a single account, took a loan against inflated collateral, and withdrew $114 million. The oracle took the price from a single source without TWAP. Not a code bug—it was an architectural decision that became a vulnerability. Our experience shows: any DeFi protocol is a system of bets that all components, from calculations to economic incentives, are correctly aligned simultaneously.

We don't write code under the 'if it works, don't touch it' mindset. We model stress scenarios: cascading liquidations, depegs, flash loans. Only then do we build events that won't break the protocol.

Why are oracles a critical component of DeFi?

Most major DeFi hacks started with oracle manipulation. Let's break down the three layers we use in every project.

Spot price as oracle—not an option. Uniswap v2 spot price can be shifted by a flash loan in one transaction. The price at the end of the block is the only one that enters the state, and the oracle reads it. Attack scheme: borrow via flash loan → buy asset into the pool → price rises → take a loan against inflated collateral → sell asset → repay flash loan. One transaction.

TWAP as protection. Uniswap v3 observe() averages the price over a period (30 minutes). Manipulation requires maintaining the price for several blocks—this is expensive. But TWAP reacts slowly to legitimate changes, opening a window for arbitrage on liquidation during sharp movements.

Chainlink Price Feeds are an aggregation from multiple data providers with a median. Standard for lending. Problem: heartbeat 1–24 hours and deviation threshold 0.5%. If the price doesn't move, the feed may not update for a day. In volatile markets—lag.

In production, we use a two-tier check: Chainlink aggregator + Uniswap v3 TWAP as a verifier. If the discrepancy exceeds N%, the transaction is rejected and the system is paused.

How to protect a DeFi protocol from flash loan attacks?

Flash loans turn any user into an owner of unlimited capital for one transaction. Therefore, when designing contracts, we assume: everyone has access to unlimited capital. This completely changes the threat model.

Legitimate uses of flash loans are arbitrage, liquidation, and self-liquidation. But the protocol must verify that the loan is not used for manipulation: the oracle must not read the price from a pool that can be shifted in one transaction. We add checks on block.timestamp and minimum liquidity depth.

Key Components of DeFi Architecture

AMM: From x*y=k to Concentrated Liquidity

Uniswap v2 uses x * y = k. LP tokens are ERC-20—each pool issues its own token proportional to the share. Problem: liquidity is spread across the entire curve, most of it unused.

Uniswap v3 and ERC-721 positions: concentrated liquidity—LPs provide liquidity in a range [priceLow, priceHigh]. Capital efficiency up to 4000x for stable pairs. But ERC-721 breaks vault strategies built for ERC-20. Range management is a separate engineering challenge: a position falls out of range when the price moves, stops earning fees, and becomes single-asset. Protocols like Arrakis Finance automatically rebalance. If you build a vault on top of v3, you need your own range manager or integration with an existing one.

Slippage in v3 is calculated via sqrtPriceX96—96-bit fixed-point math. Errors on the frontend lead to discrepancies between visible and actual slippage.

Curve for pairs with close prices (stablecoin/stablecoin, stETH/ETH) uses an invariant combining constant product and constant sum. Lower slippage within the peg range. Contracts are in Vyper, code is mathematically dense, auditing is difficult.

Lending Protocols: Collateral, Liquidation, Bad Debt

LTV defines the maximum loan against collateral. Liquidation threshold is the level for liquidation. The difference is the buffer for the liquidator. Typical example: LTV 75%, liquidation threshold 80%, bonus 5%. If the price drops 20%+, the position is open for liquidation.

Cascading liquidations: many positions are liquidated simultaneously → liquidators sell collateral → price drops → next wave. LUNA/UST 2022 is a classic cascade.

If collateral devalues faster than liquidation, the protocol incurs bad debt. Aave uses a Safety Module (staked AAVE), Compound uses reserves. Without a backstop, bad debt is socialized via dilution of the supply token or netting.

Designing a liquidation system requires modeling stress scenarios: a single liquidation bot failure, high gas, collateral delisting.

Yield Farming and Incentive Mechanics

Liquidity mining distributes governance tokens to LP providers. Problem: mercenary capital—farmers come, sell tokens, leave. TVL is illusory.

Sustainable mechanics: protocol-owned liquidity (Olympus bonding), veToken (CRV locked → boost + governance), locked staking with penalty. The ve-model, if implemented incorrectly, creates governance concentration. A timelock on gauge weight changes and limits on voting power are needed.

What Our DeFi Protocol Development Includes

• Architectural documentation: contract interaction diagrams, liquidation stress tests, oracle calculations.
• Implementation in Solidity 0.8.x with OpenZeppelin 5.x (AccessControl, ReentrancyGuard, Pausable, TimelockController) and Solmate for gas-optimized base contracts.
• Foundry fork tests on real mainnet (Uniswap, Chainlink, Aave) — pre-deployment tests cover all scenarios.
• Audit: at least two independent auditors for TVL over $1M. Code4rena or Sherlock for bug bounty.
• Deployment with Gnosis Safe 3/5 multisig + timelock 48–72 hours.
• Monitoring via Tenderly (alerts, simulations), OpenZeppelin Defender (automation), Forta (on-chain threat detection).
• Post-launch support: updates, patches, upgrades via proxy.

Our Expertise and Experience

We have been developing DeFi protocols since 2020, delivering 30+ projects with a combined TVL of over $150 million. Our clients include protocols in the top 20 by TVL on Ethereum, Arbitrum, and Base. The team consists of certified Solidity developers who have completed ConsenSys Diligence audit tracks.

DeFi basic principles that we apply in practice.

Timelines

• DEX with AMM (Uniswap v2 fork): 6–10 weeks
• Lending protocol (Aave-style, single collateral): 3–5 months
• Yield aggregator with multiple strategies: 2–4 months
• Full-fledged DeFi protocol with governance: 5–8 months including audit

Cost is calculated individually—contact us for a project estimate.

Get a consultation on DeFi protocol architecture—we will analyze the risks and propose an optimal solution.