ERC-7715 permission grants (MetaMask Delegation Framework)
What one unit is, what it costs to enter, and what we can observe onchain.
- Week2026-W43
- Updated2026-10-19
Live·Updated
19,723 delegated permissions were exercised on Base in the 7 days to 2026-10-19 — the largest of 5 chains, each counted separately.
How measured · RedeemedDelegation events on the singleton DelegationManager over the trailing window, read with eth_getLogs and no sampling; a grant emits nothing, so this is a floor on permissions granted. The trailing window, read once a week.
- One unit is
- one delegation redeemed (a scoped permission actually exercised by a session key)
- Entry costs
- free — a grant is an off-chain signature; gas only on redemption
Trend — registered, week over week
Gaps in a line are weeks the value was unknown. Chains are never combined.
What we measured
Arbitrum
Permissions exercised (delegations redeemed)RedeemedDelegation event on the DelegationManager (one per delegation exercised)
17,549Proof
Accounts whose permissions were useddistinct rootDelegator address with at least one RedeemedDelegation in the window
7,560Proof
Permissions revoked on-chainDisabledDelegation event on the DelegationManager (an explicit on-chain revocation)
0Proof
▸▾ How these were measured
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. Expiry is silent, so this undercounts permissions that stopped being valid.
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. A rootDelegator is the account that granted the permission; the redeemer (session key / agent) is counted separately as extra_distinct_redeemers.
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. A redemption through a delegation chain emits one event per link.
Base
Permissions exercised (delegations redeemed)RedeemedDelegation event on the DelegationManager (one per delegation exercised)
19,723Proof
Accounts whose permissions were useddistinct rootDelegator address with at least one RedeemedDelegation in the window
7,096Proof
Permissions revoked on-chainDisabledDelegation event on the DelegationManager (an explicit on-chain revocation)
1Proof
▸▾ How these were measured
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. A redemption through a delegation chain emits one event per link.
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. A rootDelegator is the account that granted the permission; the redeemer (session key / agent) is counted separately as extra_distinct_redeemers.
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. Expiry is silent, so this undercounts permissions that stopped being valid.
Ethereum
Permissions exercised (delegations redeemed)RedeemedDelegation event on the DelegationManager (one per delegation exercised)
11,637Proof
Accounts whose permissions were useddistinct rootDelegator address with at least one RedeemedDelegation in the window
6,158Proof
Permissions revoked on-chainDisabledDelegation event on the DelegationManager (an explicit on-chain revocation)
1Proof
▸▾ How these were measured
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. A rootDelegator is the account that granted the permission; the redeemer (session key / agent) is counted separately as extra_distinct_redeemers.
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. Expiry is silent, so this undercounts permissions that stopped being valid.
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. A redemption through a delegation chain emits one event per link.
Optimism
Permissions exercised (delegations redeemed)RedeemedDelegation event on the DelegationManager (one per delegation exercised)
288Proof
Accounts whose permissions were useddistinct rootDelegator address with at least one RedeemedDelegation in the window
146Proof
Permissions revoked on-chainDisabledDelegation event on the DelegationManager (an explicit on-chain revocation)
0Proof
▸▾ How these were measured
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. A rootDelegator is the account that granted the permission; the redeemer (session key / agent) is counted separately as extra_distinct_redeemers.
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. Expiry is silent, so this undercounts permissions that stopped being valid.
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. A redemption through a delegation chain emits one event per link.
Polygon
Permissions exercised (delegations redeemed)RedeemedDelegation event on the DelegationManager (one per delegation exercised)
17,666Proof
Accounts whose permissions were useddistinct rootDelegator address with at least one RedeemedDelegation in the window
7,603Proof
Permissions revoked on-chainDisabledDelegation event on the DelegationManager (an explicit on-chain revocation)
0Proof
▸▾ How these were measured
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. A rootDelegator is the account that granted the permission; the redeemer (session key / agent) is counted separately as extra_distinct_redeemers.
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. Expiry is silent, so this undercounts permissions that stopped being valid.
- The DelegationManager serves every Delegation Framework user, human sessions included — this is framework activity, not agent activity specifically. A redemption through a delegation chain emits one event per link.
Confirmed contracts
Every address here was confirmed on-chain twice: bytecode present, and the block explorer's verified contract name matching the claim. A confirmation older than the re-check interval renders as stale rather than as a number that looks current.
| Chain | Contract | Role | Confirmed |
|---|---|---|---|
| Arbitrum | MetaMask DelegationManager (Arbitrum)0xdb9B1e94B5b69Df7e401DDbedE43491141047dB3 | delegation-manager | 2026-09-08 · source |
| Base | MetaMask DelegationManager (Base)0xdb9B1e94B5b69Df7e401DDbedE43491141047dB3 | delegation-manager | 2026-09-08 · source |
| Ethereum | MetaMask DelegationManager (Ethereum)0xdb9B1e94B5b69Df7e401DDbedE43491141047dB3 | delegation-manager | 2026-09-08 · source |
| Optimism | MetaMask DelegationManager (Optimism)0xdb9B1e94B5b69Df7e401DDbedE43491141047dB3 | delegation-manager | 2026-09-08 · source |
| Polygon | MetaMask DelegationManager (Polygon)0xdb9B1e94B5b69Df7e401DDbedE43491141047dB3 | delegation-manager | 2026-09-08 · source |
How this is measured
RedeemedDelegation / EnabledDelegation / DisabledDelegation logs on the singleton DelegationManager (0xdb9B…7dB3, identical on every chain), trailing 7 days, walked backwards; whole window, no sampling.
Each figure is read per chain and per lifecycle stage and is never added to another. A rate computed on fewer than 20 observations is stored and shown as “not enough readings”, never as a finding; a value that could not be read says “not measured” with the reason.
What this page cannot settle
- The framework serves human MetaMask Smart Account sessions as well as agents. Framework activity, not agent activity.
- Headline safety: Per chain and per stage only. Never 'permissions granted' — that is not observable.
- Every method on this page is EVM-shaped. Solana identity registries are covered elsewhere as upper bounds; Solana payment settlement is not covered anywhere on this site.
In the directory as MetaMask Delegation Framework.
Cite this
Sato Hub, "ERC-7715 permission grants (MetaMask Delegation Framework) — measured on-chain", satohub.ai/agent-economy/erc7715_permissions, as of 2026-10-19. CC-BY.
Data: satohub.ai/api/export/adoption.json?venue=erc7715_permissions (CC-BY, current week; every row carries its method, evidence tier and sample size).
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about ERC-7715 permission grants (MetaMask Delegation Framework)
- What is one unit of ERC-7715 permission grants (MetaMask Delegation Framework)?
- one delegation redeemed (a scoped permission actually exercised by a session key). Counting anything else as a "ERC-7715 permission grants (MetaMask Delegation Framework) agent" would compare different objects, so every row on this page names the stage it counts.
- What does it cost to enter ERC-7715 permission grants (MetaMask Delegation Framework)?
- free — a grant is an off-chain signature; gas only on redemption. Entry cost is why raw sizes are not comparable across venues: free and permissionless is a different market from bonded.
- How is ERC-7715 permission grants (MetaMask Delegation Framework) measured?
- Public chain reads on 5 chains, keylessly, once a week — this view is the week beginning 2026-W43. Each row carries its method, evidence tier and sample size, and a row we could not read is null rather than zero.
- Does a count here say the agents work?
- No. A registration, a launch or a staked service is an entry in a contract. Nothing about funding, activity, competence or safety is implied, and what happens after entry is measured as its own stage.
SourcesWhere the data comes fromShowHide
Sources — the standards this venue implements
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "ERC-7715 permission grants (MetaMask Delegation Framework) — measured on-chain." Sato Hub, updated 2026-10-19, accessed 2026-10-24. https://satohub.ai/agent-economy/erc7715_permissionsData last refreshed 2026-10-19; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.