Wallet signature requests: What can a dApp do?
What does a wallet signature request allow a dApp to do? A login proves ownership; a permit can set token allowance, so read spender, value and deadline.
Onchain Report Newsroom#8ff9373 min read
A wallet signature request lets a dApp prove you own an address or, with a token permit, authorize a spender to move tokens. Signatures are free and off-chain, but a contract that accepts a permit treats it as your approval.
The signed data determines what the dApp can do
A wallet signs data, then the receiving app or contract uses it according to its format. The signature itself sends no transaction. These three request types have different effects:
- Login message: A readable EIP-4361 message, also called Sign-In with Ethereum (SIWE), or a personal_sign request proves you control the address. It does not approve token spending or move funds.
- Typed-data permit: EIP-2612 lets an ERC-20 token accept an EIP-712 signature to set an allowance. The named spender can then move tokens within that allowance without another approval transaction.
- Blind hash: An eth_sign request or unreadable hex hides what you are signing. Do not sign it: it can authorize any transaction.
For a permit, read the spender, value, nonce and deadline. The spender is the address allowed to use the tokens; the value is the limit. A value equal to the maximum uint means unlimited allowance. The nonce is a one-use number, and the deadline sets when the permit expires. Permit2 is another system that uses signatures for token permissions, so read its typed-data fields too.
A permit can stay invisible until someone submits it
Say you are removing liquidity from Fraxswap. Fraxswap pair LP tokens support permit. The Fraxswap Router can use that signature to remove liquidity without a separate approval transaction.
The sequence matters: your wallet signs typed data, then the spender submits that signature to the token contract. The contract checks the signature and its nonce and deadline, then sets the allowance. Only after submission does the permit appear on-chain, where the spender can use the allowance to move tokens.
A signed permit leaves no on-chain trace until the spender submits it, so it will not appear in your transaction history while it is waiting. To cancel it before its deadline, a transaction must use or invalidate its nonce. That cancellation costs gas. Fraxswap’s permit flow shows why a signature can save an approval step while still granting a real token permission.
Related
Can a dApp take my tokens if I only connect my wallet?
Connecting alone does not authorize token transfers. A login signature proves address ownership; a permit or on-chain approval can grant a spender permission to move tokens.
How do I revoke a token approval I already gave?
Use a token approval manager or the token’s supported method to set the spender’s allowance to zero. Revoking an on-chain approval takes a gas-paying transaction. For a signed permit that has not been submitted, invalidate its nonce before the deadline. Before clicking Sign, confirm whether the request is a login or a permit, then check the spender, value and deadline.