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
中文Download
Wallet & Assets

imtoken App

This guide connects the practical decisions behind mobile wallet, multi-chain network management, and asset viewing. It focuses on verifiable on-chain information, clear user actions, and security habits that remain useful even when interfaces change.

Download imtokenSecurity guide →
Use case

Confirm the asset network first, then verify the address, request and on-chain result.

Product use

Start from the task, then verify the network

A wallet interface is useful when each action can be tied back to a network, an address, a permission request and a verifiable result.

On this page
  1. How the wallet experience is organized
  2. Using mobile wallet with multi-chain network management
  3. Checking asset viewing and transaction history against the chain
  4. Web3 connections and permission boundaries
  5. A practical everyday workflow
  6. Security and product boundaries

How the wallet experience is organized

imtoken App is organized around user tasks: create or import a wallet, back up recovery information, choose a network, view assets, send or receive, inspect transactions, and connect to DApps. The objective is to help users understand what they are doing at each stage instead of presenting a wall of disconnected features; in imtoken App, read this specifically alongside “How the wallet experience is organized” and mobile wallet. When working through “How the wallet experience is organized,” check the source, network, request details and resulting state in that order, with extra attention to mobile wallet and multi-chain network management.

Using mobile wallet with multi-chain network management

mobile wallet and multi-chain network management are closely related in a multi-chain wallet. Assets belong to specific networks, so both parties should confirm the network and destination before a transfer; in imtoken App, read this specifically alongside “Using mobile wallet with multi-chain network management” and multi-chain network management. EVM addresses may look the same across several networks, but that visual similarity does not mean assets move between those networks automatically; in imtoken App, read this specifically alongside “Using mobile wallet with multi-chain network management” and multi-chain network management. Do not treat an interface success message as the final answer for imtoken App. Use multi-chain network management, asset viewing and transaction history to confirm that the expected change occurred on the intended network.

Checking asset viewing and transaction history against the chain

asset viewing and transaction history help reconcile the wallet interface with public on-chain data. A transaction hash can be used to verify status, sender, recipient, fee, and confirmations; in imtoken App, read this specifically alongside “Checking asset viewing and transaction history against the chain” and asset viewing. If an asset is missing from the interface, check the selected network and token contract before repeating a transfer or importing an unknown token; in imtoken App, read this specifically alongside “Checking asset viewing and transaction history against the chain” and asset viewing. If “Checking asset viewing and transaction history against the chain” is unclear, stop before approving and return to the basics of asset viewing and transaction history, then verify the result with a transaction hash, contract address or block record where applicable.

Web3 connections and permission boundaries

For Web3 activity, a wallet connection only establishes an interaction channel; in imtoken App, read this specifically alongside “Web3 connections and permission boundaries” and transaction history. Each signature, token approval, and contract transaction has its own effect and should be reviewed separately; in imtoken App, read this specifically alongside “Web3 connections and permission boundaries” and transaction history. Activities involving DApp connections deserve particular attention to the requester, approval scope, and contract address. A durable routine for imtoken App is to make transaction history a first-pass check, use DApp connections as a second check, and rely on verifiable information related to local device security rather than interface assumptions.

A practical everyday workflow

A useful everyday sequence is to confirm the device and site, check the wallet account and network, review the address/amount/gas before sending, verify the transaction afterwards, and read every DApp request before signing; in imtoken App, read this specifically alongside “A practical everyday workflow” and DApp connections. When a session is no longer needed, disconnect and consider revoking permissions that should not remain active; in imtoken App, read this specifically alongside “A practical everyday workflow” and DApp connections. This part of imtoken App should be read together with the surrounding workflow: DApp connections affects how you interpret local device security, while mobile wallet helps confirm the state after the action.

Security and product boundaries

imtoken App cannot remove the risks of blockchain networks, third-party DApps, smart contracts, or market volatility. Seed phrases and private keys remain under the user’s control, and imtoken will not ask for them; in imtoken App, read this specifically alongside “Security and product boundaries” and local device security. For local device security and other sensitive activity, use a trusted device and avoid public or remotely controlled environments. For imtoken App, connect local device security with mobile wallet and multi-chain network management; the important part is the relationship between those concepts and the on-chain evidence you can verify afterward.

Security and risk reminder

Seed phrases and private keys are controlled by the user. imtoken will never ask for them. Blockchain transactions are generally irreversible by a wallet provider, and third-party DApps, smart contracts, network conditions and digital-asset prices can introduce additional risk.