DeFi Position Monitoring System with Alerts

Health factor 1.05 in Aave means 5% until liquidation. During high volatility, it takes minutes to go from 1.05 to losing the position. Without a monitoring system, the user learns about the problem after the fact: the position is liquidated, and the 8–15% liquidation bonus goes to the liquidator. On large volumes, this amounts to thousands of dollars that could have been saved by adding collateral in time. In recent years, liquidations due to slow reaction have become more frequent — even a couple of minutes of delay can cost tens of thousands. We develop turnkey DeFi position monitoring systems that track health factor, LP positions, liquidations, and other metrics in real time. The system works with Aave, Compound, Uniswap v3, and custom protocols, supports multi-chain (Ethereum, Arbitrum, Optimism, Polygon, BNB Chain), and sends alerts via Telegram, Email, Webhook, or Push.

How does DeFi position monitoring work?

Monitoring health factor in Aave uses the formula: HF = (sum(collateral_i * liquidationThreshold_i * price_i)) / (sum(debt_j * price_j)). Calling the contract IPool.getUserAccountData(address) returns healthFactor in 1e18 = 1.0 format. A value below 1e18 means the position is being liquidated. For efficient mass polling, we use Multicall via the Multicall3 contract (0xcA11bde05977b3631167028862bE2a173976CA11). One eth_call retrieves HF for 100 addresses — 100 times more efficient than individual requests.

Alert thresholds:

Why Uniswap v3 LP positions require a separate approach?

For Uniswap v3, we monitor three metrics:

• Current USD value of the position — via NonfungiblePositionManager.positions(tokenId) + calculation of amounts based on the current pool tick.
• Accumulated fees — simulation of collect via eth_call (no real transaction) or calculation based on feeGrowthInside.
• In/out-of-range status — subscribe to the pool Swap event, compare currentTick with position bounds.

To reduce RPC load, we use The Graph subgraph (1–5 min delay), and for real-time we use WebSocket subscriptions. Comparison: subgraph provides the "past" with minute-level precision; WebSocket gives the current state.

How to set up health factor alerts?

The alert engine allows creating flexible rules for each protocol and chain. For example, a rule: if health factor <= 1.2 on Ethereum for Aave, send a Telegram notification with the text "Time to add collateral!". Thresholds can be set with 0.01 precision, and channels can be combined: Telegram for urgent, Email for daily summary. For large portfolios, we configure alerts on multiple conditions: critical HF for one asset may not indicate a problem if there is cross-collateral. The system supports logical operators (AND/OR) to avoid false positives.

System architecture

Components:

1. Indexer — reads on-chain data (polling via multicall + WebSocket subscriptions), stores in a database.
2. Alert engine — applies user-defined rules (thresholds, channels, chains).
3. Notification dispatcher — sends via Telegram Bot, Email, Webhook, Push.
4. Dashboard — React + wagmi, wallet login, HF graphs.

Storage: PostgreSQL + TimescaleDB for time-series data. Schema:

CREATE TABLE position_snapshots (
  id BIGSERIAL PRIMARY KEY,
  address VARCHAR(42) NOT NULL,
  protocol VARCHAR(20) NOT NULL,
  chain_id INTEGER NOT NULL,
  health_factor NUMERIC,
  collateral_usd NUMERIC,
  debt_usd NUMERIC,
  snapshot_at TIMESTAMPTZ NOT NULL
);
CREATE INDEX ON position_snapshots (address, protocol, snapshot_at DESC);

Multi-chain aggregation: separate connection to each network, unified under a single dashboard. Additionally, we monitor gas price — notification when base fee is below 10 gwei (a rare event for economical rebalancing).

Work process

1. Analysis — audit your positions and identify critical metrics.
2. Design — architecture of indexer, alert engine, channel selection.
3. Development — implement protocol connections, configure polling/WebSocket.
4. Testing — simulate liquidations on forked network (Hardhat anvil) to verify alerts.
5. Deployment — deploy to your infrastructure or cloud, set up uptime monitoring.

What is included in the work

• Analysis: list of protocols and metrics specific to your portfolio.
• Development of indexer and alert engine with custom rules.
• Integration of notifications (Telegram, Email, Webhooks).
• Web dashboard with history and configuration.
• Documentation for operation and deployment.
• Technical support for the first month.

Timeline estimates

Cost is calculated individually. Contact us — we will evaluate your project and offer the optimal solution. Order a monitoring system to avoid losing funds to liquidations. Guaranteed uptime 99.9% (own service monitoring via Uptime Robot). Team experience — 30+ DeFi projects. Don't wait for liquidation — get a consultation on monitoring setup today.

Formulas and contracts from official Aave documentation and Uniswap v3 whitepaper.

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.