Start with who can authorize a transfer
A crypto wallet is a tool for viewing accounts and authorizing actions on a network. In conventional self-custody, you control the signing keys; in a custodial account, a provider signs and maintains your account balance. An address is intended for receiving funds. A private key or recovery phrase is secret signing material. A password for an exchange account is a different kind of credential.
Before choosing a product, complete four sentences: who can sign, who can block a withdrawal, who can restore access, and what happens if that party disappears. Product labels such as hot, cold or decentralized do not answer all four. A smart-contract wallet may use multiple signers or recovery rules instead of one conventional seed.
1. Verify the software and device before setup
Open the maker’s official website independently and follow its download or app-store links. Compare the publisher and supported device model. A sponsored search result, QR code in an unsolicited message or familiar-looking icon is not verification. Follow the manufacturer’s authenticity and firmware checks; packaging alone cannot establish that a device is genuine.
A request to use a recovery phrase already printed in a new device’s box is a reason to stop and verify the setup with the manufacturer. Record the official support address separately. Support can explain a procedure without learning the secret that controls your assets.
2. Separate the recovery plan from the device password
For a seed-based wallet, losing the phone or hardware device need not destroy the on-chain balance, but restoring access requires the correct backup and any additional recovery requirements. A device PIN is not a substitute for that backup. Conversely, someone with the recovery material may not need the original device or its PIN.
Write a recovery plan describing the wallet model, network, backup type and where the official instructions can be found. Keep the secrets themselves out of shared notes, photos, email, cloud documents and support chats. Protect backups against both unauthorized reading and physical loss. Multiple copies can improve availability while creating additional places that need protection.
3. Check recovery without wiping the working wallet
Use the maker’s documented backup-check function where available. For example, Trezor documents a Check backup process for Model T that compares the entered backup with the device’s wallet and reports whether they match. That is a model-specific example, not a universal sequence for every wallet. Follow the instructions for your actual model and backup format.
Do not erase a working device merely to see whether your notes work. Do not type a real recovery phrase into an online checker. For a learning exercise, use an empty test wallet and record which steps are performed on the device and which in the official app. This guide describes a workflow; it does not certify or claim hands-on testing of a device.
4. Read what the next signature permits
For a transfer, compare the network, asset, full destination, amount and fee with the intended action. Where a trusted device display is available, use it to verify the transaction. For a contract interaction, also identify the spender and permission being granted. If the interface cannot explain the action sufficiently, stop before signing.
Connecting a wallet, signing a message and granting a token allowance are different actions. MetaMask’s documentation explains that disconnecting an application does not revoke an existing token approval. An allowance can remain on-chain after a browser tab is closed. Review permissions through the wallet’s official instructions and verify the network before any revocation; a revocation can require a network fee.
In a conventional self-custody setup, the wallet signs locally and sends the signed transaction. Keep recovery material private; a custody provider signs on its own systems.
AI-generated visual metaphor, not a wallet demonstration: a signing request enters the wallet and a signature leaves it. The private key stays inside. No real keys or transactions are shown.
A custody comparison you can complete
For a fictional exchange account, your worksheet might say: provider signs; provider can suspend withdrawals; account recovery goes through support; provider failure may obstruct access. For a conventional hardware wallet: owner signs; recovery uses the owner’s backup; losing both the device and recovery material can mean losing access. Add any multisignature participants or recovery contacts rather than forcing every product into these two examples.
Finish with three failure scenarios: a broken device, a lost account login, and an exposed recovery secret. The response differs in each case. Revoking one application’s allowance does not repair a compromised private key. Use the wallet maker’s verified incident guidance for the actual setup; do not disclose secrets to someone offering guaranteed recovery.
Sources & further reading
- Ethereum: wallets, accounts, keys and addresses
- Ethereum: security and scam prevention
- Trezor: check a Model T wallet backup
- MetaMask: token approvals and revocation
Educational content. Examples are illustrative. Protocols, products and rules can change; consult the linked documentation for current details.