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 digital wallet

Manage Multi-chain Assets and Connect to Web3 with Clarity

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

Use imtoken to understand the practical path from viewing multi-chain assets to choosing the correct network, receiving and sending assets, connecting to DApps, reviewing signatures and approvals, and checking transaction status. The surrounding guides explain why network selection matters and how to keep wallet secrets, permissions and transaction details under your control.

Multi-chain assetsNetwork selectionSend & receiveDAppsApproval reviewWallet security
imtoken mobile wallet product preview
01

Create a Wallet

Learn what an address, seed phrase and private key represent before creating or importing a wallet.

Start here →
02

Back Up a Wallet

Keep recovery material offline, private and readable so it is not exposed through screenshots or shared storage.

Backup guide →
03

Receive Assets

Confirm the destination network before sharing an address; matching asset names do not guarantee network compatibility.

Receiving checks →
04

Send Assets

Review the destination address, network, amount and network fee before approving a transfer.

Transfer checks →
05

Connect to a DApp

Verify the domain and account request, then inspect every signature and token approval as a separate decision.

Connection guide →

Wallet capabilities

From asset visibility to Web3 interaction

Wallet tasks are easier to reason about when the network, account, transaction and permission are treated as separate pieces of information.

Multi-chain assets

Keep assets from different networks distinct. Confirm the selected network, verify the receiving address and interpret transaction status in the context of that network.

imtoken App

Use the mobile wallet to inspect assets, manage network choices, review transaction records and evaluate DApp requests before acting.

imtoken mobile wallet interface for assets and network management

Send & receive

For receiving, match the address with the intended network. For sending, check the amount and gas, then use the transaction hash to follow confirmation progress.

imtoken Web

Browser-based Web3 activity requires attention to the site domain, connection scope, signatures, approvals and the point at which a session should be disconnected.

Wallet security

Your seed phrase and private key are your responsibility to protect. imtoken personnel will not ask for them or for a verification code.

Blockchain networks

Understand the network before interpreting a transaction

Public chains, EVM networks, Layer 2 systems and gas each describe a different part of how transactions are executed and confirmed.

Multi-chain networks

Assets, fees and transaction state belong to a specific network. Similar address formats do not make assets automatically portable between chains.

Continue reading →
Diagram of multiple blockchain networks

Public chains

Nodes propagate transactions, blocks record state changes, and confirmations help users understand how far a transaction has progressed.

Continue reading →
Public blockchain and block connection diagram

EVM networks

EVM-compatible networks can share familiar address and contract concepts while maintaining independent gas assets, contracts and state.

Continue reading →
EVM-compatible network diagram

Layer 2

Layer 2 systems process activity with a defined relationship to a base layer. Moving assets across layers may require a bridge and separate confirmation stages.

Continue reading →
Layer 2 relationship diagram

Gas & confirmations

Gas pays for network execution. A submitted transaction receives a hash, and later confirmations provide evidence that the network has incorporated it into chain history.

Continue reading →

Using your wallet

A six-step path from setup to ongoing checks

Each step carries a specific security decision. Avoid treating setup, transfer and DApp permissions as one undifferentiated action.

  1. 01

    Get imtoken

    Use the download entry on this site and review what you are opening before proceeding.

  2. 02

    Create or import a wallet

    Understand which information is public and which recovery material must remain private.

  3. 03

    Back up the wallet offline

    Keep the seed phrase offline and never disclose a private key to another person or service.

  4. 04

    Select and verify the network

    Match the network to the intended asset route and check address compatibility before a transfer.

  5. 05

    Receive or send assets

    Before sending, verify the address, network, amount and fee. Consider a small test when the situation warrants it.

  6. 06

    Review transactions and approvals

    Check transaction hashes, inspect DApp signing requests and periodically remove approvals that are no longer needed.

Web3 & DApps

Connection is only the beginning of the decision process

Connecting a wallet can expose an account to a DApp interface, but it does not mean every later signature or approval should be accepted. Treat each request as a separate action with its own domain, account, contract, amount and permission context.

Explore the Web3 guide →
Visit the DAppVerify the domainStart connectionReview account requestInspect signature or approvalComplete the intended actionDisconnect unused sessions

Security

Protect secrets first, then verify every transaction and permission

A wallet cannot reverse ordinary on-chain transactions on its own. That makes preparation important: store seed phrases and private keys privately, check the destination address and network before transfers, verify DApp domains and contract requests, and review approval scope before authorizing access. Third-party DApps and smart contracts can carry independent risks, so permissions should be limited to what is actually required and removed when they are no longer useful.

Public computers, shared devices, public Wi-Fi, remote-control software, clipboard manipulation and fake support contacts can all increase exposure. imtoken personnel will never ask for your seed phrase, private key or verification code.

Open the Security Center →
Offline private-key protection illustration
  • Back up seed phrases offline
  • Never disclose private keys
  • Verify network and address
  • Inspect every signing request
  • Manage and revoke DApp approvals

Academy · Getting Started

What Should You Understand Before Using a Digital Wallet?

A wallet address can be shared for receiving assets, while a seed phrase and private key are secrets that control access and recovery. The selected blockchain network determines where a transaction is sent, gas pays for execution, and the transaction hash gives you a reference for checking confirmation status. When a DApp asks to connect, sign or approve a token, read the request before acting rather than assuming it is routine.

These concepts form a practical sequence: identify the network, confirm the account, understand what the request changes, and preserve recovery information offline. Learning them before moving assets makes later troubleshooting easier.

Read the getting-started guide →

Ethereum & PoS

Ethereum Staking Fundamentals

Ethereum uses proof of stake and validators to participate in network consensus. Staking rewards can come from protocol activity, while validator status, withdrawal mechanics and exit queues affect how participation works over time. Rewards are not guaranteed and can change with network conditions.

Learn about Ethereum staking →

Updates

Product, network and security information

View all updates →
Recent Update · Product

Wallet-use guidance and navigation have been organized around common tasks

Start from setup, transfers, DApp use or security and follow the related learning path.

Security Notice

Never share a seed phrase, private key or verification code

Anyone requesting those secrets should be treated as a risk, regardless of how the request is presented.

Product Notice

Check network, address and amount before sending

On-chain transfers are generally not reversible by a wallet provider once confirmed by the network.

Network · Recent Update

Use the transaction hash to examine confirmation progress

A transaction hash provides a network-specific reference for checking status through an appropriate block explorer.

FAQ

Common wallet and Web3 questions

Short answers to practical questions, with a full FAQ covering wallet secrets, networks, gas, DApps, EVM, Layer 2, Ethereum PoS and validators.

Open the full FAQ →
What is the difference between an address and a private key?

An address is used to receive assets and can be shared when appropriate. A private key controls access and must remain secret.

Why does network selection matter?

Assets and transaction state belong to a specific network. Sending through the wrong route can produce an unintended result.

What is gas?

Gas is the execution fee required by a blockchain network for a transaction or smart-contract operation.

Does connecting a DApp approve every action?

No. Connection, signatures and token approvals are separate requests and should each be reviewed.

Can imtoken recover my private key?

No. Private keys and seed phrases are kept by the user; official personnel will not ask you to send them.

Does staking guarantee a return?

No. Rewards may change, exit can involve waiting, validators can face penalties, and asset prices can fluctuate.

imtoken

Continue with a clearer understanding of networks, permissions and wallet security

Use the official download entry, then follow the getting-started and security guides before moving assets or authorizing a DApp.

Download imtoken