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 & Web3 Hub

Manage Multi-chain Assets and Connect to Web3 with Clarity

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

Use one clear workflow to understand multi-chain assets, network selection, sending and receiving, DApp connections, token approvals, network concepts and wallet security.

Multi-chain assetsDAppApproval reviewWallet security
imtoken mobile wallet interface

Start with a task

Five common wallet actions

Wallet capabilities

One wallet experience, multiple on-chain contexts

Review the network, address and request behind each action instead of assuming similarly named assets behave the same way.

multi-chain network illustration

Multi-chain assets

Understand network differences, address checks and transaction confirmation before moving assets.

Explore networks →

imtoken APP

Manage networks, assets and transaction history from a mobile environment.

imtoken app product preview

Send & Receive

Review address, network, amount, gas and transaction hash as one workflow.

Transfer guide →

imtoken Web

Connect in the browser while reviewing accounts, signatures, approvals and disconnection.

Web guide →
offline private key protection

Wallet security

Protect recovery information, prefer offline backup and review permissions.

Network explorer

Understand the network before moving assets

multi-chain network relationships

Multi-chain does not mean automatic interoperability

Assets with the same symbol can exist on different networks. Verify network, contract and bridge route.

Read the guide →
public chain nodes and blocks

Understand the ledger through nodes and blocks

Use nodes, blocks, transactions, confirmations and explorers to understand chain state.

Read the guide →
EVM compatible networks

Similar addresses do not mean the same network

EVM-compatible networks can use different chain IDs, gas assets and contracts.

Read the guide →
Layer 2 and mainnet relationship

Understand settlement and cross-layer routes

Cross-layer movement can involve bridges, waiting periods and multiple confirmation stages.

Read the guide →
gas and transaction confirmation

Separate network cost from transaction state

Gas depends on network conditions, while completion should be verified by transaction hash and explorer.

Read the guide →

Wallet workflow

Six steps from setup to review

  1. 01

    Get imtoken

    Begin from a trusted download entry point rather than an unknown message or ad.

  2. 02

    Create or import a wallet

    Understand seed phrases and private keys before creating or importing.

  3. 03

    Back up offline

    Keep recovery words offline and never send them to anyone.

  4. 04

    Choose and verify the network

    Confirm the asset network, destination network, address and fee asset.

  5. 05

    Receive or send assets

    Review address, network, amount and gas; consider a small test for high-value transfers.

  6. 06

    Review transactions and approvals

    Save transaction hashes, check confirmations and remove permissions you no longer need.

Web3 & DApp

Review every request in context

A wallet connection does not mean every later request should be approved. Review each signature and approval separately.

Open the Web3 guide →
1

Open the DApp

2

Verify the domain

3

Request a connection

4

Review the account request

5

Inspect signatures or approvals

6

Complete the intended action

7

Disconnect unused connections

Security center

Protect control before convenience

Your seed phrase and private keys remain under your control. imtoken staff will never ask for them. Before transferring, signing or approving, verify the address, network, domain and permission scope. On-chain transactions generally cannot be reversed by a wallet provider, and third-party DApps or smart contracts may introduce additional risk.

Open security center →
offline key protection
  • Back up seed phrases offline
  • Keep private keys private
  • Verify network and address
  • Review signing requests
  • Manage DApp approvals

Academy · Featured

What Should You Understand Before Using a Digital Wallet?

Learn why addresses can be public while seed phrases and private keys must stay private, how networks and gas affect transfers, and why DApp connections and approvals require separate review.

Start learning →

Ethereum · PoS

Ethereum Staking Basics

Understand validators, reward sources, network status, withdrawals and exit flows before considering participation.

Learn staking →

What to understand before participating

  • Protocol penalties and validator status
  • Smart-contract technical risk
  • Exit and withdrawal waiting periods
  • Digital-asset price volatility
  • Third-party service risk

Staking does not guarantee returns. Rewards and waiting periods can change.

Updates

Information that helps you act safely

View all updates →

FAQ

Common questions before you act

A digital wallet manages keys, derives addresses and helps users interact with blockchain networks. Assets are recorded on the relevant chain rather than stored as files inside the wallet app.

No. Your seed phrase represents wallet control and remains under your custody. imtoken staff will never ask for a seed phrase, private key or verification code.

A seed phrase can derive one or more accounts, while a private key directly controls signing for a particular account. Both are sensitive recovery information.

Some EVM-compatible networks use similar address formats while maintaining independent state. Similar addresses do not make assets move automatically between networks.

Verify the full destination address, target network, asset and amount, then review gas and transaction details. Consider a small test for a high-value transfer when appropriate.

Gas is the network resource cost for processing a transaction or smart-contract call. It can change with congestion and transaction complexity and is not a fixed wallet fee.

A transaction hash identifies a specific on-chain transaction and can be used in a block explorer to check status, block inclusion and confirmations.

No. Connection usually establishes account visibility and a request channel. Message signatures, transactions and token approvals must still be reviewed separately.

View complete FAQ →

imtoken

Manage assets with a clearer review process

Use the Academy and Security Center whenever you need to verify a network, transaction or DApp request.

Download imtoken