Delegated accounts
accountsAccounts whose code is a delegation designator at the latest pinned block.
Dashboard · VantagePlanned
EIP-7702 Adoption: Delegated EOAs and Top Contracts
How many accounts use EIP-7702 delegation, and which delegate contracts do they point to?
How many accounts have delegated their code under EIP-7702, the contracts they point to and how much of it looks like sweeper scams.
ShareEmail it
Blueprint
What the dashboard will show.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
Adoption
Delegations, delegated accounts and their growth since Pectra.
Type 4 transactions, latest day
transactionsType 4 transactions included on the latest complete day.
Net new delegations
accountsAccounts that set a delegate on the latest complete day, minus accounts that cleared one.
Value in delegated accounts
USDETH and major token balances held by delegated accounts at the latest pinned block, valued at oracle prices.
Delegated accounts over time
accountsDelegated accounts at the end of each day since Pectra, with new delegations and clears per day.
Delegate contracts
Which contracts accounts point to, and how many look malicious.
Delegate contracts in use
contractsDistinct contracts that at least one account delegates to at the latest pinned block.
Accounts on sweeper code
accountsAccounts delegated to contracts the registry classifies as sweepers.
Accounts by delegate class
accountsDelegated accounts by the class of their delegate: wallet implementation, module, sweeper or unclassified.
Top delegate contracts
The delegate contracts with the most accounts, with their class, label, accounts, value held and the day each was first used.
- Chain
- Ethereum or each covered EVM chain that supports EIP-7702
- Period
- Last 30 days, 90 days or since Pectra
About
What it answers, and for whom.
EIP-7702, part of the Pectra upgrade, lets an ordinary account (an EOA) point its code at a smart contract, so the same address can batch calls, have its gas sponsored or use passkeys without moving funds. The account signs an authorization, and a type 4 transaction writes a delegation designator into its code. This dashboard counts those delegations, the accounts that hold one and the contracts they point to.
The same feature is used by attackers: a phished authorization can delegate a wallet to sweeper code that drains anything sent to it. So the dashboard classifies delegate contracts, from wallet implementations to known sweepers, and shows how many accounts and how much value sit behind each class. Every figure is pinned to a block and reads the accounts' code directly.
Method
How it will be measured.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →- Delegations are read from type 4 transactions: each authorization_list entry names a chain id, a delegate address and a nonce, and its signer (the authority) is recovered from the signature.
- An account counts as delegated when its code at the pinned block is the delegation designator 0xef0100 followed by a delegate address, read with eth_getCode; a delegation to the zero address clears it.
- Delegate contracts are classified from a reviewed registry into wallet implementations, batching or sponsorship modules and sweeper code that forwards incoming funds to an attacker.
- Balances of delegated accounts are their ETH and major token balances at the same block, valued with oracle prices, so the exposure behind each class can be measured.
- Authorizations signed with chain id zero are valid on every chain, so each use is counted on the chain where it happened.
The data it needs
Read from chain state and history
- account_abstraction_dailyTo buildSmart accounts and EIP-7702ERC-4337 UserOperations, bundlers and paymasters, and EIP-7702 delegations per chain per day.
- address_labelsTo buildAddress labelsLabels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
- token_holders_snapshotTo buildToken holders and concentrationHolder counts, top holders and concentration shares of registry tokens at a pinned block, with contract and exchange labels.
- native_prices_dailyTo buildOracle prices by dayReference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
- Type 4 transactions with authorization_list entries: chain_id, address, nonce and signature
- eth_getCode of each authority at the pinned block, checking for the 0xef0100 designator
- ETH and major token balances of delegated accounts at the same block
- A reviewed registry of delegate contracts, recorded with the source of each classification
Questions
Questions people ask.
What is EIP-7702?
A change introduced with Pectra that lets an externally owned account set its code to point at a contract. The account keeps its address and key, but calls to it run the delegate's code, which enables batching, gas sponsorship and other smart account features.
How can I check whether my address is delegated?
Read the account's code. A delegated account's code is a short designator, 0xef0100 followed by the delegate's address; an ordinary account has no code. This dashboard reads that field for every account seen in a type 4 transaction.
What is an EIP-7702 sweeper?
A malicious delegate contract. If an attacker gets a wallet's owner to sign an authorization, the wallet's code points at a contract that forwards any ETH or tokens sent to it to the attacker. The owner can replace it by signing a new authorization that points elsewhere or to the zero address.
Can a delegation be undone?
Yes. The account's owner signs a new authorization, either to a different contract or to the zero address, which clears the code. The dashboard counts clears and re-delegations, so net delegated accounts can fall as well as rise.
Is EIP-7702 only on Ethereum?
No. Several EVM chains adopted it after Ethereum's Pectra upgrade. The dashboard reads each covered chain on its own, since an authorization usually names one chain id; one signed with chain id zero is valid on every chain.
- EOA
- An externally owned account: an address controlled by a private key, with no code of its own unless it delegates under EIP-7702.
- Authorization
- A signed message by which an account names the contract its code should point to, carried in a type 4 transaction.
- Delegation designator
- The code written to a delegated account: a fixed prefix followed by the delegate contract's address.
- Sweeper
- A malicious delegate contract that moves any funds an account receives to an attacker's address.
Related
More apps like this.
Wallet Drainer Tracker: Phishing Losses by Month
What wallet drainers take each month, on which chains and through which signatures: approvals, permits, NFT listings and delegations.
Multi-chainEthereumToken Approval Checker: Open Allowances by Wallet
Every spender that can still move a wallet's tokens or NFTs, with the allowance, when it was granted and the transaction that set it.
Multi-chainEthereum Daily Transactions and Active Addresses
Transactions, active senders and new addresses on Ethereum mainnet each day, by transaction type, with likely spam flagged apart.
EthereumNext Ethereum Upgrade: Glamsterdam Status and Fork History
What the next Ethereum upgrade changes, where it stands in testing and what each past fork measurably changed on chain.
EthereumSafe Multisig Checker: Owners, Threshold and Modules
Inspect a Safe before trusting it: its signers, how many must sign, the modules and guards that can act on it and its recent changes.
Multi-chainEthereumBase+3Ethereum Gas Tracker
Base fee, priority fee and gas used on Ethereum, block by block, with the cost of a transfer, a swap and a mint.
EthereumBuild EIP-7702 Adoption: Delegated EOAs and Top Contracts on verified data.
Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.