Ava surfaces unlimited and stale token approvals — the biggest silent risk in most DeFi wallets — and helps you clean them up.
Most DeFi wallets accumulate token approvals — permissions you granted to contracts to spend your tokens. Some of those approvals are unlimited; many are to contracts you stopped using months ago. If any of those contracts get exploited, the attacker can drain the tokens you approved without ever touching your seed phrase. It's the single most common silent risk in a long-lived DeFi wallet, and almost no one is reviewing it.
In every portfolio scan, Ava flags:
MaxUint256 allowance).Each flagged approval shows: which token, which contract, how long ago it was granted, how recently it was used, and the contract's reputation signal.
🟠 You have 7 token approvals that look risky:
- Unlimited USDC →
0xAbCd…(used 0 times in 92 days)- Unlimited WETH →
0xC0fF…(used 0 times in 187 days)- Unlimited DAI →
0xDeAd…(unverified contract!)- … (4 more)
Want me to prepare the revokes?
Approval revocation is a transaction you sign from your own wallet. Approvals live on your main wallet, and Ava holds no keys to it.
Ava prepares the revoke for you. A Sign on web link opens Ava Studio, where you tap Confirm and sign in your own wallet — each revoke is a single transaction, and you pay the gas. Ava does the preparation; you do the signing. (You can also revoke with any tool you trust, such as revoke.cash.)
Auto runs only from your Ava smart wallet, never your main wallet, so approvals your main wallet gave are yours to revoke: Ava flags, you act — Ava prepares the revoke, you confirm and sign it. (Approvals held by your Ava smart wallet are different: its standard permission covers revoking approvals on the main tokens, so Ava can revoke those after you confirm, without a signature each time.)
Ava's job is to make sure you don't have to remember — it'll surface stale risky approvals every scan.
Many "scam wallet drainer" attacks rely on the victim having a stale unlimited approval to a compromised contract. The drain happens via the existing approval; the user signs nothing at attack time — because they already signed the approval months ago. Reviewing stale unlimited approvals quarterly is the single biggest preventative measure most users skip.