imtoken
Support
Find self-service troubleshooting paths and clear security boundaries without ever submitting a seed phrase, private key or verification code.
Find self-service troubleshooting paths and clear security boundaries without ever submitting a seed phrase, private key or verification code.
Start troubleshooting
Start troubleshooting is a practical part of understanding Support. Find self-service troubleshooting paths and clear security boundaries without ever submitting a seed phrase, private key or verification code. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.
imtoken guidance focuses on information you can verify. When something is unclear, do not rely on a single line in a pop-up. Check the address, network, contract, transaction history and explorer data where relevant, then decide whether the action matches your intent.
For Start troubleshooting, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.
Practical checks
- Verify the network and account before working with start troubleshooting
- Double-check important addresses, contracts, amounts or permissions
- Never send a seed phrase, private key or verification code to anyone
Transaction issues
Transaction issues is a practical part of understanding Support. Find self-service troubleshooting paths and clear security boundaries without ever submitting a seed phrase, private key or verification code. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.
Transaction issues within Support is not an isolated feature. In practice it is shaped by network state, account permissions, transaction parameters and user decisions. Understanding those relationships first makes similar-looking screens and labels much less confusing.
For Transaction issues, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.
Practical checks
- Verify the network and account before working with transaction issues
- Double-check important addresses, contracts, amounts or permissions
- Never send a seed phrase, private key or verification code to anyone
DApp issues
DApp issues is a practical part of understanding Support. Find self-service troubleshooting paths and clear security boundaries without ever submitting a seed phrase, private key or verification code. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.
A useful way to think about DApp issues within Support is to separate what the interface displays from what the blockchain records. The wallet organizes information and submits requests, while the target network records the resulting state. Addresses, networks, contracts and transaction hashes are therefore important verification points.
For DApp issues, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.
Practical checks
- Verify the network and account before working with dapp issues
- Double-check important addresses, contracts, amounts or permissions
- Never send a seed phrase, private key or verification code to anyone
Security incidents
Security incidents is a practical part of understanding Support. Find self-service troubleshooting paths and clear security boundaries without ever submitting a seed phrase, private key or verification code. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.
The risky part of Security incidents within Support is often the surrounding context rather than the button itself: which network is active, which site initiated the request, what permission is being granted, and whether the amount and fee make sense. Turning those checks into a routine is more reliable than reacting to prompts one by one.
For Security incidents, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.
Practical checks
- Verify the network and account before working with security incidents
- Double-check important addresses, contracts, amounts or permissions
- Never send a seed phrase, private key or verification code to anyone
imtoken
Ready to get started?
The download entry always goes through the dedicated download page. Keep verifying networks, addresses and request details before acting.