# WalletPermissions > Plain-language explanations of EVM wallet requests and AI-agent wallet permissions, practised on fictional examples. No wallet connection, no address input and no ratings of any request, app or wallet: education only. Each page states what the request is, what it lets the other party do, what it does not do, how long it lasts, how to undo it, and the dated primary sources (EIPs, ERCs, official docs) it was checked against. Pages drafted with AI assistance say so. To act on a real account, people use established tools such as Revoke.cash or Etherscan’s token approval checker; this site never does. ## Start here - [Connecting is not approving](https://walletpermissions.com/learn/connect-vs-approve.md): Connecting 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 transfer](https://walletpermissions.com/learn/bounded-allowance.md): Approving 50 tokens sets how much a spender may move later. It does not move them now. - [Unlimited means unlimited](https://walletpermissions.com/learn/unlimited-allowance.md): A 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 approvals](https://walletpermissions.com/learn/disconnect-does-not-revoke.md): Disconnecting 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 refund](https://walletpermissions.com/learn/zero-allowance-does-not-refund.md): Revoking stops future spending. It does not bring back tokens that already moved. ## Request types - [Token approval (ERC-20 approve)](https://walletpermissions.com/learn/requests/approve.md): 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)](https://walletpermissions.com/learn/requests/increase-allowance.md): 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)](https://walletpermissions.com/learn/requests/set-approval-for-all.md): A transaction that lets an operator manage every token you hold in one NFT or multi-token collection contract. - [Permit signature (EIP-2612)](https://walletpermissions.com/learn/requests/permit.md): 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 signatures](https://walletpermissions.com/learn/requests/permit2.md): A 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)](https://walletpermissions.com/learn/requests/sign-typed-data.md): A request to sign structured data. What the signature authorizes depends on the contract or service that will check it. - [Message signature (personal_sign)](https://walletpermissions.com/learn/requests/personal-sign.md): 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)](https://walletpermissions.com/learn/requests/eth-sign.md): 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)](https://walletpermissions.com/learn/requests/eip-7702-authorization.md): 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)](https://walletpermissions.com/learn/requests/erc-7715-permissions.md): 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)](https://walletpermissions.com/learn/requests/send-transaction.md): 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 - [A session key limited to 25 a day for 7 days](https://walletpermissions.com/learn/agents/session-key-daily-limit.md): An 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”](https://walletpermissions.com/learn/agents/unlimited-approval-to-save-gas.md): 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 expiry](https://walletpermissions.com/learn/agents/erc-7715-spend-limit-expiry.md): An 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 allowance](https://walletpermissions.com/learn/agents/x402-payment-vs-allowance.md): An 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 - [cow.fi domain hijack: a familiar address, unfamiliar requests](https://walletpermissions.com/incidents/cow-swap-domain-hijack-2026-04.md): For about 4.5 hours on 14 April 2026, attackers controlled the cow.fi domain and served a phishing site. Visitors who signed its requests lost tokens. The lesson: the address bar can be right while the request is wrong. ## Optional - [All pages in one file](https://walletpermissions.com/llms-full.txt) - [Embeddable practice cards](https://walletpermissions.com/embed) - [Corrections and changelog](https://walletpermissions.com/changelog) - [Interactive practice](https://walletpermissions.com/) --- # Connecting is not approving > Connecting 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. - Request: `Connection request` - Standard: Wallet connection; ERC-20 for approvals - Track: Start here - Checked against sources: 2026-11-04 - Review status: drafted with AI assistance, awaiting human review - Canonical page: https://walletpermissions.com/learn/connect-vs-approve 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 happens - A connection lets the app see the account you chose and send you further requests. - An ERC-20 approval is a separate request that lets a spender move tokens. You get a separate prompt for it. ## What it does not do - A connection alone does not set an ERC-20 allowance. ## How to undo it - Disconnect the app in your wallet’s settings. MetaMask’s guide on disconnecting explains that this is different from revoking token approvals; see the disconnect lesson. ## Practice question (fictional) Every app and token here is fictional. | Field | Value | | --- | --- | | Action | Connect to fictional Orchard app | | Network | Fictional Ethereum EVM context | | Token / spender | Fictional LEAF / Orchard (no real address) | | Amount | No token allowance requested | | Expiry | Connection until disconnected | | Request type | Connection only | **Question:** Does this connection alone give Orchard a token allowance? **Answer:** No. A connection grants app access to the selected account connection. It is not an ERC-20 approve call. Other requests can follow: review each separately. ## Sources - [How to disconnect your wallet from a dapp](https://support.metamask.io/more-web3/dapps/disconnect-wallet-from-a-dapp/). MetaMask Support. Page as published on the check date. Checked 2026-11-04. - [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04. --- # An approval is not a transfer > Approving 50 tokens sets how much a spender may move later. It does not move them now. - Request: `approve(spender, 50)` - Standard: ERC-20 - Track: Start here - Checked against sources: 2026-11-04 - Review status: drafted with AI assistance, awaiting human review - Canonical page: https://walletpermissions.com/learn/bounded-allowance 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 happens - ERC-20 `approve` “allows `_spender` to withdraw from your account multiple times, up to the `_value` amount.” - The tokens move only when the spender calls `transferFrom`. ## What it does not do - It does not transfer tokens at the moment you approve. - Standard ERC-20 approvals have no expiry. ## How to undo it - Send `approve(spender, 0)`. See the full approval explainer for details. ## Practice question (fictional) Every app and token here is fictional. | Field | Value | | --- | --- | | Action | Set standard ERC-20 allowance for fictional Orchard | | Network | Fictional Ethereum EVM context | | Token / spender | Fictional LEAF / Orchard (no real address) | | Amount | 50 fictional LEAF tokens | | Expiry | No expiry in standard ERC-20 allowance | | Request type | Transaction: approve | **Question:** Is this approval distinct from an immediate transfer of 50 tokens? **Answer:** Yes. Standard ERC-20 approve sets the spender’s allowance. A transferFrom is a separate token-moving operation. The spender can use the allowance up to its remaining amount; this card is not a recommendation to approve. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04. --- # Unlimited means unlimited > A maximum approval is not tied to the purchase you are making. It covers later transfers by the same spender while it stays in place. - Request: `approve(spender, maximum)` - Standard: ERC-20 - Track: Start here - Checked against sources: 2026-11-04 - Review status: drafted with AI assistance, awaiting human review - Canonical page: https://walletpermissions.com/learn/unlimited-allowance 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 happens - The spender’s allowance is set to the largest possible value. - ethereum.org: projects do this “to minimize the number of requests required”. ## What it does not do - It is not limited to your first purchase, and it does not expire. ## How to undo it - Send `approve(spender, 0)`, then check your real approvals with Revoke.cash or Etherscan’s token approval checker. ## Practice question (fictional) Every app and token here is fictional. | Field | Value | | --- | --- | | Action | Set maximum allowance for fictional Orchard | | Network | Fictional Ethereum EVM context | | Token / spender | Fictional LEAF / Orchard (no real address) | | Amount | Unlimited (maximum token allowance) | | Expiry | No expiry in standard ERC-20 allowance | | Request type | Transaction: approve | **Question:** Is this allowance limited to the first intended 5-token purchase? **Answer:** No. An unlimited allowance is not bounded by the amount of your intended purchase. The token-level authorization can cover later transfers by that spender while it remains in place. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04. - [How to revoke smart contract access to your crypto funds](https://ethereum.org/guides/how-to-revoke-token-access). ethereum.org. Page as published on the check date. Checked 2026-11-04. --- # Disconnecting does not revoke approvals > Disconnecting an app removes its connection to your account. Token approvals you already gave stay on-chain until you change them. - Request: `Disconnect in wallet settings` - Standard: Wallet connection vs ERC-20 allowance - Track: Start here - Checked against sources: 2026-11-04 - Review status: drafted with AI assistance, awaiting human review - Canonical page: https://walletpermissions.com/learn/disconnect-does-not-revoke 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 happens - The app can no longer see your account through the wallet connection. ## What it does not do - ethereum.org: “if you disconnect your wallet from the project, but you’ve granted token allowance permissions, they can still use those tokens. You need to revoke that access.” ## How to undo it - Revoke the approval itself with `approve(spender, 0)` or `setApprovalForAll(operator, false)`. Revoke.cash and Etherscan’s token approval checker show what your real account has approved. ## Practice question (fictional) Every app and token here is fictional. | Field | Value | | --- | --- | | Action | Disconnect fictional Orchard in wallet settings | | Network | Fictional Ethereum EVM context | | Token / spender | Fictional LEAF / Orchard (no real address) | | Amount | Existing 50-token allowance unchanged | | Expiry | Existing standard allowance has no expiry | | Request type | Connection setting | **Question:** Can an existing token allowance remain after the app is disconnected? **Answer:** Yes. Disconnecting the app connection does not revoke token approvals already recorded on-chain. Connection permissions and token allowances are different layers. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [How to revoke smart contract access to your crypto funds](https://ethereum.org/guides/how-to-revoke-token-access). ethereum.org. Page as published on the check date. Checked 2026-11-04. - [How to disconnect your wallet from a dapp](https://support.metamask.io/more-web3/dapps/disconnect-wallet-from-a-dapp/). MetaMask Support. Page as published on the check date. Checked 2026-11-04. --- # Setting an allowance to zero does not refund > Revoking stops future spending. It does not bring back tokens that already moved. - Request: `approve(spender, 0)` - Standard: ERC-20 - Track: Start here - Checked against sources: 2026-11-04 - Review status: drafted with AI assistance, awaiting human review - Canonical page: https://walletpermissions.com/learn/zero-allowance-does-not-refund 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 happens - A new `approve` “overwrites the current allowance with `_value`”, so a value of 0 leaves the spender nothing to spend. ## What it does not do - It does not reverse completed `transferFrom` calls or recover tokens. ## How to undo it - There is nothing to undo here: this is the undo for future spending. Check what remains with Revoke.cash or Etherscan’s token approval checker. ## Practice question (fictional) Every app and token here is fictional. | Field | Value | | --- | --- | | Action | Set fictional Orchard allowance to zero | | Network | Fictional Ethereum EVM context | | Token / spender | Fictional LEAF / Orchard (no real address) | | Amount | 0 fictional LEAF tokens; 10 previously transferred | | Expiry | No new spending allowance for this spender | | Request type | Transaction: approve with value 0 | **Question:** Does setting allowance to zero reverse a completed 10-token transfer? **Answer:** No. Setting the standard ERC-20 allowance to zero changes the remaining permission for future spending. It does not undo completed transfers or recover tokens that already moved. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04. - [How to revoke smart contract access to your crypto funds](https://ethereum.org/guides/how-to-revoke-token-access). ethereum.org. Page as published on the check date. Checked 2026-11-04. --- # 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. - Request: `approve(spender, amount)` - Standard: ERC-20 - 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/approve 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 - The token: each token contract keeps its own allowances. - The spender: the address that receives the right to move your tokens. It is often a contract, not the app’s name. - The amount: a number, or the maximum possible value, which wallets and apps often call unlimited. - The network the request is on. ## What it lets the other party do - The spender can call `transferFrom` to move your tokens of that token contract. ERC-20 describes `approve` as allowing the spender “to withdraw from your account multiple times, up to the `_value` amount.” - A new `approve` for the same spender replaces the old amount. ERC-20: “If this function is called again it overwrites the current allowance with `_value`.” ## What it does not do - It does not move tokens by itself. Moving them is a separate `transferFrom` call made by the spender. - It does not cover other tokens. - Disconnecting the app in your wallet does not remove it. ethereum.org: if you disconnect but have granted token allowance permissions, “they can still use those tokens.” ## How long it lasts - ERC-20 defines no expiry. The allowance stays until it is used up or you replace it. ethereum.org: “There are no expiration dates on contract permissions.” (That sentence is about ERC-20 style approvals; Permit2 and some newer systems do have expirations.) ## How to undo it - Send a new `approve` for the same spender with an amount of 0. That changes future spending only. It does not return tokens that already moved. - To see the approvals your real account has, use an established external checker such as Revoke.cash or Etherscan’s token approval checker. This site never looks at your account. ## A pattern to recognise - A button labelled “verify”, “claim” or “enable” whose wallet prompt is actually an approval for a spender you do not recognise, often for the maximum amount. Read the prompt, not the button. ## Practice question (fictional) Fictional Lanternfly Swap asks for an approval before your first swap. | Field | Value | | --- | --- | | Request type | Transaction: approve | | Token | MOSS (fictional) | | Spender | Lanternfly Router (fictional contract) | | Amount | 100 MOSS | | You then swap | 40 MOSS | **Question:** After the 40-token swap, can the router still move more of your MOSS without a new approval? **Answer:** Yes. An allowance is a ceiling for repeated `transferFrom` calls, not a single-use pass. If the swap used 40 of it, up to 60 MOSS stays available to the router until you set the allowance to 0. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04. - [How to revoke smart contract access to your crypto funds](https://ethereum.org/guides/how-to-revoke-token-access). ethereum.org. Page as published on the check date. Checked 2026-11-04. - [How to disconnect your wallet from a dapp](https://support.metamask.io/more-web3/dapps/disconnect-wallet-from-a-dapp/). MetaMask Support. Page as published on the check date. Checked 2026-11-04. --- # 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. - Request: `increaseAllowance(spender, addedValue)` - Standard: Not part of ERC-20; OpenZeppelin 4.x extension - 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/increase-allowance 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 - The function name: `increaseAllowance`, not `approve`. - The amount: it is added on top of whatever the spender is already allowed. - The spender and the token, as with any approval. ## What it lets the other party do - It raises the spender’s allowance. OpenZeppelin 4.x documents it as: “Atomically increases the allowance granted to `spender` by the caller.” The new total is the old allowance plus the added amount. - The spender can then use `transferFrom` up to that new total. ## What it does not do - It is not in the ERC-20 standard. OpenZeppelin removed it in Contracts 5.0.0 (released 2023-10-05): “Removed the non-standard `increaseAllowance` and `decreaseAllowance` functions.” Older tokens built on 4.x can still have it; tokens without it reject the call. - It does not move tokens and does not set an expiry. ## How long it lasts - Like any ERC-20 allowance: no expiry, until used up or replaced. ## How to undo it - The standard route is `approve(spender, 0)`, which sets the total to 0 whatever it was. - Check your real approvals with Revoke.cash or Etherscan’s token approval checker. ## A pattern to recognise - A small number in an `increaseAllowance` prompt can sit on top of a large existing allowance. The small number is not the total. ## Practice question (fictional) Fictional Pebble Pass already has an allowance of 500 LEAF from you. It now asks for one more step. | Field | Value | | --- | --- | | Request type | Transaction: increaseAllowance | | Token | LEAF (fictional) | | Spender | Pebble Pass Vault (fictional contract) | | Amount in the call | 20 LEAF | | Existing allowance | 500 LEAF | **Question:** After this request, is Pebble Pass Vault limited to 20 LEAF? **Answer:** No. `increaseAllowance` adds to the existing allowance. The vault would be allowed 520 LEAF in total. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [OpenZeppelin Contracts changelog, 5.0.0 (2023-10-05)](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/CHANGELOG.md). OpenZeppelin. 5.0.0 released 2023-10-05. Checked 2026-11-04. - [OpenZeppelin Contracts 4.9.6 ERC20.sol (increaseAllowance)](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/v4.9.6/contracts/token/ERC20/ERC20.sol). OpenZeppelin. Tag v4.9.6. Checked 2026-11-04. - [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04. --- # Approval for all (setApprovalForAll) > A transaction that lets an operator manage every token you hold in one NFT or multi-token collection contract. - Request: `setApprovalForAll(operator, true)` - Standard: ERC-721 and ERC-1155 - 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/set-approval-for-all 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 - The collection contract the request is sent to. - The operator: the address that receives the right. - The true or false value: `true` grants the right, `false` removes it. ## What it lets the other party do - ERC-721: “Enable or disable approval for a third party (“operator”) to manage all of `msg.sender`’s assets.” ERC-1155: “Enable or disable approval for a third party (“operator”) to manage all of the caller’s tokens.” - The operator can transfer your tokens in that contract. Because the approval is an on/off switch for the operator, not a list of token IDs, it covers whatever you hold in that contract when the operator acts. ## What it does not do - It covers one contract only, not your other collections. - It does not transfer anything by itself, and it sets no price or amount limit. ## How long it lasts - Neither ERC-721 nor ERC-1155 defines an expiry. It stays on until you call `setApprovalForAll(operator, false)`. ## How to undo it - Send `setApprovalForAll(operator, false)` to the same collection contract. It does not return tokens that already moved. - Check your real approvals with Revoke.cash or Etherscan’s token approval checker. ## A pattern to recognise - Marketplaces can ask for this when you list, so the prompt can look routine. A “free mint” or “claim” page asking for it on a collection you already own deserves a second look at the operator. ## Practice question (fictional) You want to list one fictional Paper Heron for sale on fictional Kiteframe Market. You hold six herons. | Field | Value | | --- | --- | | Request type | Transaction: setApprovalForAll | | Collection | Paper Herons (fictional ERC-721) | | Operator | Kiteframe Transfer Helper (fictional contract) | | Value | true | | You hold | 6 herons | **Question:** Does this request cover only the one heron you plan to list? **Answer:** No. Approval for all covers every token you hold in the Paper Herons contract, including the other five, until you switch it off. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [ERC-721: Non-Fungible Token Standard](https://ercs.ethereum.org/ERCS/erc-721). Ethereum ERCs. Final; created 2018-01-24. Checked 2026-11-04. - [ERC-1155: Multi Token Standard](https://ercs.ethereum.org/ERCS/erc-1155). Ethereum ERCs. Final; created 2018-06-17. Checked 2026-11-04. --- # 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. - Request: `eth_signTypedData_v4 with primaryType "Permit"` - Standard: ERC-2612 (uses EIP-712) - 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/permit 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 - It arrives as a signature request, not a transaction. - The primary type `Permit` and the domain’s verifying contract, which is the token. - The fields `spender`, `value` and `deadline`. ## What it lets the other party do - ERC-2612: a call to `permit(...)` “will set `allowance[owner][spender]` to `value`”. The EIP adds: “The caller of the `permit` function can be any address.” - Once submitted, the spender can use `transferFrom` like any approval. ## What it does not do - It cannot be submitted after `deadline`: the current block time must be “less than or equal to `deadline`.” - Each permit uses your current nonce for that token and increases it by 1, so it cannot be used twice. - It only works on tokens that implement EIP-2612. ## How long it lasts - There are two clocks. The `deadline` limits when the signature can be submitted. The allowance it creates has no expiry, like any ERC-20 allowance. ## How to undo it - Before it is submitted: EIP-2612 defines no cancel function. Its security notes say that if the signer submits a permit themselves, that “can render previously signed Permits invalid”, because the nonce moves on. - After it is submitted: `approve(spender, 0)`, then check with Revoke.cash or Etherscan’s token approval checker. ## A pattern to recognise - A no-gas “sign to continue” step can still create an allowance. Look for `Permit` in the primary type and read the spender and value. ## Practice question (fictional) Fictional Orchard asks you to sign a message so you can skip an approval transaction. | Field | Value | | --- | --- | | Request type | Signature: eth_signTypedData_v4 | | Primary type | Permit | | Token | LEAF (fictional) | | Spender | Orchard Vault (fictional contract) | | Value | 1,000,000 LEAF | | Deadline | 30 minutes from now | **Question:** If Orchard submits this within 30 minutes, does the allowance end when the 30 minutes are up? **Answer:** No. The deadline only limits when the signature can be submitted. Once submitted, the 1,000,000 LEAF allowance has no expiry until it is used up or set to 0. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [ERC-2612: Permit Extension for EIP-20 Signed Approvals](https://ercs.ethereum.org/ERCS/erc-2612). Ethereum ERCs. Final; created 2020-04-13. Checked 2026-11-04. - [EIP-712: Typed structured data hashing and signing](https://eips.ethereum.org/EIPS/eip-712). Ethereum EIPs. Final; created 2017-09-12. Checked 2026-11-04. - [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04. --- # Permit2 approvals and signatures > A 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. - Request: `approve(Permit2) then PermitSingle, PermitBatch or PermitTransferFrom signatures` - Standard: Uniswap Permit2 contract - 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/permit2 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 - Step 1 is an ordinary ERC-20 `approve` to the Permit2 contract. Uniswap’s docs note it is “commonly for the maximum `uint256` amount”. - Step 2 is a signature. For `PermitSingle` or `PermitBatch`, read each token’s `amount` and `expiration`, the `spender`, and `sigDeadline`. For `PermitTransferFrom`, read the token, the amount and `deadline`. ## What it lets the other party do - AllowanceTransfer: Uniswap describes it as “a standing, time-bound allowance inside the Permit2 contract”. The spender can transfer up to `amount` until “the allowance is exhausted or expires.” - SignatureTransfer: “a single, nonce-scoped transfer through one signature”, which “leaves no standing allowance.” - `PermitBatch` covers several tokens in one signature. ## What it does not do - A Permit2 allowance does not outlive its `expiration`. - Permit2 can only move tokens you have approved the Permit2 contract for. ## How long it lasts - Three different limits: the ERC-20 approval to Permit2 has no expiry; `sigDeadline` limits when a signature can be submitted; `expiration` is when the allowance stops working. - In Permit2’s source, an expiration of 0 means the allowance “only lasts the duration of the block.” ## How to undo it - Permit2’s `approve(token, spender, 0, 0)` or its `lockdown` function, which the source describes as “batch revoking approvals”, sets allowances to 0. - `invalidateNonces` cancels unused allowance signatures; `invalidateUnorderedNonces` does the same for one-time transfer signatures. - Setting the underlying ERC-20 approval to Permit2 to 0 stops all Permit2 spending of that token. Revoke.cash or Etherscan’s token approval checker can show both layers. ## A pattern to recognise - One `PermitBatch` signature can list many tokens. Read every entry, not just the first, and check each expiration. ## Practice question (fictional) Fictional Lanternfly Swap asks for a Permit2 signature. | Field | Value | | --- | --- | | Request type | Signature: PermitSingle | | Token | MOSS (fictional) | | Amount | 500 MOSS | | Expiration | 30 days from now | | Spender | Lanternfly Router (fictional contract) | | sigDeadline | 30 minutes from now | **Question:** If the router does not submit this signature within 30 minutes, can it still use it next week? **Answer:** No. `sigDeadline` is the last moment the signature can be submitted. The 30-day expiration only matters if the signature was submitted in time. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [Permit2 overview](https://developers.uniswap.org/docs/protocols/permit2/overview). Uniswap developer docs. Page as published on the check date. Checked 2026-11-04. - [Permit2 source: IAllowanceTransfer, ISignatureTransfer, Allowance library](https://github.com/Uniswap/permit2). Uniswap/permit2 on GitHub. main branch on the check date. Checked 2026-11-04. - [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04. --- # 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. - Request: `eth_signTypedData_v4` - Standard: EIP-712 - 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/sign-typed-data 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 - The domain: `name`, `chainId` and especially `verifyingContract`. EIP-712: “the address of the contract that will verify the signature.” - The primary type, such as `Permit` or an order, and every amount, recipient, deadline and nonce in the message. - MetaMask’s docs say “the top-level struct type’s name and the `domain.name` are presented to the user prominently in the confirmation.” Both are chosen by whoever built the request. ## What it lets the other party do - It produces a signature that a contract or server can verify. Depending on the primary type it can be a token permit, a marketplace order, a vote or a login. - Whoever holds the signature can try to use it. EIP-712 warns that an attacker can intercept a signature “and submits it to the contract before the original intended use takes place.” ## What it does not do - Signing is not itself an on-chain transaction and costs no gas. - EIP-712 does not prevent replays on its own: “It does not include replay protection.” That is left to each application. ## How long it lasts - There is no general rule. Look for deadline, expiry and nonce fields in the message. If there are none, ask how the receiving contract limits it. ## How to undo it - There is no universal cancel. Some protocols provide a cancel or nonce function. If the signature has already created an allowance, remove it like any allowance and check with Revoke.cash or Etherscan’s token approval checker. ## A pattern to recognise - A familiar name in the domain with an unfamiliar verifying contract. The name is free text; the verifying contract is what checks the signature. ## Practice question (fictional) Fictional Kiteframe Market asks you to sign a listing. | Field | Value | | --- | --- | | Request type | Signature: eth_signTypedData_v4 | | Domain name | Kiteframe Market | | Primary type | Order | | You offer | 1 Paper Heron (fictional NFT) | | You receive | 0.0001 fictional ETH | **Question:** Because signing costs no gas, is it impossible for this signature to move your heron? **Answer:** No. A signed order is meant to be submitted to a marketplace contract, which can then transfer the heron on the stated terms. No gas at signing time says nothing about what happens when someone submits it. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [EIP-712: Typed structured data hashing and signing](https://eips.ethereum.org/EIPS/eip-712). Ethereum EIPs. Final; created 2017-09-12. Checked 2026-11-04. - [Sign data (eth_signTypedData_v4 and personal_sign)](https://docs.metamask.io/metamask-connect/evm/guides/sign-data/). MetaMask developer docs. Page as published on the check date. Checked 2026-11-04. - [ERC-191: Signed Data Standard](https://ercs.ethereum.org/ERCS/erc-191). Ethereum ERCs. Final; created 2016-01-20. Checked 2026-11-04. --- # 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. - Request: `personal_sign` - Standard: ERC-191 version 0x45; often ERC-4361 sign-in - 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/personal-sign 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 - The full message text. - For Sign-In with Ethereum: the domain, the statement, the nonce and any expiration time. ## What it lets the other party do - It proves to whoever receives it that your account signed this exact text. MetaMask’s docs say it is “often used for signature challenges that are authenticated on a web server, such as Sign-In with Ethereum.” - A service or contract can choose to treat the signature as permission for something. What the message says matters. ## What it does not do - ERC-191 explains that the `0x19` prefix means “any EIP-191 `signed_data` can never be an Ethereum transaction.” - It does not create an on-chain allowance by itself. ## How long it lasts - Whatever the receiving service decides. ERC-4361 sign-in messages can include an `Expiration Time`, “the time when the signed authentication message is no longer valid.” ## How to undo it - There is nothing on-chain to undo. For a sign-in, log out of the service. ## A pattern to recognise - Readable is not the same as harmless: read what the text says you agree to. No legitimate signature request needs your recovery phrase. ## Practice question (fictional) Fictional Pebble Pass asks you to sign in. | Field | Value | | --- | --- | | Request type | Signature: personal_sign | | Message | pebblepass.example wants you to sign in with your Ethereum account. Nonce: 8f2k1. Expiration Time: in 10 minutes. | **Question:** Could this exact signature be broadcast as a transaction that sends your tokens? **Answer:** No. personal_sign adds the “\x19Ethereum Signed Message” prefix, and ERC-191 notes that such signed data can never be an Ethereum transaction. It can still be used by the service that asked for it, as a login. ## Sources - [ERC-191: Signed Data Standard](https://ercs.ethereum.org/ERCS/erc-191). Ethereum ERCs. Final; created 2016-01-20. Checked 2026-11-04. - [ERC-4361: Sign-In with Ethereum](https://ercs.ethereum.org/ERCS/erc-4361). Ethereum ERCs. Final; created 2021-10-11. Checked 2026-11-04. - [Sign data (eth_signTypedData_v4 and personal_sign)](https://docs.metamask.io/metamask-connect/evm/guides/sign-data/). MetaMask developer docs. Page as published on the check date. Checked 2026-11-04. --- # 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. - Request: `eth_sign` - Standard: Legacy JSON-RPC method; discontinued in MetaMask (MIP-3) - 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/eth-sign 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 - A hex string with no readable meaning. That is the warning sign: the prompt cannot show you what the hash represents. ## What it lets the other party do - MetaMask’s MIP-3: `eth_sign` “allows blind signing of arbitrary data without the `\x19Ethereum Signed Message` prefix” and “can be used to sign arbitrary hashes, making it possible for attackers to trick users into signing malicious transactions or messages.” ## What it does not do - It does not tell you what you are approving. Nothing in the prompt describes the action. ## How long it lasts - Nothing in a raw hash signature sets an expiry. How long it can be used depends on what the hash stands for, which the prompt does not tell you. ## How to undo it - There is no cancel. If you signed one, treat the account as you would after any unknown signature and check approvals with Revoke.cash or Etherscan’s token approval checker. ## Where it stands - MetaMask disabled `eth_sign` by default (MIP-3: “As of last year, `eth_sign` was disabled by default”) and MIP-3, created 2024-05-15 and accepted, proposes discontinuing support entirely. MetaMask’s developer docs list it as deprecated. Other wallets may differ. ## Practice question (fictional) A fictional site asks you to turn on an advanced wallet setting so you can sign a “login code”. | Field | Value | | --- | --- | | Request type | Signature: eth_sign | | Data | 0x7c1e…a94f (32 bytes of hex) | | Site says | Login code | **Question:** Can you tell from this prompt what the signature will authorize? **Answer:** No. eth_sign signs a raw hash. The hash could stand for a transaction or anything else, and the prompt cannot show which. The site’s label is not part of what you sign. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [MIP-3: Discontinuing the eth_sign signature method](https://github.com/MetaMask/metamask-improvement-proposals/blob/main/MIPs/mip-3.md). MetaMask Improvement Proposals. Accepted; created 2024-05-15. Checked 2026-11-04. - [Sign data (eth_signTypedData_v4 and personal_sign)](https://docs.metamask.io/metamask-connect/evm/guides/sign-data/). MetaMask developer docs. Page as published on the check date. Checked 2026-11-04. - [ERC-191: Signed Data Standard](https://ercs.ethereum.org/ERCS/erc-191). Ethereum ERCs. Final; created 2016-01-20. Checked 2026-11-04. --- # 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. - Request: `Authorization tuple [chain_id, address, nonce] in a set code transaction` - Standard: EIP-7702 - 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/eip-7702-authorization 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 - The `address` you are delegating to. - The `chain_id`. EIP-7702 accepts “0 or the ID of the current chain”, so 0 means any chain. - Which wallet is asking. The EIP expects wallets, not websites, to initiate this. ## What it lets the other party do - Once processed, your account’s code is set to a delegation indicator, and calls to your account load “the code at `address`” and execute it “in the context of `authority`”, which is your account. - EIP-7702: “The code specified by an authorization has unrestricted access to the account.” It also warns that a poorly built delegate can “allow a malicious actor to take near complete control over a signer’s EOA.” ## What it does not do - There is no permission system at this level. EIP-7702: “It is also not possible to implement a system of permissions at this level to minimize the risk.” ## How long it lasts - It persists until a new authorization replaces it. EIP-7702 also notes the delegation is “not rolled back” if the rest of the transaction fails. ## How to undo it - Sign a new authorization through your wallet. Delegating to the zero address clears the account’s code, per the EIP. It does not undo anything the delegated code already did. - To look at your real account, use an established external tool such as Revoke.cash. ## A pattern to recognise - A website asking you to sign an “account upgrade”. EIP-7702: “Applications must not expect that they can suggest the user sign an authorization, and therefore it is the duty of the wallet to not provide an interface to do so.” ## Practice question (fictional) A fictional site, Lanternfly Swap, asks you to sign an “upgrade” so swaps can be batched. | Field | Value | | --- | --- | | Request type | EIP-7702 authorization | | Delegate to | Lanternfly Batcher (fictional contract) | | chain_id | 0 | | Requested by | The website | **Question:** Does `chain_id` 0 limit this authorization to one network? **Answer:** No. EIP-7702 accepts a chain ID of 0 on any chain. It is also a website requesting an authorization, which the EIP says applications must not expect to do. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [EIP-7702: Set Code for EOAs](https://eips.ethereum.org/EIPS/eip-7702). Ethereum EIPs. Final; created 2024-05-07. Checked 2026-11-04. --- # 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. --- # 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. - Request: `eth_sendTransaction` - Standard: EIP-1474 (JSON-RPC) - 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/send-transaction 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`: ethereum.org explains that if it is an externally-owned account “the transaction will transfer value. If a contract account, the transaction will execute the contract code.” - `value`: the amount of ETH sent. - `data`: empty for a plain transfer. If it is not empty, it is a contract call. Read the decoded function name. - The network. ## What it lets the other party do - EIP-1474 describes the method as: “Creates, signs, and sends a new transaction to the network.” - With `data`, your account calls a contract function. That function can be `approve` or `setApprovalForAll`, so a “transaction” can be a permission. ## What it does not do - A plain value transfer does not create any allowance for later. - It is not reversible once settled. ethereum.org: once a block is finalized “it could only ever be changed by a network level attack that would cost many billions of dollars.” ## How long it lasts - A transfer is a single event. A contract call can leave lasting state, such as an allowance. ## How to undo it - A completed transfer has no undo. Setting an allowance to 0 does not bring back tokens that moved. - If the call was an approval, remove it as described on the approval pages, and check with Revoke.cash or Etherscan’s token approval checker. ## A pattern to recognise - A transaction with a value of 0 that looks like it “does nothing” but whose data is an approval. ethereum.org calls opaque data a “blind signing” problem. ## Practice question (fictional) Fictional Orchard asks you to confirm a transaction. | Field | Value | | --- | --- | | Request type | Transaction: eth_sendTransaction | | to | LEAF token contract (fictional) | | value | 0 ETH | | data (decoded) | approve(Orchard Router, maximum) | **Question:** Because the value is 0, does this transaction leave your tokens untouched in every way? **Answer:** No. Value is the ETH sent. The data is an `approve` call that gives Orchard Router an unlimited LEAF allowance. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [EIP-1474: Remote procedure call specification (eth_sendTransaction)](https://eips.ethereum.org/EIPS/eip-1474). Ethereum EIPs. Stagnant; created 2018-10-02. Checked 2026-11-04. - [Transactions (developer docs)](https://ethereum.org/developers/docs/transactions/). ethereum.org. Page as published on the check date. Checked 2026-11-04. - [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04. --- # A session key limited to 25 a day for 7 days > An 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. - Request: `Session account or spending-limit module` - Standard: Wallet-specific - Track: Agent permissions - Checked against sources: 2026-11-04 - Review status: drafted with AI assistance, awaiting human review - Canonical page: https://walletpermissions.com/learn/agents/session-key-daily-limit 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 - Which key or account receives the right. MetaMask describes a session account “created solely to request and redeem Advanced Permissions”. Safe{Wallet} says a spending-limit spender “can be anyone: a bot, a teammate, or an external wallet.” - The token, the amount per period, the period length, the start time and the end. ## What the limit covers - A ceiling per period, not per payment: the agent can make several payments that add up to the limit. - Over 7 days at 25 a day, the total can reach 175. - Resets can line up back to back. In the source of Safe{Wallet}’s spending-limit module, the spent amount resets at regular intervals, so the full amount can be used just before a reset and again just after it. - Safe{Wallet}: “Transfers inside the limit execute immediately, with no approval from other signers.” ## What it does not cover - Who gets paid. Safe{Wallet}’s help article on spending limits: “They do not restrict who the spender sends to.” MetaMask’s documented periodic permission parameters do not include a recipient either. - Whether a payment was worth it. The limit is a number, not a judgement about the agent’s choices. ## How to stop it - In Safe{Wallet}, “Only signers of the Safe account can change a spending limit”; the help article shows removing a spender or a token from the limit. - For an ERC-7715 permission, the standard defines `wallet_revokeExecutionPermission`. The screen for it depends on your wallet. ## Practice question (fictional) A fictional shopping agent asks for a session key. | Field | Value | | --- | --- | | Request | Session key for Shopkeep Agent (fictional) | | Token | DOLLR (fictional stablecoin) | | Limit | 25 DOLLR per day | | Duration | 7 days | | Recipient | Not specified | **Question:** Does this limit mean the agent can only pay the shop you had in mind? **Answer:** No. The limit caps how much moves per day. Unless the permission names a recipient, it does not say where the money goes. ## Sources - [Set up and use spending limits](https://help.safe.global/en/articles/40842-set-up-and-use-spending-limits). Safe{Wallet} Help Center. Page as published on the check date. Checked 2026-11-04. - [AllowanceModule.sol (Safe{Wallet} spending-limit module source)](https://github.com/safe-global/safe-modules/blob/main/modules/allowances/contracts/AllowanceModule.sol). safe-global/safe-modules on GitHub. main branch on the check date. 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. - [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. --- # 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. - Request: `approve(spender, maximum)` - Standard: ERC-20 - Track: Agent permissions - Checked against sources: 2026-11-04 - Review status: drafted with AI assistance, awaiting human review - Canonical page: https://walletpermissions.com/learn/agents/unlimited-approval-to-save-gas 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 - The amount. A maximum approval removes the ceiling. A specific number keeps one. - The spender. The approval is for that address, whatever app or agent is talking to you. ## What the limit covers - ethereum.org explains why projects ask for unlimited allowances: “to minimize the number of requests required, meaning the user only has to approve once and pay the transaction fee only once.” - A bounded approval of the amount you plan to spend gives the same spender the same ability, up to that amount. ## What it does not cover - Time. ERC-20 approvals have no expiry, so the unlimited allowance stays until you set it to 0. - Your other plans. The spender can use the allowance for later transfers you did not have in mind, as long as it remains. - If you want a time limit, look for systems that have one, such as Permit2’s `expiration` or an ERC-7715 permission with an `expiry` rule. ## How to stop it - Send `approve(spender, 0)`. Check your real approvals with Revoke.cash or Etherscan’s token approval checker. ## Practice question (fictional) A fictional trading agent shows you two options. | Field | Value | | --- | --- | | Option A | approve(Tidepool Router, 50 DOLLR) | | Option B | approve(Tidepool Router, maximum) “to save gas on future trades” | | Your plan | Spend 50 DOLLR this week | **Question:** If you choose option B, can Tidepool Router move more than the 50 DOLLR you planned to spend? **Answer:** Yes. Option B has no ceiling and no expiry. The router can transfer any amount of your DOLLR until you set the allowance to 0. Option A stops at 50. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [How to revoke smart contract access to your crypto funds](https://ethereum.org/guides/how-to-revoke-token-access). ethereum.org. Page as published on the check date. Checked 2026-11-04. - [ERC-20: Token Standard](https://ercs.ethereum.org/ERCS/erc-20). Ethereum ERCs. Final; created 2015-11-19. Checked 2026-11-04. - [Permit2 overview](https://developers.uniswap.org/docs/protocols/permit2/overview). Uniswap developer docs. Page as published on the check date. Checked 2026-11-04. - [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. --- # An ERC-7715 grant with a spend limit and expiry > An 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. - Request: `wallet_requestExecutionPermissions` - Standard: ERC-7715 (Draft) - Track: Agent permissions - Checked against sources: 2026-11-04 - Review status: drafted with AI assistance, awaiting human review - Canonical page: https://walletpermissions.com/learn/agents/erc-7715-spend-limit-expiry 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 - `to`: the session account that will act. ERC-7715 calls it “the DApp session account associated with the permission”. - `permission.type` and its data. For MetaMask’s `erc20-token-periodic`: `tokenAddress`, `periodAmount`, `periodDuration`, `startTime`, `justification`. - `rules`: ERC-7715’s `expiry` rule makes a permission “only valid until a specified timestamp.” - `isAdjustmentAllowed`: whether the wallet “MAY attenuate(reduce or increase)” the permission. ## What the limit covers - An amount per period that resets each period, until the expiry. - The `justification` is text written by the requester. It explains; it does not restrict. ## What it does not cover - A recipient. The documented periodic permission parameters do not name one. - A promise that the grant matches the request: “it is not guaranteed that the values received are equivalent to those requested.” Read what your wallet shows you are granting. ## How to stop it - ERC-7715 defines `wallet_revokeExecutionPermission`. The standard is a Draft and wallet screens differ, so look for granted permissions in your wallet’s settings. ## Practice question (fictional) A fictional research agent asks your wallet for a permission. | Field | Value | | --- | --- | | to | Fieldnotes Agent session account (fictional) | | permission.type | erc20-token-periodic | | Token | DOLLR (fictional) | | periodAmount | 10 DOLLR | | periodDuration | 86400 seconds (1 day) | | rules | expiry in 14 days | | justification | “Pay for research APIs” | **Question:** Does this permission restrict the agent to paying research APIs? **Answer:** No. The justification is the requester’s description. The documented parameters limit the token, the amount per day and the time window; none names who can be paid. ## 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. - [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. - [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. --- # An x402 pay-per-request payment vs a standing allowance > An 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. - Request: `x402 PAYMENT-SIGNATURE (exact scheme on EVM)` - Standard: x402 protocol v2; ERC-3009 - Track: Agent permissions - Checked against sources: 2026-11-04 - Review status: drafted with AI assistance, awaiting human review - Canonical page: https://walletpermissions.com/learn/agents/x402-payment-vs-allowance 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 - x402 flow: a server answers with a payment required signal, and the client “submits a signed payment authorization in the subsequent request.” - In the `exact` scheme with ERC-3009, the authorization names `from`, `to`, `value`, `validAfter`, `validBefore` and a unique `nonce`. - The asset transfer method. The `exact` scheme lists ERC-3009, Permit2 and ERC-7710. ## What the limit covers - For ERC-3009 and Permit2 in the `exact` scheme, the spec lists the usage as “One-time use”, and says “the Facilitator cannot modify the amount or destination.” - The `upto` scheme is different: the client “authorizes a maximum amount”, and the server settles “for the actual amount used”, up to that maximum. ## What it does not cover - The Permit2 method needs a one-time ERC-20 approval of the Permit2 contract first. That approval is a standing allowance, separate from each payment. - The ERC-7710 method in the `exact` scheme is listed as “One-time use and multi-use”. Read which one you are granting. - Whether the response was worth paying for. The signature pays; it does not judge the result. ## How to stop it - An unused one-time authorization stops working after `validBefore`. - A standing allowance, including an approval of Permit2, stays until you set it to 0. Check with Revoke.cash or Etherscan’s token approval checker. ## Practice question (fictional) Your fictional research agent pays a fictional API 0.01 DOLLR for one answer, using x402’s `exact` scheme with ERC-3009. | Field | Value | | --- | --- | | Scheme | exact (EVM, eip3009) | | to | Datawell API payee (fictional) | | value | 0.01 DOLLR | | validBefore | 60 seconds from now | | nonce | unique | **Question:** Can Datawell use this same signature to charge another 0.01 DOLLR tomorrow? **Answer:** No. The authorization is for one transfer, with a unique nonce and a short validity window. A second charge needs a new signature. A standing allowance would not need one. ## Check your real account elsewhere This site never connects to a wallet or asks for an address. Established tools (independent, not endorsements): - [Revoke.cash](https://revoke.cash/): shows and removes token approvals across many networks - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker): shows and removes token approvals on Ethereum mainnet ## Sources - [x402 protocol specification, version 2](https://github.com/x402-foundation/x402/blob/main/specs/x402-specification-v2.md). x402 on GitHub. Protocol version 2; main branch on the check date. Checked 2026-11-04. - [x402 scheme: exact on EVM](https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_evm.md). x402 on GitHub. Last changed 2026-10-15. Checked 2026-11-04. - [x402 scheme: upto on EVM](https://github.com/x402-foundation/x402/blob/main/specs/schemes/upto/scheme_upto_evm.md). x402 on GitHub. main branch on the check date. Checked 2026-11-04. - [ERC-3009: Transfer With Authorization](https://ercs.ethereum.org/ERCS/erc-3009). Ethereum ERCs. Draft; created 2020-09-28. Checked 2026-11-04. --- # cow.fi domain hijack: a familiar address, unfamiliar requests > For about 4.5 hours on 14 April 2026, attackers controlled the cow.fi domain and served a phishing site. Visitors who signed its requests lost tokens. The lesson: the address bar can be right while the request is wrong. - Date: 2026-04-14 - Protocol: CoW Swap (cow.fi) - Checked: 2026-11-04 - Review status: drafted with AI assistance, awaiting human review - Canonical page: https://walletpermissions.com/incidents/cow-swap-domain-hijack-2026-04 ## What the official source says - Date: 14 April 2026 (CoW DAO, CIP-86, posted 23 April 2026) - What was compromised: The domain registrar used by CoW Swap’s DNS holder, through social engineering. CoW DAO states CoW Swap itself “was not hacked”. - Duration: “approximately 4.5 hours” of attacker control of the domain - What users did: A phishing site “tricked cow.fi visitors into signing malicious transactions that drained tokens from their wallets”. Claim criteria refer to signing “a malicious message or transaction”. - Estimated loss: “approximately 1.2M USDC worth of user funds” (core team estimate in CIP-86) ## Which kind of permission CoW DAO’s forum post says victims signed malicious transactions or messages; it does not say which request types. Both kinds can move tokens: a transaction can carry an approval or transfer, and a signed message can be a permit or an order. These explainers cover the possibilities: - [Send a transaction (eth_sendTransaction)](https://walletpermissions.com/learn/requests/send-transaction.md) - [Token approval (ERC-20 approve)](https://walletpermissions.com/learn/requests/approve.md) - [Permit signature (EIP-2612)](https://walletpermissions.com/learn/requests/permit.md) - [Typed-data signature (eth_signTypedData_v4)](https://walletpermissions.com/learn/requests/sign-typed-data.md) ## What it let the attacker do - Because the domain was the real one, the usual “check the URL” advice did not help during those hours. - Whatever a visitor signed went to the attacker’s contract, not to CoW Swap. - Signed approvals or permits could keep working after the domain was recovered, until revoked. ## A fictional replica of the prompt A fictional replica, not the real prompt. It shows the kind of request a hijacked front end can show. - Site in address bar: swap.example (the real, familiar domain) - Request type: Signature: eth_signTypedData_v4 - Primary type: Permit - Spender: An address you have not seen before - Value: Maximum If the spender in a prompt does not match what you expected from the app, the domain alone does not settle it. ## What to do now - Follow the project’s official post first. - Check approvals your real account gave around that time with Revoke.cash or Etherscan’s token approval checker. - CoW DAO’s claim window for its grants program closed on 14 May 2026, per CIP-86. - Official post: [CoW DAO forum: CIP-86](https://forum.cow.fi/t/cip-86-discretionary-grants-program-for-victims-of-the-cow-fi-domain-hijacking/3431) - [Revoke.cash](https://revoke.cash/) - [Etherscan token approval checker](https://etherscan.io/tokenapprovalchecker) ## Sources - [CIP-86: Discretionary grants program for victims of the cow.fi domain hijacking](https://forum.cow.fi/t/cip-86-discretionary-grants-program-for-victims-of-the-cow-fi-domain-hijacking/3431). CoW DAO forum (official governance forum). Posted 2026-04-23. Checked 2026-11-04.