imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.
imtoken

Support

A practical guide to pre-use checks, common questions, self-troubleshooting, security boundaries, and support paths, with clear decision points and risk boundaries.

What you can learn here

A practical guide to pre-use checks, common questions, self-troubleshooting, security boundaries, and support paths, with clear decision points and risk boundaries.

Important boundaries

No fixed returns are promised, and no user counts, partnerships, licenses, or rankings are invented. Evaluate on-chain and third-party services using verifiable information.

Understand the core idea first

The practical value of Support comes from understanding how pre-use checks, common questions, self-troubleshooting, security boundaries, and support paths relate to one another. Before an on-chain action, confirm the network, destination, request content, and any fee or permission that may be involved. Do not rely on appearance or naming alone when something is uncertain.

Practical check

Apply this to a real action: verify the target and network, read the request details, then confirm the result with on-chain information. Familiar interfaces should not replace verification.

How to evaluate a real action

When working with pre-use checks, common questions, self-troubleshooting, security boundaries, and support paths, break the task into four checks: identify the counterparty or target, verify the network, read the request, and verify the result afterward. Transfers require address, network, and amount checks; signatures and approvals require careful review of the requester and scope.

Practical check

Apply this to a real action: verify the target and network, read the request details, then confirm the result with on-chain information. Familiar interfaces should not replace verification.

Common mistakes and risk boundaries

Typical mistakes include assuming matching address formats mean matching networks, treating a DApp connection as permission to approve everything, and assuming a submitted transaction is already final. On-chain actions usually cannot be reversed by a wallet provider alone, so pre-action review matters.

Practical check

Apply this to a real action: verify the target and network, read the request details, then confirm the result with on-chain information. Familiar interfaces should not replace verification.

Build a repeatable safety routine

For pre-use checks, common questions, self-troubleshooting, security boundaries, and support paths, use a routine you can repeat: keep recovery material offline, never send seed phrases or private keys to anyone, use trusted devices, verify domains, review each signature or approval, and remove connections or approvals you no longer need.

Practical check

Apply this to a real action: verify the target and network, read the request details, then confirm the result with on-chain information. Familiar interfaces should not replace verification.