Aave Liquidation Monitor

Quick Start

Configure your wallet and thresholds once, then the skill runs automatically every 6 hours (configurable).

Step 1: Initialize Your Config

Run /aave-config init to set up:

• - Your Ethereum wallet address (read-only; no private keys required)
• Health factor thresholds (default: critical 1.05, warning 1.2, stable >1.5)
• Check interval in hours (default: 6)
• Notification verbosity (verbose = daily summaries even if stable; quiet = only alerts)
• Preferred notification channel (Telegram default, or specify Discord/Slack)

Example:
CODEBLOCK0

Step 2: Test the Monitor

Run /aave-monitor check to fetch your position immediately and see the alert format:

CODEBLOCK1

Step 3: Enable Proactive Monitoring

Run /aave-monitor enable to start automatic checks every 6 hours. The skill registers a cron job that silently runs in the background and alerts you only when health factor drops below threshold.

For manual override:
CODEBLOCK2

Configuration Reference

See references/config-guide.md for detailed config options, chain support, and threshold guidance.

See references/aave-api.md for Aave V3 GraphQL schema and query patterns.

Security & Credentials: See SECURITY.md for how credentials are handled and threat model.

For auditors: See SECURITY.md for code review checklist and architecture details.

How It Works

1. 1. Query Phase: Calls Aave V3 GraphQL API with your wallet address
2. Analysis Phase: Extracts health factor, collateral, debt, borrowed/supplied assets
3. Alert Logic:

1. 4. Notification Phase: Posts alert to your configured channel with clear summary
2. Retry Logic: If API fails, retries up to 3 times with exponential backoff

Error Handling

• - Invalid wallet address → Logs error, skips check, retries next interval
• API timeout → Retries up to 3x with exponential backoff (2s, 4s, 8s)
• Malformed response → Alerts you to API changes, logs full response for debugging
• Network errors → Silently retries; alerts only if all retries fail

Security & Credentials

NO private keys are requested or stored — this is read-only monitoring only.

How messaging credentials work

The skill uses OpenClaw's built-in message routing — it does NOT store Telegram, Discord, or Slack tokens.

1. 1. You configure your messaging channel in OpenClaw (outside this skill)
2. The skill calls OpenClaw's messaging API with just the alert text
3. OpenClaw routes the message using your configured channels

Example:
CODEBLOCK3

You must have a messaging channel already set up in OpenClaw. See OpenClaw docs for setting up Telegram/Discord/Slack integrations.

Data handling

• - Wallet address: Stored in OpenClaw's encrypted config (never sent to external services except Aave's public API)
• API responses: Parsed for health factor only; sensitive position data is NOT logged
• Credentials: Managed by OpenClaw, never stored in skill files

What the skill accesses

✅ Aave GraphQL API (public) — reads your position data
✅ OpenClaw message routing — sends formatted alerts to your configured channel
✅ Cron scheduler — runs background checks on your interval

❌ Does NOT:

• - Request private keys
• Store API tokens
• Execute transactions
• Modify your positions

Examples

Alert Examples

Critical Alert (HF < 1.05):
CODEBLOCK4

Warning Alert (HF < 1.2):
CODEBLOCK5

Stable Position (HF > 1.5, verbose mode only):
CODEBLOCK6

Command Examples

CODEBLOCK7

Chains Supported

Primary: Ethereum mainnet

Also works (with same config address where applicable):

• - Polygon
• Arbitrum
• Optimism
• Base
• Avalanche
• Gnosis

Edit scripts/monitor.js to add chains or customize per-chain endpoints.

Customization

Change check interval:
CODEBLOCK8

Change alert thresholds:
CODEBLOCK9

Enable verbose mode (daily summaries even if stable):
CODEBLOCK10

Switch notification channel:
CODEBLOCK11

Implementation Details

See scripts/monitor.js for the core monitoring logic (GraphQL queries, health factor calculation, alert formatting).

See scripts/cron-runner.js for cron job integration with OpenClaw's cron scheduler.

Troubleshooting

"Invalid wallet address"
→ Check format: must be 0x... format. Try /aave-config view to see current config.

"Health factor not returned by API"
→ Wallet may not have Aave position. Try /aave-monitor check for immediate response.

"API endpoint unreachable"
→ Aave API may be down. Skill retries automatically. Check https://status.aave.com.

"No notifications sent"
→ Check that your notification channel is active. Run /aave-monitor check to test delivery.

Notes

• - Health factor = Total Collateral / Total Debt (net of liquidation threshold ratios)
• Liquidation occurs when HF ≤ 1.0
• Variable debt accrues interest; stable debt is fixed-rate
• eMode allows higher LTV for correlated assets (e.g., stablecoins, ETH-LSTs)
• Supplied assets are collateral; they earn interest but can be seized if you're liquidated