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 Multi-chain Wallet

Manage Multi-chain Assets and Connect to Web3 with Clarity

A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken

Move from multi-chain asset views and network selection to receiving, sending, DApp connections, approvals, network fundamentals and wallet security with a workflow built around clear checkpoints.

Multi-chain assetsNetwork checksWeb3 approvalsSecurity habits
imtoken mobile wallet interface
Wallet capabilities

Keep the network context visible from assets to connections

Multi-chain network and asset relationship

Multi-chain assets

The same token name can exist on different networks. Read balances, receiving addresses and token contracts in the correct network context.

Understand multi-chain networks →

Send & Receive

Review destination address, network, amount, gas and transaction hash as one complete flow.

See the workflow →
imtoken App product view

imtoken App

Mobile access for asset views, network management, transaction history and DApp activity.

Explore the App →

imtoken Web

Understand account requests, approvals, DApp access and disconnection boundaries in the browser.

Explore Web use →
Offline protection of recovery secrets

Wallet security

Keep seed phrases and private keys under your own control, prioritize offline backup and review unused approvals.

Open Security Center →
Blockchain networks

Choose the right network before thinking about fees and confirmations

Multi-chain networks

Multi-chain

Similar address formats do not mean assets live on the same network. Confirm chain, network and asset context first.

Learn more →
Public chain nodes and blocks

Public Chains

Distributed nodes maintain a public ledger, while later blocks can add confidence to a recorded transaction.

Learn nodes and blocks →
EVM network and smart contract

EVM Networks

Understand addresses, gas, token contracts and approvals without overlooking network separation.

Understand EVM →
Layer 2 and base chain relationship

Layer 2

Moving across layers may involve bridges, waiting periods and extra confirmations rather than a normal same-chain transfer.

Learn Layer 2 →

Gas & Confirmations

Fees change with network conditions and complexity. Use the transaction hash to understand pending, successful and failed states.

Learn confirmations →
Wallet journey

Build a clearer wallet workflow in six steps

  1. 01

    Get imtoken

    Use a trusted entry point to the download page rather than an unsolicited file link.

  2. 02

    Create or Import

    Handle recovery information only inside a wallet environment you trust.

  3. 03

    Back Up Offline

    Keep the seed phrase offline and never disclose a private key.

  4. 04

    Select and Verify the Network

    Make sure the asset, address and destination service use the intended network.

  5. 05

    Receive or Send

    Review address, network, amount and expected network fee before sending.

  6. 06

    Review Transactions and Approvals

    Read DApp signatures carefully and remove permissions you no longer need.

Web3 & DApps

A connection is only the beginning; review every request separately

Connecting a wallet does not mean every later request should be accepted. Domain, account, signature content, approval target and permission scope all require their own review.

Open the Web3 guide →
Visit DAppVerify domainConnectReview account requestCheck signature or approvalComplete actionDisconnect when no longer needed
Connecting a wallet does not mean every signature request should be accepted. Review each signature and approval independently.
Security

Protect recovery secrets, devices, approvals and transfers with one consistent routine

Seed phrases and private keys remain under the user’s control. imtoken personnel will never ask for them or request verification codes through chat, web forms or remote-support tools. On-chain actions are generally irreversible, and third-party DApps and smart contracts introduce separate risks.

Open Security Center →
Offline protection of private keys and recovery information
  • Back up the seed phrase offline
  • Never disclose a private key
  • Verify network and address
  • Review signature requests
  • Manage DApp approvals
Ethereum & PoS

Ethereum Staking Basics

Learn how proof of stake, validators, reward sources, network conditions, withdrawals and exits fit together. Rewards are not fixed and can change with protocol and network conditions.

Read Ethereum staking basics →
FAQ

Frequently Asked Questions

Should I give a seed phrase or private key to imtoken personnel for verification?

No. Recovery secrets remain under your control, and imtoken personnel will never ask for them.

Can the wallet reverse a confirmed transaction?

Generally no. Review address, network and amount before submitting an on-chain transaction.

Why can the same address format appear on different EVM networks?

Compatible networks can share an address format while keeping balances and transaction state separate.

Does connecting a DApp automatically approve tokens?

No. A connection and a token approval are different requests and should be reviewed separately.

Is gas a fixed fee?

No. Gas depends on network conditions, transaction complexity and fee settings.

Does staking guarantee returns?

No. Rewards can change, and validator, contract, service and market risks remain.

View the full FAQ →
imtoken

Start with clear network and security checks

Every download button leads to the imtoken download page. Keep enough time to review transfers, signatures and approvals before confirming them.

Download imtoken