# Execution permission request (ERC-7715)

> An app or AI agent asks your wallet to let a separate session account execute transactions from your account, within stated limits, without asking you each time.

- Request: `wallet_requestExecutionPermissions (earlier drafts: wallet_grantPermissions)`
- Standard: ERC-7715 (Draft)
- Track: Request types
- Checked against sources: 2026-11-04
- Review status: drafted with AI assistance, awaiting human review
- Canonical page: https://walletpermissions.com/learn/requests/erc-7715-permissions

Education only. This does not assess any real request, wallet or app, and is not advice to sign or not sign. Every app, token and address in the practice card is fictional.

## What to read in the prompt

- `to`: the session account that receives the permission.
- The permission type and its data, such as a token, an amount and a period.
- The rules, such as an `expiry` timestamp.
- `isAdjustmentAllowed`: whether your wallet may let you change the terms.

## What it lets the other party do

- ERC-7715 is for “executing transactions for users without a wallet connection” and with “a wallet connection that is scoped with permissions.” The `to` account redeems the permission to have your account act within its terms.
- The ERC does not define the permission types. MetaMask documents, for example, `erc20-token-periodic`: “a per-period limit for ERC-20 token transfers. At the start of each new period, the allowance resets.”

## What it does not do

- What is granted can differ from what was requested: “it is not guaranteed that the values received are equivalent to those requested.”
- It only limits what the permission type limits. MetaMask’s documented parameters for `erc20-token-periodic` are the token, the amount per period, the period length, a start time and a justification. None of them names a recipient.

## How long it lasts

- Until its `expiry` rule, if one is set, or until it is revoked.
- The ERC places enforcement on the wallet: “Wallets MUST correctly enforce permissions. Ultimately, users must trust that their wallet software is implemented correctly.”

## How to undo it

- ERC-7715 defines `wallet_revokeExecutionPermission`. How a wallet shows granted permissions and revocation varies by wallet.

## Status and naming

- ERC-7715 is a Draft. Its text changed on 2026-01-16: the method that earlier drafts called `wallet_grantPermissions` is now `wallet_requestExecutionPermissions`, and the expiry moved into a rule.

## Practice question (fictional)

A fictional budgeting agent, Pebble Pass Assistant, asks for a permission.

| Field | Value |
| --- | --- |
| Request type | wallet_requestExecutionPermissions |
| to | Pebble Pass session account (fictional) |
| Permission | erc20-token-periodic |
| Token | LEAF (fictional) |
| Per period | 10 LEAF every 1 day |
| Rule | expiry in 30 days |

**Question:** Over the 30 days, could the session account move more than 10 LEAF in total?

**Answer:** Yes. The limit resets each period. Over 30 daily periods that is up to 300 LEAF, unless you revoke it sooner.

## Sources

- [ERC-7715: Request Permissions from Wallets](https://ercs.ethereum.org/ERCS/erc-7715). Ethereum ERCs. Draft; created 2024-05-24; text last changed 2026-01-16. Checked 2026-11-04.
- [ERC-7715 as of 2025-02-20 ("Grant Permissions from Wallets", wallet_grantPermissions)](https://github.com/ethereum/ERCs/blob/e1d58b0afa/ERCS/erc-7715.md). ethereum/ERCs on GitHub. Draft text at commit e1d58b0afa, 2025-02-20. Checked 2026-11-04.
- [Advanced Permissions (ERC-7715)](https://docs.metamask.io/smart-accounts-kit/concepts/advanced-permissions/). MetaMask Smart Accounts Kit docs. Page as published on the check date. Checked 2026-11-04.
- [Advanced Permissions reference: permission types](https://docs.metamask.io/smart-accounts-kit/reference/advanced-permissions/permissions/). MetaMask Smart Accounts Kit docs. Page as published on the check date. Checked 2026-11-04.
