Classify the issue first
When working through “Classify the issue first”, separate what the interface displays from what the blockchain records. A wallet can organize information, prepare a request and show the result, but the selected network ultimately determines transaction and contract state. For Support, confirm the network, account and destination rather than relying only on familiar buttons or visual cues.
A practical review sequence is source, target, permission and outcome. Identify where the request came from, what address or contract it affects, what authority it is asking for, and what may happen after approval. This turns a vague sense that a request “looks normal” into a set of facts that can be checked before acting.
If the interface does not match expectations, avoid immediately repeating the action. Check the selected network, whether a transaction hash exists, whether an explorer shows the record, and whether the token or contract address matches the intended asset. Confirmation can take time, especially when a network is congested.
Security boundaries remain important throughout Support. imtoken will never ask for a seed phrase, private key or verification code. Do not send those secrets to anyone or enter them into an unfamiliar website. Before a transfer, signature or approval, review the address, network, amount, spender and permission scope. Third-party DApps and smart contracts can introduce risks outside a wallet’s control.
Service decisions should account for changing network rewards, exit queues, validator penalties, smart-contract risk, third-party dependencies and digital-asset price volatility. No outcome should be treated as guaranteed.
Key point
A good support workflow first separates device-display issues, network status, transaction confirmation and third-party DApp behavior. imtoken support information should never ask for a seed phrase, private key or verification code.
Transaction troubleshooting
A practical review sequence is source, target, permission and outcome. Identify where the request came from, what address or contract it affects, what authority it is asking for, and what may happen after approval. This turns a vague sense that a request “looks normal” into a set of facts that can be checked before acting.
If the interface does not match expectations, avoid immediately repeating the action. Check the selected network, whether a transaction hash exists, whether an explorer shows the record, and whether the token or contract address matches the intended asset. Confirmation can take time, especially when a network is congested.
Security boundaries remain important throughout Support. imtoken will never ask for a seed phrase, private key or verification code. Do not send those secrets to anyone or enter them into an unfamiliar website. Before a transfer, signature or approval, review the address, network, amount, spender and permission scope. Third-party DApps and smart contracts can introduce risks outside a wallet’s control.
When working through “Transaction troubleshooting”, separate what the interface displays from what the blockchain records. A wallet can organize information, prepare a request and show the result, but the selected network ultimately determines transaction and contract state. For Support, confirm the network, account and destination rather than relying only on familiar buttons or visual cues.
Service decisions should account for changing network rewards, exit queues, validator penalties, smart-contract risk, third-party dependencies and digital-asset price volatility. No outcome should be treated as guaranteed.
Key point
A good support workflow first separates device-display issues, network status, transaction confirmation and third-party DApp behavior. imtoken support information should never ask for a seed phrase, private key or verification code.
DApp and approval questions
If the interface does not match expectations, avoid immediately repeating the action. Check the selected network, whether a transaction hash exists, whether an explorer shows the record, and whether the token or contract address matches the intended asset. Confirmation can take time, especially when a network is congested.
Security boundaries remain important throughout Support. imtoken will never ask for a seed phrase, private key or verification code. Do not send those secrets to anyone or enter them into an unfamiliar website. Before a transfer, signature or approval, review the address, network, amount, spender and permission scope. Third-party DApps and smart contracts can introduce risks outside a wallet’s control.
When working through “DApp and approval questions”, separate what the interface displays from what the blockchain records. A wallet can organize information, prepare a request and show the result, but the selected network ultimately determines transaction and contract state. For Support, confirm the network, account and destination rather than relying only on familiar buttons or visual cues.
A practical review sequence is source, target, permission and outcome. Identify where the request came from, what address or contract it affects, what authority it is asking for, and what may happen after approval. This turns a vague sense that a request “looks normal” into a set of facts that can be checked before acting.
Service decisions should account for changing network rewards, exit queues, validator penalties, smart-contract risk, third-party dependencies and digital-asset price volatility. No outcome should be treated as guaranteed.
Key point
A good support workflow first separates device-display issues, network status, transaction confirmation and third-party DApp behavior. imtoken support information should never ask for a seed phrase, private key or verification code.
Principles for security incidents
Security boundaries remain important throughout Support. imtoken will never ask for a seed phrase, private key or verification code. Do not send those secrets to anyone or enter them into an unfamiliar website. Before a transfer, signature or approval, review the address, network, amount, spender and permission scope. Third-party DApps and smart contracts can introduce risks outside a wallet’s control.
When working through “Principles for security incidents”, separate what the interface displays from what the blockchain records. A wallet can organize information, prepare a request and show the result, but the selected network ultimately determines transaction and contract state. For Support, confirm the network, account and destination rather than relying only on familiar buttons or visual cues.
A practical review sequence is source, target, permission and outcome. Identify where the request came from, what address or contract it affects, what authority it is asking for, and what may happen after approval. This turns a vague sense that a request “looks normal” into a set of facts that can be checked before acting.
If the interface does not match expectations, avoid immediately repeating the action. Check the selected network, whether a transaction hash exists, whether an explorer shows the record, and whether the token or contract address matches the intended asset. Confirmation can take time, especially when a network is congested.
Service decisions should account for changing network rewards, exit queues, validator penalties, smart-contract risk, third-party dependencies and digital-asset price volatility. No outcome should be treated as guaranteed.
Key point
A good support workflow first separates device-display issues, network status, transaction confirmation and third-party DApp behavior. imtoken support information should never ask for a seed phrase, private key or verification code.
Practical checklist
- Do not treat rewards as fixed or guaranteed.
- Understand exit and withdrawal waiting periods.
- Consider validator penalties and network conditions.
- Review smart-contract and third-party service risk.
- Consider digital-asset price volatility and your own circumstances.