Which chains and DeFi protocols Ava Guardian supports today, and what's on the roadmap.
Ava starts narrow on purpose: a small set of chains and protocols, on assets and contracts that are audited and battle-tested, so its safety guarantees actually mean something.
| Chain | Read-only scan | Action (with permission) | Notes |
|---|---|---|---|
| Ethereum | ✅ | ✅ | Lead chain; deepest protocol coverage. |
| Base | ✅ | ✅ | Lead L2 — low gas, deep Aave liquidity. |
More EVM chains (Arbitrum, Optimism, etc.) come online as we validate protocol-specific safety guarantees on each. The Guardian model is chain-agnostic; rollout is gated by safety, not engineering.
| Protocol | What Ava does | Read-only | Action |
|---|---|---|---|
| Aave v3 | Watch health factor; top-up collateral; flag risky borrows; estimate impact. | ✅ | ✅ |
| Uniswap v3 | Surface LP positions; flag out-of-range; impermanent-loss context. | ✅ | — |
| Lido | Surface stETH balance; track unstaking queue. | ✅ | — |
| Token approvals (ERC-20) | Surface stale / unlimited approvals. | ✅ | — |
"Action" coverage expands as we add and audit the specific on-chain flows each protocol needs. The first audited action surface is Aave health-factor top-up — the Liquidation Guard. Earn (idle-USDC into Aave Base) follows.
For Ava to act on a protocol on your behalf, three things have to be true:
For Ava to read a protocol — show your position, warn about risk — only data coverage from our providers is needed. So read-only support typically lights up months before action support.
In rough order:
We ship a new protocol or chain when (a) demand is validated on a probe page, (b) the audit clears, and (c) the simulation surface is honest. Roadmap order can shift if a real safety win lands earlier on a different chain.