Sato Hub
Wallet Infrastructure

MetaMask Delegation Framework

MetaMask's official smart-account delegation contracts — grant an AI agent scoped, revocable permissions instead of a private key.

  • Sato Score72
  • ChainsEthereum, Base +1
ActiveUnverifiedActive · 1d ago

MetaMask Delegation Framework is an open-source wallet infrastructure by MetaMask on Ethereum and Base, with last code activity on 2026-10-20 (Active). Latest release on 2025-07-24. Sato Score 72/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install MetaMask Delegation Framework →

Last commit Oct 20, 2026 · Last release Jul 24, 2025 · ★ 231

Listed from gator.metamask.io on 2026-07-19. Install: not attempted. Evidence →

Next step

Watch MetaMask Delegation Framework

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on metamask/delegation-framework before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

The Delegation Framework (branded Gator) is MetaMask's official ERC-7710-style smart-contract system for delegating scoped, revocable permissions from a smart account to another address or agent, rather than sharing a private key outright. It's a reference implementation builders point to for giving an onchain agent bounded spending/action authority under human control. 215 GitHub stars, actively maintained.

Sato Score

72/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
19/20
Interface verifiability
0/10
Docs & demo
6/10
Listing transparency & provenance
9/15
Independent verification
3/10

Evidence — listed vs checked · what the words mean

Listed from gator.metamask.io on 2026-07-19. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedEthereum, Base, Multichainself-reporteddocs.metamask.ioas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportedgator.metamask.ioas of 2026-10-21
Recent activitylast release 2025-07-24 · last commit 2026-10-20observedgithub.com/MetaMask/delegation-framework2026-10-21
Install worksdocumented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_specself-reportedgithub.com/MetaMask/delegation-frameworkas of 2026-09-14
Website answersanswered (HTTP 301)observedgator.metamask.io2026-10-21
Daily check record90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Built byMetaMaskconfidence 0.85self-reportedgator.metamask.ioas of 2026-09-18
Sato Score72/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-21

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — not run by us — no falsifiable install+entry probe from deploy_spec

Runtime: Foundry / Solidity 0.8.23 (smart-contract framework, not a runnable server)

forge build
forge test
forge script script/DeployDelegationFramework.s.sol --rpc-url <your_rpc_url> --private-key $PRIVATE_KEY --broadcast

You supply: .env populated from .env.example, then `source .env`, PRIVATE_KEY (deployer key for forge scripts — risk: funded deployer private key in env), RPC URL for the target chain; optional local fork via `anvil -f <your_rpc_url>`

Read from the project’s own docs as of 2026-09-14. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-23

100%of 91 checks since 2026-07-23 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-21, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
72
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Measured on-chain — week 2026-W43

What we can observe about this project on-chain, from public reads, with the method and sample size attached to every figure. A raw deployment count is not an adoption figure and is shown separately below.

Permissions revoked on-chainerc7715_permissions · Arbitrum
0Proof
Accounts whose permissions were usederc7715_permissions · Arbitrum
7,560Proof
Permissions exercised (delegations redeemed)erc7715_permissions · Arbitrum
17,549Proof
Permissions exercised (delegations redeemed)erc7715_permissions · Base
19,723Proof
Accounts whose permissions were usederc7715_permissions · Base
7,096Proof
Permissions revoked on-chainerc7715_permissions · Base
1Proof
Accounts whose permissions were usederc7715_permissions · Ethereum
6,158Proof
Permissions revoked on-chainerc7715_permissions · Ethereum
1Proof
Permissions exercised (delegations redeemed)erc7715_permissions · Ethereum
11,637Proof
Accounts whose permissions were usederc7715_permissions · Optimism
146Proof
Permissions revoked on-chainerc7715_permissions · Optimism
0Proof
Permissions exercised (delegations redeemed)erc7715_permissions · Optimism
288Proof
Accounts whose permissions were usederc7715_permissions · Polygon
7,603Proof
Permissions revoked on-chainerc7715_permissions · Polygon
0Proof
Permissions exercised (delegations redeemed)erc7715_permissions · Polygon
17,666Proof

Rates on fewer than 20 observations are shown but not quotable. Full venue detail: erc7715_permissions · The onchain agent economy.

Details

Chains
Ethereum, Base, Multichain
Agent types
Smart-account delegation framework
Open source
Yes
Last checked
2026-10-21

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#wallet-infrastructure#smart-account#delegation#erc-7710#permissions

Where MetaMask Delegation Framework fits

Related concepts: How Agents Use Wallets, What Are Onchain Agents?

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to MetaMask Delegation Framework's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 26, 2026
    Sato Score tier: Medium → High
    Score 62 → 72.
  2. Sep 18, 2026
    Auto-enriched: creator name
  3. Sep 7, 2026
    Sato Score tier: High → Medium
    Score 70 → 60.
  4. Sep 1, 2026
    Sato Score tier: Medium → High
    Score 67 → 70.
  5. Jul 24, 2026
    Sato Hub began tracking this listing
  6. Jul 20, 2026
    Edited: deploy spec
  7. Jul 19, 2026
    Edited: chains supported, docs url
  8. Jul 19, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about MetaMask Delegation Framework

Is MetaMask Delegation Framework open source?
Yes. MetaMask Delegation Framework is open source under the Apache-2.0 OR MIT license; the repository is https://github.com/MetaMask/delegation-framework. Checked as of 2026-10-21.
Which chains does MetaMask Delegation Framework support?
MetaMask Delegation Framework lists support for Ethereum, Base, Multichain as of 2026-10-21.
Is MetaMask Delegation Framework still maintained?
The most recent code activity Sato Hub observed was on 2026-10-20 (last commit 2026-10-20, last release 2025-07-24), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run MetaMask Delegation Framework?
Foundry / Solidity 0.8.23 (smart-contract framework, not a runnable server). Install: forge build && forge test. Entry: forge script script/DeployDelegationFramework.s.sol --rpc-url <your_rpc_url> --private-key $PRIVATE_KEY --broadcast. This is taken from the project's own documentation and has not been reproduced by Sato Hub.
Is MetaMask Delegation Framework verified on Sato Hub?
No independent verification is on record for MetaMask Delegation Framework; its verification status is "Unverified" and its Sato Score is 72 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "MetaMask Delegation Framework — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/metamask-delegation-framework

Data last refreshed 2026-10-21; 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.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.