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

Explore multi-chain assets, network selection, sending and receiving, DApp connections, token approvals, network concepts, and wallet security in one structured experience designed around real user tasks.

Multi-chain AssetsNetwork ChecksDApp ApprovalsWallet Security
imtoken multi-chain wallet product interface
01

Create a Wallet

Understand seed phrases and private keys first, then prepare an offline backup immediately after setup.

View steps →
02

Back Up a Wallet

Keep recovery information offline, private, and protected from accidental sharing or loss.

Backup guide →
03

Receive Assets

Confirm the receiving address and network before sharing account details with a sender.

Receive checks →
04

Send Assets

Review the address, network, amount, and gas before broadcasting a transaction.

Send checks →
05

Connect to a DApp

Verify the domain, account request, signature details, and permission scope.

Connection guide →
Wallet Capabilities

Organized around real tasks, from asset views to security

Multi-chain network and asset relationship

Multi-chain Assets

One wallet can interact with multiple networks. Understanding network differences and checking addresses and confirmations are core habits.

Understand multi-chain →

Send & Receive

Addresses, networks, amounts, gas, and transaction hashes form the key checkpoints of an on-chain transfer.

View transfer flow →
imtoken App multi-chain asset interface

imtoken App

Use mobile tools for network management, asset views, transaction history, and DApp access.

Explore the App →

imtoken Web

Browser connections require careful checks of domains, account requests, signatures, and approvals.

Explore Web →
Offline seed phrase and private key security

Wallet Security

Users control their seed phrases and private keys. Offline backups, careful approvals, and transaction checks matter more than absolute security claims.

Open Security Center →
Blockchain Networks

Understand the network before moving assets or using contracts

Multi-chain networks

Multi-chain does not mean every network works the same way

Fees, confirmation speeds, asset standards, and DApp support vary by network. Confirm where the asset exists and what the destination supports.

Public chain nodes and blocks

Public chains maintain state through nodes and blocks

After broadcast, a transaction is accepted and included in a block. Explorers can show hashes, block heights, and confirmation status.

EVM-compatible network

EVM networks share an execution model, not a single network

Similar address formats do not make networks interchangeable. Gas, contract addresses, token approvals, and chain IDs still need checks.

Layer 2 and mainnet relationship

Layer 2 introduces mainnet and cross-layer considerations

Bridging may include source-chain transactions, destination settlement, and waiting mechanisms. Check both sides if a transfer is delayed.

Gas and confirmations describe network execution

Fees vary with network conditions and transaction complexity. After submission, distinguish broadcast, inclusion, and the confirmation depth you expect.

Usage Path

Build a repeatable on-chain workflow in six steps

  1. 01 Get imtoken

    Use the clear download entry and start the download through an explicit user action.

  2. 02 Create or Import

    Understand recovery information and never type a seed phrase into a website.

  3. 03 Back Up Offline

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

  4. 04 Select and Check the Network

    Verify the network, address format, and destination support.

  5. 05 Receive or Send Assets

    Check the address, network, amount, and estimated fee before sending.

  6. 06 Review Transactions and Approvals

    Inspect DApp signatures and periodically remove permissions you no longer need.

Web3 & DApps

A connection is only the start; each signature and approval needs its own decision

Connecting a wallet allows a DApp to request account interaction. It does not mean every later request should be accepted. Verify the domain, request type, signature details, and approval scope.

Read the Web3 guide →
Visit a DAppVerify the domainStart the connectionReview account accessCheck signature or approvalComplete the actionDisconnect when no longer needed
Security

Move risk checks before transfers, signatures, and approvals

Wallet security is a set of ongoing habits rather than a single switch. Keep seed phrases and private keys offline, avoid entering recovery information on unfamiliar websites, verify domains and account requests before using DApps, read the content of each signature, inspect approval targets and scope, and confirm the address, network, and amount before every transfer. Public devices, public networks, and remote-control sessions can add exposure and error risk. On-chain transactions generally cannot be reversed by a wallet, while third-party DApps and smart contracts may have technical or operational risks.

Open Security Center →
Offline backup and private key security
  • Back up the seed phrase offline
  • Never disclose a private key
  • Check the network and address
  • Review signature requests
  • Manage DApp approvals
Academy

What Should You Understand Before Using a Digital Wallet?

Addresses receive on-chain assets, seed phrases and private keys control accounts, networks determine where a transaction occurs, and gas is the cost of execution. Transaction hashes help locate on-chain status, while DApp connections and token approvals add separate permission and request layers.

Start with the beginner path →
NetworkPublic Chains & ConfirmationsFrom nodes and blocks to explorer checks.ContractsEVM & Smart ContractsGas, contract calls, and tokens.ScalingLayer 2 BasicsMainnet relationships and bridging.Web3DApp ApprovalsTargets, limits, and revocation.SecurityWallet SecurityBuild repeatable checks.
Ethereum & PoS

Ethereum Staking Basics

Learn how Ethereum PoS, validators, reward sources, network state, withdrawals, and exits fit together. Rewards can change with protocol and network conditions and are not guaranteed.

Read Ethereum Staking →
Updates

Product, network, and security information

FAQ

Quick answers about wallets and on-chain activity

Should I give my seed phrase or private key to support?

No. You control that information, and imtoken staff will not ask for it or for verification codes.

What should I check before sending?

Review the destination address, network, amount, and estimated fee before broadcasting.

Can I approve every request after connecting to a DApp?

No. A connection and later signatures or approvals are separate actions that each need review.

Why does gas change?

Gas costs depend on network conditions, transaction complexity, and current pricing.

Why can a Layer 2 exit take time?

Different Layer 2 systems have different settlement and withdrawal mechanisms, some of which include waiting periods.

Does staking guarantee returns?

No. Rewards can change, validators can be penalized, and contract, service, and market risks remain.

View the full FAQ →

Start with clear network and security checks

Every download entry goes to the imtoken download page. Confirm the network, address, and request details before any on-chain action.

Download imtoken