Support
imtoken Support: clear product guidance, practical steps and risk-aware explanations covering issue diagnosis, transaction lookup, security incidents, information preparation, self-service checks.
Support guidance helps diagnose network, transaction, approval and security issues, but never asks users to submit a seed phrase, private key or verification code.
Service scope
Support makes more sense when issue diagnosis, transaction lookup, security incidents, information preparation, self-service checks are considered as parts of one on-chain workflow. The goal is not to memorize more terminology, but to make each action explainable, verifiable and reviewable.
During real use, confirm the active network and account first, then verify the object, scope and expected outcome related to issue diagnosis. Any action that changes assets, permissions or account state deserves a full review before confirmation.
How to begin
During real use, confirm the active network and account first, then verify the object, scope and expected outcome related to issue diagnosis. Any action that changes assets, permissions or account state deserves a full review before confirmation.
For transaction lookup, prefer information that can be independently checked: the wallet transaction summary, the relevant network explorer, an explicit contract address or an official product page. Breaking an action into separate checks reduces mistakes caused by familiar-looking pages, similar links or urgent prompts.
Information to prepare
For transaction lookup, prefer information that can be independently checked: the wallet transaction summary, the relevant network explorer, an explicit contract address or an official product page. Breaking an action into separate checks reduces mistakes caused by familiar-looking pages, similar links or urgent prompts.
When security incidents is involved, separate display data from on-chain facts. Names, icons and fiat estimates may come from external data sources, while balances, transaction state and approvals should be verified on the selected network.
Risk and boundaries
When security incidents is involved, separate display data from on-chain facts. Names, icons and fiat estimates may come from external data sources, while balances, transaction state and approvals should be verified on the selected network.
For information preparation, retain the transaction hash or other useful reference when appropriate. On-chain transactions generally cannot be reversed unilaterally by a wallet, which makes pre-broadcast checks of the address, network, amount and permissions especially important.