Aegis7702

Aegis7702 makes EIP‑7702 delegation safe enough to actually use.

In 7702, "delegation" is similar to installing a new program for your wallet. If the implementation is malicious (or just buggy), it can drain funds, brick the account, or break when you switch implementations. That’s why most wallets block "delegate to an arbitrary address" and rely on tiny allowlists.

Aegis7702 replaces blind trust with verifiable safety: before delegation, our AI Analyzer reviews any 7702-implementation address, produces a security report, and publishes a Safe/Unsafe verdict (plus an integrity fingerprint) to a shared on‑chain Safety Registry.

After delegation to our Guard 7702-delegator, Aegis, every transaction is pre-checked by our AI Analyzer and risky actions are proactively blocked. We also run post‑transaction monitoring: watchers compare expected vs actual outcomes and can trigger an emergency Freeze to stop further damage. Unfreeze is controlled by the user's offline recovery key—not by us.

The Safety Registry is public and composable: other wallets, apps, and analysts can reuse the same Safe/Unsafe verdicts and reports (keyed by implementation + code hash), so the ecosystem benefits from shared security knowledge instead of fragmented allowlists.

On-chain, the AegisGuardDelegator is the EIP‑7702 delegation target. It stores only minimal per-wallet metadata in the EOA's storage using hashed, namespaced slots (EIP‑1967-style + ERC‑7201) to reduce collision risk. The Guard only delegatecalls implementations that are marked SAFE and match the recorded fingerprint.

Off-chain, we run a Python FastAPI service + worker pipeline. LLM-based analyzers emit structured SAFE/UNSAFE reports (JSON schema). A watcher continuously post-audits mined transactions, and triggers on-chain notes/freezes when it detects abnormal or drainer-like behavior.