Is this address delegated under EIP-7702, to what, and on which chains?
Paste an EVM address. The tool reads every EVM chain it covers and answers, chain by chain:
- not delegated: a plain key wallet there;
- delegated to
0x…: the account runs another contract's code, plus whether that contract is a known wallet implementation (with a link to the vendor's own source) or not on our list; - could not read: the chain's public RPCs did not answer (never shown as "not delegated");
- 7702 not active: the chain does not run EIP-7702 (if a designator turns up there anyway, the code wins and it is reported as delegated);
- a contract: the address is an ordinary contract on that chain, so it cannot carry a delegation.
It is keyless and read-only. It never asks for a seed phrase, private key, OTP or signature, holds no funds, and never signs or sends anything. Clearing a delegation is something only the account's own key can do; the page explains how.
EIP-7702 lets a key wallet point itself at a smart contract by signing an authorization. The delegation is stored in the account as its code and persists until the account's key replaces it. Rotating keys in a custody system, pausing withdrawals or moving funds away does not clear it. On 29 Oct 2026 about $6.3B was taken from Binance hot wallets; on Ethereum one transaction carried 50 EIP-7702 authorizations pointing a hot wallet at an attacker's sweeper contract, and the delegation stayed in place for hours (Hypernative, Chainalysis). Most wallets show no delegation status at all.
One eth_getCode(address, "latest") per chain. Per EIP-7702
(Specification, Behavior step 8), a delegated account's code is exactly the 23-byte delegation indicator
0xef0100 || address. Anything else non-empty is an ordinary contract. EIP-3541 forbids deploying contracts whose
code starts with 0xef, so a designator can only have been written by a 7702 authorization.
Clearing: an authorization whose address is 0x0000000000000000000000000000000000000000 makes the chain skip writing
the indicator and reset the account's code to empty (same section). It has to be signed by the account's key, once per
chain where the account is delegated (an authorization signed for chain ID 0 is valid on every chain).
The 31 live EVM chains of Safe to Send (src/chains.js, same public RPCs, no keys, no dRPC/1RPC). Whether each one
runs 7702 is recorded with its evidence in src/activation.js, checked 16 Nov 2026:
- 7702 active, seen directly (25): a type-4 (set-code) transaction in a recent block and/or accounts whose code is a designator: Ethereum, BNB Chain, Base, Arbitrum One, OP Mainnet, Linea, Scroll, Gnosis, Unichain, Robinhood Chain, Sonic, Celo, Mantle, Morph, Berachain, Ink, Polygon, Cronos, Sei, Taiko, Monad, Plasma, Katana, Soneium, Mode.
- 7702 active, from the upgrade record (1): Zora (OP Stack Isthmus,
isthmus_time = 1746806401in the superchain registry; no type-4 transaction in the last 3,000 blocks). - 7702 not active (5): Avalanche C-Chain (ACP-209 still Proposed), Metis, ZKsync Era, Abstract (EraVM) and
HyperEVM. Metis and Avalanche also ignored the authorization list in an
eth_estimateGasprobe (21,000 gas, where 7702 chains charge 46,444). These chains are still read, so a delegation there would still be reported.
Retired chains (Blast, Polygon zkEVM, Lisk) are never read.
src/known-delegates.json: a deliberately small list. Each address was read from the vendor's own repository or
docs (the source link) and has code on Ethereum mainnet, checked 16 Nov 2026: MetaMask EIP7702StatelessDeleGator
v1.3.0, Coinbase Smart Wallet EIP7702Proxy, Uniswap Calibur v1.1.0 and v1.0.0, Ambire AmbireAccount7702,
eth-infinitism Simple7702Account, Alchemy SemiModularAccount7702, ZeroDev Kernel v3.3, and two Biconomy Nexus v1.2.0
deployments. Safe is not listed: it publishes no canonical 7702 delegate address.
node cli.js 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 # every chain
node cli.js 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 --chains 1,8453 --jsonimport { checkDelegation } from "./src/delegation.js";
const r = await checkDelegation("0x…"); // or checkDelegation("0x…", [1, 8453])
// r.chains: [{ id, name, explorer, active, status, delegate, known }], r.summary: { delegated, unknown, notActive }The page is index.html + src/page.js, served as static files. Strict CSP (scripts from itself only, network only to
the chains' RPCs), textContent only, no analytics.
No install, no node_modules, no build step. Plain ES modules, Node 22 or later:
node --test "test/*.test.js" # or: npm testTests replay real eth_getCode answers recorded on 16 Nov 2026 (fixtures/, a few KB each; re-record with
node scripts/record.mjs <name> <address> [chainIds]). No network.
src/rpc.js: copied verbatim from Safe to Send (as of its commit 66b253e). Keep it byte-identical; change it there first.src/chains.js: copied from Safe to Send at the same commit. TheCHAINSlist,LIVE_CHAINS,chainByIdandchainNameare verbatim; the non-EVMNETWORKSlist (format-only networks this tool never reads) and its two lookup helpers are removed.src/delegation.js: the new core.parseCode(code),knownDelegate(address)andcheckDelegation(address, chains, { clients }).src/activation.js: per-chain 7702 activation and the evidence for it.src/known-delegates.json: the curated delegate list with sources.src/report.js+cli.js: the terminal report.index.html+src/page.js: the page.
Safe to Send's own classifier already recognises a designator (kindOfCode returns "eip7702" for
/^0xef0100[0-9a-f]{40}$/i) but does not name the delegate or check every chain for it; this tool does.
- It reads only the current code. It does not show when a delegation was set, past delegations, approvals or balances.
- A "known" label is not a safety guarantee. It means the delegate's address matches a wallet implementation its vendor published. An account delegated to a known wallet can still be drained if its key or signer is compromised, and an unlisted delegate is not proof of theft.
- Activation can change. A chain marked "7702 not active" may upgrade; the code read still wins.
- Public RPCs can lag or fail. A chain that does not answer is shown as "could not read".
Nothing is stored and nothing is logged: no account, no cookies, no analytics, no server of ours in the path. To read an address, your browser (or the CLI) asks each chain's public RPC service about it, so those services see the address and your IP.
Read-only and keyless by construction. See SECURITY.md. MIT licensed.