ERC-20 approval guard

Most onchain drains exploit an approval the owner forgot about. This finds them.

Gather

• Enumerate Approval(owner, spender, value) logs for the wallet on Base.
• For each (token, spender) still in effect, read the current allowance — past logs lie; only the live value matters.
• Resolve each spender: verified contract? known router/protocol? EOA? unverified?
• Note last-use: when did the wallet last interact with this spender?

Classify risk

• Critical — unlimited allowance (2^256-1 or near) to an unverified or EOA spender.
• High — unlimited allowance to a verified contract that's gone dormant (no use in 90d).
• Medium — finite but oversized allowance, or any allowance to an unaudited spender.
• Low — bounded allowance to an active, verified protocol.

Emit a revoke plan

Order by risk, then by token balance at stake. For each item to revoke, produce the calldata for approve(spender, 0) (or decreaseAllowance where supported), ready to sign. Group by token so an agent can batch.

Output

{ wallet, chain, items: [{ token, symbol, spender, spenderLabel, allowance, risk, lastUsed, revokeCalldata }], summary: { critical, high, medium, low } }

Read-only analysis — it never moves funds. The wallet owner signs every revoke.