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

Create & Backup

Follow a clear path from preparation and execution to verification, common errors and security checks.

Server-rendered HTMLOn-chain verifiableSecurity-first education

Control credentials

Seed phrases and private keys are recovery credentials, not ordinary account passwords. This topic should be understood through both user workflow and verifiable on-chain results. The wallet interface helps with context, but the network, address, contract and transaction state remain the source of truth.

In practice, combine interface information with data you can verify on-chain. If anything is unclear, stop before a high-value action and confirm the network, address, contract or transaction state.

Offline backup

Record recovery information accurately and prefer a non-networked storage method. This topic should be understood through both user workflow and verifiable on-chain results. The wallet interface helps with context, but the network, address, contract and transaction state remain the source of truth.

In a multi-chain environment, the network name, native gas asset, block explorer and contract address create the decision context. Icons, symbols and screenshots are only supporting cues.

Import environment

Disable screen sharing, recording and remote control while importing a wallet. This topic should be understood through both user workflow and verifiable on-chain results. The wallet interface helps with context, but the network, address, contract and transaction state remain the source of truth.

Seed phrases and private keys remain under user control, and official staff will never request them. Any website or person asking for recovery material or verification codes should not be trusted.

Verify without sharing

Checking a backup never requires sending the phrase to a website or support agent. This topic should be understood through both user workflow and verifiable on-chain results. The wallet interface helps with context, but the network, address, contract and transaction state remain the source of truth.

When a third-party DApp, bridge or smart contract is involved, consider permission scope, contract risk, congestion and service dependencies. Confirmed on-chain transactions usually cannot be reversed by a wallet.

Recovery checks

After restoring, verify expected addresses and networks before important activity. This topic should be understood through both user workflow and verifiable on-chain results. The wallet interface helps with context, but the network, address, contract and transaction state remain the source of truth.

After the action, keep the transaction hash and review confirmations to build independent verification habits. Revisit persistent connections and approvals when they are no longer needed.

Review after the action

After completing the task, compare the on-chain state with what you expected. Network, transaction hash, block height, confirmation count and approval status can reveal display delays, network mistakes or permissions that remain active longer than intended. Security is an ongoing review process, not a one-time setting.

Continue with imtoken

The download entry points to download.html. Back up first and verify the network before acting.

Download imtoken