← Back to Blog
Web3 Security · 8 min read · November 16, 2026

What Is a Wallet Permission? Session Keys and Spend Permissions Explained

A token approval asks one question and never expires. A wallet permission asks several — which token, how much, how often, until when, at which contract — and the smart account refuses anything outside them. Different objects, different signatures, different revoke paths, and the gap between them is where the largest losses still happen.

Three things everyone calls “permission”

“I clicked allow” covers three mechanisms with three different cleanup paths. Confusing them is how people revoke one thing, feel safe, and stay exposed to the other two.

Only the second is designed to be narrow. The first is unlimited by default, and the third is not a permission at all: it changes what your account is.

How a session key is actually granted

Three drafts describe the stack: ERC-7715 for how an app asks, ERC-7710 for how the wallet approves onchain, ERC-7679 for how the account enforces the rules.

  1. The app asks. Each request names a permission type — native transfer, ERC-20 transfer or contract call — and attaches policies: a spend cap with a refill period, a contract allowlist, a rate limit, a gas ceiling and an expiry.
  2. The wallet turns the ask into a sentence. Instead of calldata you read something like “this app may spend up to 50 USDC per week, only on this contract, until 30 November”, and only then is the permission provisioned.
  3. The app signs with the session signer. Every execution is checked against the policies, and any breach reverts rather than settles.

The session account usually holds no funds. It is a signing key, not a custody point: execution is redeemed from your smart account, so an app can act without a funded hot wallet.

The numbers behind the shift

More than 1.25 billion smart-wallet actions have settled on Ethereum through ERC-4337, over 50 million addresses carry an EIP-7702 delegation, and Safe passed 63 million accounts in the second quarter of 2026. Coinbase shipped the model to developers as spend permissions: a manager contract is added as an owner of the wallet, tracks cumulative spend in storage, and reverts anything above the limit.

The pressure to get details right is measurable. Drainer losses fell from roughly $494 million across more than 332,000 wallets in 2024 to about $83.85 million across 106,106 wallets in 2025, an 83% drop as signature attacks gave way to impersonation and malware. Fewer signatures, larger amounts — exactly the profile of a permission grant.

Five ways a permission stops protecting you

The cap is the entire security model

A rule allowing 5,000 USDC a day for thirty days is doing exactly what you approved. The limit is not a safety net under the grant; it is the grant. A cap nobody read does not exist.

Contract-call permissions are the loosest

Allowing a contract call means enumerating function selectors. The draft calls this type the most flexible and the most error-prone, because a broad selector set on a router is a blank cheque attached to your account.

Lifetime is the quiet multiplier

A thirty-day session is thirty days of exposure. If the app persists that ephemeral key on a server and the server is breached, the attacker inherits the session for its remaining life. Session keys belong in client memory, rotated on a short timer.

The enforcement is code you did not audit

A policy is only as real as the module checking it. If an enforcer misreads the cap, the rule is decorative. The delegation framework ships more than thirty caveat enforcers — a lot of surface for one vendor to get right.

You approve a sentence, not calldata

ERC-7715 is blunt here: malicious applications can pose as legitimate ones and persuade users into broad permissions, so wallets must display asks clearly and warn about dangerous ones. A prompt that reads like a login while provisioning a spend permission is this model’s phishing vector.

One more asymmetry: the same request becomes a Safe module for one user, a Kernel validator for another and a Coinbase permission for a third. Revoking in one wallet says nothing about the others.

Six questions before you tap allow

  1. Which asset — the token, or the chain’s native currency?
  2. What is the cap, per day, per week or lifetime?
  3. Which contracts, and for contract calls, which functions?
  4. When does it expire?
  5. Can the app ask to widen scope later?
  6. Can you revoke without the app’s cooperation?

Where the revoke switch actually is

Session permissions are not allowances, so a token-approval revoker may not list them. Look in the wallet’s own permissions screen, which calls wallet_revokePermissions or an equivalent. Some wallets disable a session instantly by flag; others need a transaction with gas. Coinbase exposes listing and revoking by permission hash. A 7702 delegation is cleared a third way, by authorising the zero address, and appears in neither list.

What this means for agent wallets

This is the first model where limiting blast radius is enforceable rather than aspirational: an agent holding a session key can trade only to the cap, only on allowlisted contracts, only until the clock runs out. The realistic failure is not an agent draining an account. It is a human approving a thirty-day uncapped grant because the screen was long and the logo looked right.

Frequently Asked Questions

Is a wallet permission the same as a token approval?

No. An approval is a number inside a token contract, with no scope and no expiry, cleared by a write transaction. A permission is a rule set enforced by a smart account, with a cap, allowed contracts and an end date. They are granted by different signatures and revoked in different places.

Can a session key drain my whole wallet?

Only within the limits you approved, unless the grant is uncapped, long-lived or broad enough to be an approval by another name. That is why the cap, the contract allowlist and the expiry are the security model rather than fine print.

How do I revoke a wallet permission?

Open the wallet’s permissions or sessions screen. Session grants are not allowances, so a token-approval revoker may not show them. Some wallets revoke by disabling a flag instantly, others need a transaction that costs gas.

Do hardware wallets help when I grant a permission?

Partly. The device protects the key, but a permission request is a structured signature that many screens still render as a hash. Clear-signing descriptors such as ERC-7730 are the fix, and coverage is still thin.

Why does an app ask for a permission instead of a transaction?

Because it wants to act later without prompting you each time: subscriptions, automated trades inside a cap, in-game purchases. That is the trade, convenience in exchange for a standing rule, which is exactly why the rule should be narrow and short.

Every permission starts on a page someone built

A grant is only as trustworthy as the front end that asked for it. RootCrak’s autonomous scanner checks your domains, front-end assets and cloud surfaces for the tampering and lookalikes that precede a drain.

Get a Free Security Scan