How Ava prevents Aave liquidation — watch, warn, fix — end-to-end.
The canonical Guardian job. The one that justifies the whole product.
You borrow against collateral on Aave. The collateral price moves the wrong way. Your health factor (HF) drops. Below 1.0, you get liquidated — typically losing 5%+ of the position to liquidators in seconds. You can prevent it by topping up collateral or repaying — but only if you're awake, only if you notice in time, and only if the right asset is sitting in your wallet when minutes matter.
Manual monitoring is stressful, unreliable, doesn't scale.
Ava runs a Liquidation Guard job on your position:
🛡️ Ava — ⚠️ Heads up — your Aave position dropped to a health factor of 1.3. Liquidation risk is rising. Want me to help you top it up?
You — yes
🛡️ Ava — Here's what's in your wallet right now: • 500 USDC • 0.2 WETH • 50 LINK. Which would you like to top up with?
[ USDC ] [ WETH ] [ LINK ]You — taps
USDC🛡️ Ava — Simulated: supplying 300 USDC lifts your health factor 1.3 → 1.9 — safely clear of liquidation. Gas ≈ $0.40. Non-custodial — funds never leave your wallet.
[ ✅ Confirm ] [ Adjust amount ]You — taps
✅ Confirm🛡️ Ava — ✅ Done. Supplied 300 USDC → health factor now 1.9. I'll keep watching and ping you before it gets risky again.
The Liquidation Guard policy authorizes Ava to:
supply() (and optionally repay()) on the Aave Pool.Nothing else. No borrow(), no withdraw(), no other contracts. See Permissions & Limits.
If nothing in your wallet (within caps) can resolve the risk, Ava says so and asks for input — it doesn't silently fail or borrow on your behalf:
⚠️ You're at HF 1.2 but I'm not authorized to use anything large enough to fix this. Want to send USDC to this wallet now, or raise the cap?
Ava re-simulates on every confirm. If HF jumps to 1.0 before you tap confirm, Ava re-presents with the new numbers — possibly a bigger top-up, possibly already-liquidated reality. The re-presentation is always honest.