Core concepts
Wallet Guides should be understood in the context of the exact network, account and on-chain action involved, rather than as an isolated screen or feature.
A reliable workflow separates identity, network and intent. First identify what account is acting, then confirm where the action will execute, and finally inspect what state change is being requested. This sequence reduces errors caused by familiar-looking interfaces.
Why context matters
When an interface uses a short label such as “Send”, “Approve” or “Connect”, do not treat the label as a complete explanation. The underlying transaction or signature contains the actual destination, amount, contract method and permissions.
How to review the action
Before acting, verify the relevant identifiers for wallet guides: network, address, contract, request type or validator state as applicable.
If information is unclear, stop before signing. Re-open the request from a trusted entry point, compare the network and contract details, and look for independent on-chain evidence. A slower review is often safer than trying to reverse an action later.
imtoken will never ask for your seed phrase, private key or verification code.
Common risks and mistakes
Use the transaction hash, block explorer data, approval records or protocol state to confirm outcomes instead of relying only on a local interface.
Third-party DApps, smart contracts and network services can introduce technical or operational risk. No wallet interface can guarantee the safety of an external contract or recover a private key for the user.
Keep a record of transaction hashes for important actions. They provide a durable way to check whether a transaction was pending, successful or reverted and help separate display problems from actual on-chain results.
A repeatable checklist
- Confirm the exact network before signing or sending.
- Check the full address, contract or validator identifier relevant to the action.
- Review amounts, permissions, gas and request details before approval.
- Never provide a seed phrase, private key or verification code to a website or support agent.
- After the action, verify the resulting on-chain state using reliable public data.
Related learning path
Continue with the related guides below, and treat every new network or DApp as a fresh verification task.