ERC-7715 primary sources — 2026-05-07

Project status in this pass

• No standalone ERC-7715 whitepaper or litepaper surfaced.
• The clearest current source of truth was the draft ERC itself, backed by the raw ERC markdown and MetaMask’s implementation-facing Advanced Permissions materials.
• The sources consistently frame ERC-7715 as wallet-mediated permission infrastructure for delegated execution, not just as smoother wallet UX.

Primary-source snapshots

1) Canonical ERC page

• URL: https://eips.ethereum.org/EIPS/eip-7715
• Key excerpt/signals:
  • The abstract says wallet_requestExecutionPermissions lets a dapp request permissions from a wallet to execute transactions on the user’s behalf.
  • The motivation names two target use cases: execution for disconnected users and scoped execution for connected users.
  • The examples center on permissions, rules, session accounts, and later redemption through a delegation manager.
• Why it mattered:
  • This is the clearest evidence that ERC-7715 belongs in the corpus as wallet authority and delegation-request infrastructure.

2) Raw ERC markdown / permission and rule model

• URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-7715.md
• Key excerpt/signals:
  • Permissions and rules are typed extensible objects rather than a fixed closed schema.
  • The spec warns that type-name collisions matter and says new permission and rule types should be defined by additional ERCs.
  • isAdjustmentAllowed explicitly allows the wallet to attenuate requested authority to match user approval terms.
• Why it mattered:
  • These details show that ERC-7715 is creating an extensible permission namespace and a wallet-mediated policy boundary, not just one canned session-key flow.

3) Raw ERC markdown / response and redemption flow

• URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-7715.md
• Key excerpt/signals:
  • The permission response may differ from the original request and includes context, dependencies, and delegationManager.
  • dependencies can force the dapp to deploy undeployed accounts before permission redemption.
  • Redeeming permissions routes through ERC-7710 redeemDelegations on the returned delegation manager.
• Why it mattered:
  • This is the strongest source-level evidence that ERC-7715 is the wallet-side request layer above a broader delegated-execution stack.

4) MetaMask Advanced Permissions launch note

• URL: https://metamask.io/news/introducing-advanced-permissions
• Key excerpt/signals:
  • MetaMask says Advanced Permissions are built on ERC-7715 and let users approve exactly what a dapp can do in a single interaction.
  • The post says execution happens through a session account that never holds user funds and redeems permissions via ERC-7710 delegation.
  • It highlights human-readable approval, user adjustment of terms, revocability, and concrete use cases like subscriptions, DCA, and AI agents.
• Why it mattered:
  • This is strong evidence that ERC-7715 is already becoming implementation-facing wallet authority infrastructure.

5) MetaMask Smart Accounts Kit overview

• URL: https://metamask.io/developer/delegation-toolkit
• Key excerpt/signals:
  • MetaMask’s toolkit says it provides a unified API to request Advanced Permissions (ERC-7715).
  • The page frames the standard as support for delegated actions, automation, and agentic AI use cases.
  • It presents granular permission sharing as a core smart-account behavior rather than a niche extension.
• Why it mattered:
  • This shows a major wallet vendor is treating ERC-7715 as a real developer-facing control plane for delegated behavior.

Working conclusion

ERC-7715 is best cataloged as wallet permission-delegation infrastructure. The decisive evidence in this pass was the ERC’s extensible permission-and-rule namespace, wallet-mediated attenuation and discovery model, ERC-7710 redemption path, and MetaMask’s concrete packaging of the standard into human-readable, revocable Advanced Permissions for automation and agent-driven execution.