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

From viewing assets across networks and choosing the right chain to sending, receiving, DApp connections and approvals, imtoken organizes each action around clear checks. Wallet security belongs in every stage: creation, backup, transfers, signatures and ongoing approval management.

Multi-chain AssetsNetwork SelectionDAppsApproval ManagementWallet Security
imtoken mobile wallet interface illustration
01

Create a Wallet

Understand the environment, key ownership and backup responsibilities before creating a new wallet.

Start here →
02

Back Up a Wallet

Complete an offline backup early and never send a seed phrase, private key or recovery phrase to another person.

Backup principles →
03

Receive Assets

Confirm the network before sharing a public receiving address so both sides use a compatible chain.

Receiving flow →
04

Send Assets

Check the network, destination, amount and gas before submitting, then keep the transaction hash for verification.

Transfer checks →
05

Connect to a DApp

Verify the domain first, then evaluate every connection, signature and approval as a separate decision.

Connection guide →

Wallet capabilities organized around real tasks

Asset management becomes clearer when networks, addresses, transactions and security checks are part of one workflow.

Multi-chain Assets

Distinguish asset versions, address context and transaction state across networks. Multi-chain support does not mean assets automatically move between chains.

Multi-chain asset and network relationship

Send & Receive

Confirm the network and public address when receiving. Before sending, check network, address, amount and gas; after submission, use the transaction hash to follow confirmations.

Understand the flow →

imtoken App

View assets, manage networks, review transaction history and enter DApp workflows while keeping the device and backup environment under your control.

imtoken App asset and network management illustration

imtoken Web

Browser connections support DApp access and request review. A connected site is not automatically trusted; every signature still needs a fresh decision.

Explore Web connections →

Wallet Security

Seed phrases and private keys remain under user control. Offline backup, device security, signature checks and approval management work together.

Offline protection for wallet recovery material

Understand each on-chain action through its network

Every network has its own blocks, fees, contract state and confirmation rhythm. Learn the network before moving assets or interacting with contracts.

Multi-chain

One wallet can organize accounts and assets across several networks, but each action still takes place on one specific chain. Re-check asset version, address and network state every time you switch.

Explore multi-chain →
Multi-chain network structure

Public Chains

Nodes propagate transactions, blocks record state and confirmations show how a transaction is being built upon. Block explorers help verify public on-chain information.

Learn public-chain basics →
Public-chain blocks and nodes

EVM Networks

EVM-compatible networks often use similar address formats while keeping separate gas markets, contracts and asset states. Always interpret a contract address inside the current network.

Understand EVM →
EVM-compatible network illustration

Layer 2

Layer 2 networks relate to a base chain through settlement or security mechanisms. Moving between layers can involve bridges, waiting periods and additional confirmations.

Learn Layer 2 →
Layer 2 and base-chain relationship

Gas & Confirmations

Gas prices network resources; confirmations describe transaction progress. Fees, pending state, block height and the transaction hash should be read together.

Gas and confirmation guide →
Network confirmation and transaction state

A six-step wallet workflow you can verify

Each step has a clear checkpoint so networks, assets and permissions remain understandable.

01

Get imtoken

Use the official download entry rather than unknown links or temporary file sources.

02

Create or Import

Use a device you control and understand that a seed phrase or private key represents account control.

03

Back Up Offline

Keep the seed phrase offline, avoid cloud screenshots and never disclose a private key or recovery phrase.

04

Select and Verify the Network

Confirm where the asset exists, the target network and the address context before acting.

05

Receive or Send

Check address, network and amount before sending, understand gas and use a small test when appropriate.

06

Review Transactions and Approvals

Keep the transaction hash, review confirmations and remove connections or approvals you no longer need.

Web3 Workflow

A connection is only the beginning

From the domain to the account request, signature and approval target, each step deserves its own decision. Connecting a wallet does not mean every later request should be accepted.

Open the Web3 guide

Visit the DApp

Enter through a trusted route rather than an unsolicited message.

Confirm the Domain

Check spelling and context before connecting.

Start the Connection

Confirm the active network and account being exposed.

Read the Account Request

Understand what the site wants to see or call.

Review Signature or Approval

Check target, content, allowance and likely outcome.

Disconnect When Done

Remove old connections and review remaining approvals.

Security

Reliable security comes from repeatable checks

A wallet puts account control in the user’s hands, which means recovery material, device context and on-chain requests all require judgment. Keep seed phrases and private keys offline; imtoken staff will not ask for them. Verify network, address and amount before transfers, then inspect domains, signatures and approval scope during DApp use. Third-party DApps and smart contracts can carry risk, and confirmed on-chain transactions generally cannot be reversed by the wallet alone.

Open the Security Center
Offline wallet security illustration
  • Back up the seed phrase offline
  • Never disclose private keys
  • Verify network and address
  • Review signature requests
  • Manage DApp approvals

Academy: from concepts to confident actions

Learn the terminology first, then the workflow, then build security into the habits that remain.

Featured Guide

What Should You Understand Before Using a Digital Wallet?

An address identifies an account for receiving. A seed phrase and private key relate to control. The network determines where an action happens. Gas pays for network resources. A transaction hash locates an on-chain transaction. DApps can request connections, signatures and approvals. Linking these ideas together makes independent verification possible.

Read the beginner guide

Ethereum & PoS: understand the mechanics before participating

Staking is not a fixed-return product. Rewards, waiting periods, validator state, penalties, technical risk and market volatility all matter.

Ethereum Staking Basics

Ethereum PoS relies on validators. Rewards relate to network rules, while withdrawals and exits are separate flows that can involve waiting and state transitions.

Explore Ethereum staking →

Know Before Participating

Validators can face network penalties. Smart contracts and third-party services introduce technical and operational risk, and digital-asset prices can move sharply. Staking does not guarantee returns.

Understand PoS and validators →

Frequently asked questions

Start with the most common decisions around backup, networks, transactions, Web3 and staking.

View all FAQ

Ready to get started with imtoken?

Review backup, network and transfer-check principles before downloading.

Download imtoken