Understand important changes before you act

This section brings together product guidance, network checks, security reminders and service information. When no verified publication date is available, the site does not invent one; the priority is the information users need before making a wallet decision.

ProductNetworkSecurityService

Recent Update

Review the whole transaction context, not one field

Many multi-chain wallet mistakes happen because the network, address, asset and request details are reviewed separately. Before acting in imtoken, ask four connected questions: which network is active, which asset is involved, whether the destination is correct, and what the current request will actually change. An asset name or familiar-looking address format provides only part of that context. The active network and public on-chain state remain essential checks.

After a transaction is submitted, use its transaction hash on the appropriate network to review status. A pending state is not, by itself, a reason to repeatedly send the same transfer. Confirm the network, account and transaction hash first, then decide whether any further action is appropriate.

Product Notice

Creating, importing and backing up a wallet are different actions

Creating a wallet produces new recovery material. Importing uses recovery material that already controls an account. Backing up means preserving that recovery material in a way the user can continue to control. Screenshots, chat apps, email and cloud notes should not be treated as a default backup method. Seed phrases and private keys remain under the user’s control, and official personnel will not request them.

Before changing devices or reinstalling software, confirm that you understand the correct recovery method. Stop any “migration,” “verification” or “sync” flow that asks you to enter a seed phrase, private key or verification code into an ordinary web page.

Read guide

Network

A similar address format does not mean assets share one network

Several EVM networks can use similar address formats, while balances, gas, contracts, transaction history and approval state remain separate. When receiving assets, verify both the address and the network chosen by the sender and receiver. Layer 2 or cross-layer transfers may add bridge or settlement steps that require their own confirmation checks.

If an asset does not appear where expected, check the current network, token contract and transaction hash before sending another transfer simply because the address looks familiar.

Network guide

Security Notice

Every signature and approval still needs a separate decision after connecting

A wallet connection allows a DApp to request account-related access; it does not mean later signatures, transactions or token approvals should be accepted automatically. Review the domain, account, asset movement, approval target and permission scope before confirming. If you cannot explain what a signature is asking for, stop rather than approving it merely to finish a workflow.

Disconnect DApps that are no longer needed and consider revoking on-chain approvals that no longer serve a purpose. A previous connection is not proof that a third-party contract is safe.

Approval security

Service

All download actions use the site’s single download entry

Download buttons across the site lead to the same local download page instead of exposing multiple final destinations throughout content pages. Downloads should start only after a user action, without hidden redirects, countdown pressure or repeated pop-ups. When the desktop download service is unavailable, the page can present a concise maintenance state and links back to either language homepage.

Before downloading, verify that you are using the intended website entry. After installation or wallet creation, recovery materials should still remain under your own control.

Download entry

Security Notice

Review address, network and amount before sending

After copying an address, compare identifying characters or use another reliable verification method to reduce clipboard-replacement risk. Then confirm that the asset network matches the recipient’s expected network and review the amount together with the estimated network fee. For an unfamiliar route, a smaller test transfer may help validate the process, while still incurring normal network fees.

On-chain transactions generally cannot be reversed by a wallet provider, which makes pre-send verification more valuable than trying to recover from an incorrect submission.

Transaction checks