Read the request before you sign it.
Plain-language explanations of EVM wallet requests, including the permissions people now give AI agents. Every example is fictional. Nothing here connects to a wallet or looks at an address.
Start here
The five distinctions from the practice page, one page each.
- Connecting is not approvingConnecting your wallet to an app shares your account with it. It does not give the app any of your tokens. Token approvals are separate requests.
- An approval is not a transferApproving 50 tokens sets how much a spender may move later. It does not move them now.
- Unlimited means unlimitedA maximum approval is not tied to the purchase you are making. It covers later transfers by the same spender while it stays in place.
- Disconnecting does not revoke approvalsDisconnecting an app removes its connection to your account. Token approvals you already gave stay on-chain until you change them.
- Setting an allowance to zero does not refundRevoking stops future spending. It does not bring back tokens that already moved.
Request types
One page per kind of wallet request: what to read in the prompt, what it lets the other party do, what it does not do, how long it lasts and how to undo it. Each ends with one fictional practice question.
- Token approval (ERC-20 approve)A transaction that lets another address, the spender, move up to a set amount of one token out of your account, until you change it.
- Increase allowance (increaseAllowance)A function some tokens offer that adds to an existing allowance instead of replacing it. The number in the request is the amount added, not the new total.
- Approval for all (setApprovalForAll)A transaction that lets an operator manage every token you hold in one NFT or multi-token collection contract.
- Permit signature (EIP-2612)An off-chain signature that sets an ERC-20 allowance once anyone submits it to the token contract. Signing costs no gas, but the result is a normal allowance.
- Permit2 approvals and signaturesA shared approval contract. You approve the Permit2 contract once per token, then sign messages that give individual spenders an amount and an expiration, or a one-time transfer.
- Typed-data signature (eth_signTypedData_v4)A request to sign structured data. What the signature authorizes depends on the contract or service that will check it.
- Message signature (personal_sign)A request to sign a readable message. A fixed prefix means the signed data can never be a valid Ethereum transaction.
- Raw hash signature (eth_sign)A legacy signing method that, as implemented in MetaMask, signed an arbitrary hash with no message prefix. You cannot read what the hash stands for.
- Account code delegation (EIP-7702 authorization)A signed authorization that points your regular account (EOA) at a contract’s code. Calls to your account then run that code with your account’s assets.
- 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.
- Send a transaction (eth_sendTransaction)A request to create, sign and send a transaction. A plain transfer moves value once it is included; the same request type also carries contract calls, including approvals.
Agent permissions
What you are letting an AI agent do with your wallet: session keys, spending limits, ERC-7715 permission grants, “unlimited to save gas” approvals and x402 payments.
- A session key limited to 25 a day for 7 daysAn agent asks for its own key, accepted by your account only within a daily limit. Read what the limit counts, when it resets, and what it leaves open.
- An unlimited approval “to save gas”An agent asks for a maximum token approval so it does not have to ask again. The saving is real; so is the missing ceiling.
- An ERC-7715 grant with a spend limit and expiryAn agent asks your wallet for an execution permission with a periodic token limit and an expiry. Read each field: who gets it, how much per period, until when, and whether you can change it.
- An x402 pay-per-request payment vs a standing allowanceAn agent pays for one API request by signing a single, exact transfer. Compare that with an approval that lets a service charge you again and again.
Incident explainers
Which kind of permission a real incident relied on, in plain words, with a fictional replica of the prompt. Facts come only from the affected project’s own posts.
- cow.fi domain hijack: a familiar address, unfamiliar requestsApril 14, 2026 · CoW Swap (cow.fi)
For docs teams and AI assistants
- Embeddable practice cards for wallet and protocol docs: no scripts, no cookies, no tracking.
- llms.txt and llms-full.txt: every page in markdown for AI assistants.
- Every explainer has a markdown copy: add
.mdto its address. - Corrections and changelog.