Service & help
Wallet Guides
Wallet guides are most useful when organized around tasks such as setup, backup, receiving, sending, history review, and recovery, because each task has different prerequisites.
Scope and how to use it
Wallet guides are most useful when organized around tasks such as setup, backup, receiving, sending, history review, and recovery, because each task has different prerequisites. When working with Wallet Guides, separate what the interface displays from facts that can be verified on-chain. A wallet can organize information and prepare requests, but the network, address, contract, and final transaction state still need independent context. If a critical field cannot be explained, stop before confirming and verify it again instead of responding to urgency from a page, an unknown contact, or short-term market movement.
Learning why a step exists is as important as learning where to click; that knowledge remains useful when an interface changes. In a real workflow, Wallet Guides should not be reduced to a single click or one status message. Review the network, account, requested action, amount, and permission scope as separate checkpoints so inconsistencies become visible earlier. If a critical field cannot be explained, stop before confirming and verify it again instead of responding to urgency from a page, an unknown contact, or short-term market movement.
- Confirm that the network, address, or contract involved in Wallet Guides matches the intended context
- Use public information for verification and never submit a seed phrase, private key, or verification code
- Treat signatures, approvals, transfers, and contract calls as separate decisions rather than permanent trust
Identify the object first, then the action, then the expected result.
Questions users commonly face
Learning why a step exists is as important as learning where to click; that knowledge remains useful when an interface changes. In a real workflow, Wallet Guides should not be reduced to a single click or one status message. Review the network, account, requested action, amount, and permission scope as separate checkpoints so inconsistencies become visible earlier. If a critical field cannot be explained, stop before confirming and verify it again instead of responding to urgency from a page, an unknown contact, or short-term market movement.
Security guidance belongs inside each workflow rather than as an afterthought, especially for backups, transfers, and DApp interactions. Risk often hides inside familiar-looking details. Similar names, addresses, domains, and repeated confirmation dialogs can make a request feel routine even when the underlying target or authority is different. If a critical field cannot be explained, stop before confirming and verify it again instead of responding to urgency from a page, an unknown contact, or short-term market movement.
- Confirm that the network, address, or contract involved in Wallet Guides matches the intended context
- Use public information for verification and never submit a seed phrase, private key, or verification code
- Treat signatures, approvals, transfers, and contract calls as separate decisions rather than permanent trust
Before transferring, verify address, network, and amount; before signing, read the request.
Verification and risk boundaries
Security guidance belongs inside each workflow rather than as an afterthought, especially for backups, transfers, and DApp interactions. Risk often hides inside familiar-looking details. Similar names, addresses, domains, and repeated confirmation dialogs can make a request feel routine even when the underlying target or authority is different. If a critical field cannot be explained, stop before confirming and verify it again instead of responding to urgency from a page, an unknown contact, or short-term market movement.
Wallet guides are most useful when organized around tasks such as setup, backup, receiving, sending, history review, and recovery, because each task has different prerequisites. After a Wallet Guides action, review the final state and retain non-secret reference information such as the transaction hash, network name, or contract address when relevant so later verification is possible. If a critical field cannot be explained, stop before confirming and verify it again instead of responding to urgency from a page, an unknown contact, or short-term market movement.
- Confirm that the network, address, or contract involved in Wallet Guides matches the intended context
- Use public information for verification and never submit a seed phrase, private key, or verification code
- Treat signatures, approvals, transfers, and contract calls as separate decisions rather than permanent trust
Third-party DApps and smart contracts can introduce risk, so stop and re-check unfamiliar requests.
Useful next steps
Wallet guides are most useful when organized around tasks such as setup, backup, receiving, sending, history review, and recovery, because each task has different prerequisites. After a Wallet Guides action, review the final state and retain non-secret reference information such as the transaction hash, network name, or contract address when relevant so later verification is possible. If a critical field cannot be explained, stop before confirming and verify it again instead of responding to urgency from a page, an unknown contact, or short-term market movement.
Learning why a step exists is as important as learning where to click; that knowledge remains useful when an interface changes. When working with Wallet Guides, separate what the interface displays from facts that can be verified on-chain. A wallet can organize information and prepare requests, but the network, address, contract, and final transaction state still need independent context. If a critical field cannot be explained, stop before confirming and verify it again instead of responding to urgency from a page, an unknown contact, or short-term market movement.
- Confirm that the network, address, or contract involved in Wallet Guides matches the intended context
- Use public information for verification and never submit a seed phrase, private key, or verification code
- Treat signatures, approvals, transfers, and contract calls as separate decisions rather than permanent trust
Keep public references such as transaction hashes and review connections or approvals that are no longer needed.
imtoken
Keep the network, request, and expected result visible
Review the details before transferring, signing, approving, or interacting with a contract.