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.
A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken

Manage Multi-chain Assets and Connect to Web3 with Clarity

Learn how to handle multi-chain assets, choose networks, send and receive funds, connect to DApps, review approvals, understand blockchain networks and build safer wallet habits through one connected learning path.

Multi-chain assetsNetwork checksDAppsApproval security
imtoken mobile wallet interface illustration

Start with the task you need to complete

01

Create a Wallet

Understand seed phrases and control before creating a new address.

View steps →
02

Back Up a Wallet

Keep recovery information offline and avoid screenshots or casual cloud sync.

Backup guidance →
03

Receive Assets

Confirm that the sender and receiver are using the same network.

Receive safely →
04

Send Assets

Review the address, network, amount and gas before confirming.

Transaction checks →
05

Connect to a DApp

Verify the domain and review each signature or approval separately.

DApp guide →

Wallet capabilities organized around real use

Multi-chain assets

When reviewing assets across networks, identify the network first, then check the address, gas currency and confirmation state.

Multi-chain network relationship illustration

imtoken App

Use the mobile wallet for network management, asset views, transaction history and DApp access while keeping the device environment under your control.

imtoken App product illustration

Send & Receive

Destination address, network, amount, gas and transaction hash form one verification chain.

Transfer guide →

imtoken Web

Browser connections require separate review of account requests, signatures and approvals.

Web usage →

Wallet security

Seed phrases and private keys stay under user control. Keep backups offline and review device security and approvals over time.

Offline private key protection illustration

Explore blockchain networks

A familiar address format does not mean two networks share the same state. Network choice affects gas, confirmations, EVM compatibility and Layer 2 transfer paths.

Multi-chain

Each chain has its own ledger, fee market and confirmation rhythm. Confirm the current and destination networks before sending.

Multi-chain network structure

Public chains

Nodes propagate transactions, consensus determines block order, and block explorers expose public on-chain state.

Public chain blocks and nodes

EVM networks

EVM networks share a similar contract model while chain IDs, gas currencies and state remain separate.

EVM-compatible network illustration

Layer 2

Layer 2 systems have settlement relationships with a base layer, and cross-layer transfers may involve bridges and waiting periods.

Layer 2 and base-layer relationship

A six-step wallet path

01

Get imtoken

Use a trusted entry point and never submit recovery credentials to an unfamiliar site.

02

Create or import a wallet

Understand addresses and control, and only handle recovery information in a trusted wallet environment.

03

Back up offline

Keep seed phrases offline and never disclose private keys or verification codes.

04

Select and verify the network

Confirm the chain, gas currency, destination address and service support.

05

Receive or send assets

Review address, network and amount, then keep the transaction hash for verification.

06

Review transactions and approvals

Read DApp requests before signing and periodically revoke permissions you no longer need.

Web3 & DApps: connection is not blanket consent

Connecting a wallet does not mean every later request should be approved. Review every signature and permission on its own terms.

Open the Web3 guide →
Visit the DApp
Verify the domain
Start the connection
Review account requests
Inspect signatures or approvals
Complete the intended action
Disconnect unused sessions

Security is a repeatable habit, not a single switch

Users control their seed phrases and private keys, and imtoken staff will never ask for them. Before sending, signing or approving, review the address, network, amount and exact request. Confirmed on-chain transactions are generally not reversible by the wallet, and third-party DApps and smart contracts can introduce additional risk.

Public computers, public networks, remote-control tools and untrusted browser extensions can all increase exposure. Put the review step before every sensitive action.

Open the Security Center →
Offline wallet key protection
  • Back up seed phrases offline
  • Never disclose private keys
  • Verify network and address
  • Inspect signature requests
  • Manage DApp approvals
Featured starter guide

What Should You Understand Before Using a Digital Wallet?

Addresses identify on-chain accounts, seed phrases and private keys relate to control, networks determine where a transaction happens, gas pays for execution, and transaction hashes help you verify results. Web3 adds another layer: connections, signatures, transactions and approvals are separate actions.

Start learning →
Networks

Public chains and confirmations

Understand blocks, confirmation depth and explorer checks.

Contracts

EVM and smart contracts

Understand addresses, gas, tokens and contract calls.

Layer 2

Check the network before bridging

Learn about bridges, waiting periods and arrival confirmation.

Security

DApp approvals and wallet safety

Make signature and permission review part of every workflow.

Ethereum Staking Basics

Ethereum PoS uses validators to participate in consensus. Rewards come from protocol mechanisms and can change with network conditions; exits can also involve waiting periods.

Learn about Ethereum staking →

Product and security updates

Recent Update

Wallet review checklist

Keep address, network and fee checks in place before transfers and network switches.

Security Notice

Do not submit recovery secrets to websites

Normal connection, support and claim flows should never ask for a seed phrase or private key.

Network

Assets do not automatically sync across networks

Choosing the wrong network can create confusing balance or arrival results.

Product Notice

Review signatures and approvals separately

An account connection does not remove the need to inspect each later request.

Frequently Asked Questions

Why can the same address format appear on multiple networks?

EVM networks can use the same address format, while balances and transaction state remain separate.

How do I verify a transfer?

Use the transaction hash in the relevant network's block explorer to check status, confirmations and execution.

What should I watch after connecting a DApp?

A connection creates a session; each later signature, transaction and approval still needs separate review.

Can I give my seed phrase to support?

No. imtoken staff will never ask for a seed phrase, private key or verification code.

Why can a Layer 2 transfer take time?

Cross-layer flows can involve bridges, proofs or exit queues depending on the network design.

Does Ethereum staking guarantee returns?

No. Rewards vary, and validator, contract, exit and market risks remain.

Start with a clear first step

After getting imtoken, secure your backup before moving on to networks, transfers and approval checks.

Download imtoken