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.

Product & Security Updates

Learn product notes, network alerts, security reminders and service notices with practical security checks and on-chain verification guidance.

Updates and notices

Product Notice

Wallet workflow

Review the active network and asset contract before a transfer.

Security Notice

Protect recovery material

Keep seed phrases and private keys offline and never send them to support.

Network

Confirmation delays

Busy networks can increase fees or waiting time; use the transaction hash to check status.

Service

Approval review

Periodically revoke DApp permissions you no longer need.

Recent Update

Layer 2 learning guide

Review network selection, bridging and withdrawal waiting time.

Common mistakes and verification

Common mistakes include using the wrong network, copying a bad address, ignoring token contracts, treating pending transactions as failures, or accepting an unclear approval. Troubleshoot product notes, network alerts, security reminders and service notices with verifiable data such as transaction hashes, block heights, address history and contract addresses instead of relying only on interface messages.

Common mistakes include using the wrong network, copying a bad address, ignoring token contracts, treating pending transactions as failures, or accepting an unclear approval. Troubleshoot product notes, network alerts, security reminders and service notices with verifiable data such as transaction hashes, block heights, address history and contract addresses instead of relying only on interface messages.

Security and risk boundary

Seed phrases and private keys should remain under the user’s control. Official support should not request them, and verification codes should never be shared. Third-party DApps, smart contracts and network services can introduce risk. Because confirmed transactions are usually not reversible by the wallet alone, pre-signing checks are essential.

Seed phrases and private keys should remain under the user’s control. Official support should not request them, and verification codes should never be shared. Third-party DApps, smart contracts and network services can introduce risk. Because confirmed transactions are usually not reversible by the wallet alone, pre-signing checks are essential.