Read a wallet request by the authority it grants
A wallet can show a password prompt, a connection request, a message to sign or a transaction. They do not grant the same powers. Use a fictional token allowance to connect private keys, recovery phrases, self-custody and hardware wallets to the permissions a phishing page may try to obtain.
Know which secret you are protecting
A private key authorizes actions for the accounts or spending conditions it controls. A seed phrase is a human-readable backup used by many wallets to derive a seed and recover a collection of keys. It is not an ordinary website password. Someone who obtains the necessary recovery information may recreate the wallet elsewhere without possessing your phone.
BIP-39 specifies one widely used phrase format, but wallet recovery is not universal. Some wallets use different formats or additional recovery information, such as a separate passphrase. Follow the instructions for the actual wallet. Do not invent a memorable sentence, translate backup words or enter recovery information into a site that claims to validate it. This lesson never needs your keys or backup.
A hardware wallet changes where signing happens
In self-custody, responsibility includes protecting recovery material and understanding what you authorize. A hardware wallet is designed to keep signing keys isolated while presenting a way to approve operations. It reduces exposure of those keys to a connected computer, but does not turn every operation you approve into a safe one.
A malicious request can still ask you to authorize a harmful transfer or permission. Compare the intended recipient, network, asset and action with the trusted device display and relevant documentation. If the meaning cannot be established, stop rather than relying on the device brand or a site's professional appearance.
Connection and spending permission are separate
For a standard ERC-20 token, an approval sets an allowance for a particular spender. The spender can use the token's transferFrom mechanism subject to that allowance and the contract's rules. The approval identifies a token and spender; it does not mean every app receives the same permission.
Disconnecting a website from the wallet interface does not cancel an existing onchain allowance. Revoking or reducing that allowance requires the relevant onchain change to take effect. Revocation also does not repair an exposed seed phrase: if signing authority is compromised, removing one permission leaves a different problem unresolved.
Phishing often blurs these distinctions. A page may describe a request as verification while asking for recovery words, a broad allowance or a signature with wider consequences. Read the actual authorization. A claim that signing is free says nothing about what that signature can permit.
A 40-token allowance is not a 40-token balance
An imaginary account holds 100 units of a standard token and approves a spender for 40. If the spender transfers 15 under an ordinary allowance implementation, the account has 85 units and the remaining allowance is 25. Closing the app or disconnecting the website changes neither number. This is an accounting illustration, not a claim about any particular token contract.
| State | Token balance | Remaining allowance |
|---|---|---|
| After approval | 100 | 40 |
| After a 15-unit transferFrom | 85 | 25 |
| After a completed revocation to zero | 85 | 0 |
Check your understanding
Does revoking an allowance protect an account whose recovery phrase was leaked?
No. Allowance management and compromised signing authority are different problems. Revocation removes that spender's permission once effective; it does not remove an attacker's ability to use exposed recovery information. Do not provide recovery information to anyone offering to fix the problem.
Check the primary sources
These references explain the rules behind the lesson. The examples above are fictional teaching scenarios written for this dictionary.