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

Manage Multi-chain Assets and Connect to Web3 with Clarity

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

Understand multi-chain assets, network selection, sending and receiving, DApp connections, token approvals, blockchain concepts and wallet security in one clear workflow. Every onchain action should be based on verifiable details and an independent review.

Multi-chain assetsDAppApproval checksSecurity education
imtoken App product interface
Verify the network firstThen send, sign or approve
Common tasks

Start with what you need to do now

Each task leads to a fuller workflow with security checks.

01

Create a Wallet

Understand creation versus import and initialize in a trusted environment.

View guide →
02

Back Up a Wallet

Keep the seed phrase offline; do not screenshot or send it to anyone.

View guide →
03

Receive Assets

Confirm the receiving network, then verify address and asset type.

View guide →
04

Send Assets

Review address, network, amount, gas and token before sending.

View guide →
05

Connect to a DApp

Verify the domain and assess connection, signatures and approvals separately.

View guide →
Wallet capabilities

Keep assets, networks and security in one connected workflow

Multi-chain network illustration

Multi-chain assets

Keep the active network in context when reviewing assets, and distinguish native assets, token contracts and confirmations.

Understand multi-chain →
imtoken App mobile view

imtoken APP

Manage networks, assets and transaction history on mobile while maintaining device and backup security.

WEB3

imtoken Web

A browser connection is not the same as asset permission. Review every signature and approval independently.

Learn about Web use →
Offline private-key protection illustration

Wallet security

Back up seed phrases offline, keep private keys private, review signature targets and remove DApp approvals you no longer need.

Open Security Center →
Explore networks

Know which chain you are actually using

Multi-chain

A multi-chain wallet manages several independent networks in one interface. Switching networks does not move assets across chains.

Before acting, confirm the active network, address, native gas asset and transaction target.

Open network guide →
Multi-chain
Public Chains

Public chains are maintained by distributed nodes, and transactions gain additional confirmation as more blocks are added.

Before acting, confirm the active network, address, native gas asset and transaction target.

Open network guide →
Public Chains
EVM

EVM networks may share address formats and contract concepts, but balances, gas and state remain network-specific.

Before acting, confirm the active network, address, native gas asset and transaction target.

Open network guide →
EVM
Layer 2

Layer 2 systems settle in relation to a base chain. When moving assets across layers, verify the bridge route, destination network and arrival status.

Before acting, confirm the active network, address, native gas asset and transaction target.

Open network guide →
Layer 2
Gas & Confirmations

Gas represents execution cost; confirmation represents onchain progress after inclusion. They are related but not the same.

Before acting, confirm the active network, address, native gas asset and transaction target.

Open network guide →
Gas & Confirmations
Wallet journey

Six steps for a repeatable wallet workflow

  1. 01

    Get imtoken

    Use the single download entry for the product flow.

  2. 02

    Create or import a wallet

    Initialize in a trusted environment and share no recovery material.

  3. 03

    Back up offline

    Keep the seed phrase offline; do not screenshot or upload it.

  4. 04

    Choose and verify the network

    Confirm the network, address format, gas asset and target asset.

  5. 05

    Receive or send assets

    Review address, network, amount and fee before sending.

  6. 06

    Review transactions and approvals

    Check the transaction hash and review DApp approvals you no longer need.

Web3 & DApp

Connection is only the beginning; review each request separately

Connecting a wallet does not mean every signature request should be approved. Review each signature and approval independently.

Read the full Web3 guide →
  1. Visit the DApp
  2. Verify the domain
  3. Connect
  4. Review account request
  5. Review signature or approval
  6. Complete the action
  7. Disconnect when no longer needed
Security

Security comes from repeatable, verifiable choices

Seed phrases and private keys remain under the user’s control, and official staff will not ask for them. Never send a seed phrase, private key or verification code to anyone. Check address, network and amount before a transfer; review every DApp signature and approval target; consider revoking permissions you no longer use. Use extra care on public devices, public networks and remote-access environments.

Open Security Center
Offline private-key protection illustration
  • Back up seed phrases offline
  • Never disclose private keys
  • Verify network and address
  • Review signature requests
  • Manage DApp approvals
Ethereum & PoS

Ethereum Staking Basics

Understand Ethereum PoS, validators, reward sources, network state, withdrawals and exits. Rewards can change and exits can involve waiting.

Learn Ethereum staking →

Before participating

  • Validators can face protocol penalties
  • Smart contracts involve technical risk
  • Exits can involve waiting
  • Digital asset prices fluctuate
  • Third-party services can add risk
Understand validators →
Product & security updates

Recent notices, organized by what matters

View all updates →
Product Notice

Wallet workflow guidance updated

Review related guidance and checks without relying on unverified dates or market claims.

Network

Confirm the active network before multi-chain actions

Review related guidance and checks without relying on unverified dates or market claims.

Security Notice

Never provide a seed phrase or private key

Review related guidance and checks without relying on unverified dates or market claims.

Service

Understand staking exit and waiting mechanics

Review related guidance and checks without relying on unverified dates or market claims.

FAQ

Frequently asked questions

No. Seed phrases and private keys should remain under the user’s control, and official staff will not ask for them.

Onchain transactions are generally not reversible by a wallet provider. Verify address, network, amount and fee before sending.

Because each network maintains independent state. A shared address format does not make assets portable across networks.

Connection usually establishes account access. Asset impact typically comes from later transaction signatures or token approvals, which should be reviewed separately.

Gas measures the resources used to execute a transaction or contract call; cost depends on network conditions and the operation.

No. Rewards can change, exits can take time, validators can face penalties, and technical and market risks apply.

Read the full FAQ →
imtoken

Start with clear network and security checks

Use the single download entry for imtoken. Keep seed phrases, private keys and verification codes private before and after installation.

Download imtoken