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

Bring multi-chain asset management, network selection, sending and receiving, DApp connections, approval review, network education and wallet security into one clear workflow. Every action starts by checking the network, address and request details.

Multi-chain assetsNetwork selectionSend & receiveDAppsApprovalsWallet security
imtoken mobile wallet product interface

Start with a task

Learn the wallet through real actions

Enter through the task you need to complete, then build the surrounding knowledge. Each route emphasizes verifiable information and clear security boundaries.

01

Create a Wallet

Understand the difference between creating and importing, and keep control of the wallet with you.

Start →
02

Back Up a Wallet

Record the seed phrase offline. Avoid screenshots, cloud syncing or sending it to anyone.

View guide →
03

Receive Assets

Confirm the receiving network first, then copy the address and make sure the sender uses the same network.

Review checks →
04

Send Assets

Review address, network, amount and gas before submission, then track the transaction hash.

Check the flow →
05

Connect to a DApp

Verify the domain and account request. Review every signature and approval separately.

Learn connections →

Wallet capabilities

Keep assets, networks, transactions and security in one workflow

Multi-chain assets

When moving between networks, understand network differences, address relationships and confirmation mechanics instead of treating same-named assets as one shared state.

Understand multi-chain networks →
Multi-chain network relationships

imtoken App

imtoken app product view

Review networks, assets and transaction history on mobile, and inspect DApp or signature requests before confirming.

Explore the App →

Send & receive

Use a fixed check order for receiving addresses, networks, amounts, gas and transaction hashes.

Open the guide →

imtoken Web

Understand account connections, approval prompts, DApp access and disconnecting without treating later requests as pre-approved.

Using imtoken Web →

Wallet security

Keep seed phrases and private keys offline where possible, and inspect the target and scope of every approval.

Open Security Center →
Offline backup and wallet security

Blockchain networks

Understand asset movement by starting with the network

Select a topic to explore network structure, asset paths, fees and confirmation behavior, then continue through the linked guide for more detail.

Multi-chain does not mean automatic interoperability

Networks maintain separate state. Check the destination network, address compatibility and asset standard before sending.

Learn more →
Multi-chain network diagram

Public chains maintain state through nodes and blocks

Transactions propagate through nodes, enter blocks and accumulate confirmations as the chain progresses.

Public chain basics →
Public chain nodes and blocks

EVM connects accounts, gas and smart contracts

Similar address formats do not make networks identical. Contract interactions also require checks of the target and approval scope.

Understand EVM →
EVM network and contracts

Layer 2 has an explicit relationship with its base layer

Cross-layer transfers may involve bridges, waiting periods and different confirmation paths.

Explore Layer 2 →
Layer 2 and mainnet relationship

Gas and confirmations shape transaction progress

Gas prices execution resources; confirmations help you understand how far a transaction has progressed after inclusion.

Gas & confirmation guide →

Wallet path

Six steps for a reviewable wallet routine

01 Get imtoken

Start from the dedicated download route

Use the imtoken download entry, then review backup and security principles before creating or importing a wallet.

02 Create or import

Understand wallet control first

Know what the seed phrase and private key represent before you begin using the account.

03 Back up offline

Do not depend on an online account

Prefer offline storage for the seed phrase and avoid screenshots or messaging apps.

04 Choose and verify the network

The network determines where state exists

Confirm both the network and address before a transfer.

05 Receive or send assets

Review amount and gas

Receiving requires network confirmation; sending adds checks for destination, amount and fees.

06 Review transactions and approvals

Check again after completion

Inspect DApp signatures before acting, then review transaction status and remove approvals you no longer need.

Web3 & DApps

Connection is not blanket consent

Connecting a wallet does not mean every later signature should be accepted. Review each signature and approval on its own.

Open the Web3 guide →
  1. Visit the DApp and verify the domain
  2. Select the wallet account you intend to expose
  3. Review account and network requests
  4. Inspect signature details and the target contract
  5. Check token approval target and allowance
  6. Verify transaction or approval state afterward
  7. Disconnect sessions you no longer need

Security

Security comes from repeatable checks, not absolute promises

The user is responsible for safeguarding seed phrases and private keys, and official staff will not request them. Before transferring, signing or approving, treat the network, address, amount, contract target and permission scope as standard review items.

If a site asks for a seed phrase, private key or verification code, stop. On-chain transactions generally cannot be reversed by a wallet alone, so preserving time to check before an irreversible step matters.

Open Security Center
Offline backup and security checklist
✓ Back up the seed phrase offline
✓ Never disclose private keys
✓ Verify network and address
✓ Inspect signature requests
✓ Manage DApp approvals

Academy · Featured beginner guide

What Should You Understand Before Using a Digital Wallet?

An address receives assets; a seed phrase and private key represent control; the network determines where a transaction occurs; gas affects execution cost; and a transaction hash helps you inspect on-chain status. In Web3, DApp connection, signing and token approval are separate actions.

Learning these concepts before the first receive or send transaction makes it easier to notice network mismatches, address errors or unexpected permission requests.

Read the beginner guide →

Ethereum & PoS

Understand staking from both mechanics and risk

Ethereum Staking Basics

Ethereum PoS uses validators in network consensus. Understanding reward sources, network state, withdrawals and exits helps explain how staking services work.

Read staking basics →

Know this before participating

Rewards can change, exits may involve waiting periods, validators can face network penalties, smart contracts introduce technical risk and digital-asset prices can fluctuate. Staking does not guarantee returns.

Learn PoS & validators →

Updates

Product, network and security notices

View all →
Recent Update

Network-first transaction checks

Put network verification before address and asset checks when preparing a transfer or DApp action.

View
Security Notice

Never provide a seed phrase or private key

Fake support, impersonation pages and remote-control requests may try to obtain wallet control.

View
Product Notice

Review DApp approvals independently

After connecting an account, each signature and token approval still requires its own target and scope check.

View
Service

Staking content focuses on mechanism and risk

No fixed yield, principal guarantee or guaranteed-return claims are made.

View

FAQ

Answers to questions that affect real decisions

No. Users safeguard seed phrases and private keys themselves, and official staff will not ask for them.

At minimum, verify the destination address, network, asset, amount and available network fee.

Connection and signing are separate actions. Review every signature or approval independently.

On the relevant block explorer it can show status, block inclusion, confirmations and related addresses.

Not necessarily. Cross-layer movement may require a specific bridge or transfer route.

No. Rewards, network conditions, waiting periods, penalties and market prices can all change.

View full FAQ →

imtoken

Understand first, then act on-chain

Download access, learning resources and security guidance stay within one clear path.

Download imtoken