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

Use imtoken to learn how to view multi-chain assets, choose networks, send and receive, connect to DApps, review approvals and build safer wallet habits.

Multi-chain AssetsNetwork ChecksDAppApproval ReviewWallet Security
imtoken mobile wallet interface

Start with the task in front of you

Move through the wallet in a practical order. Each task highlights the context that should be checked before you continue.

01

Create a Wallet

Create a new wallet on a trusted device and understand what the seed phrase controls.

Read guide →
02

Back Up a Wallet

Write the seed phrase offline, verify the order and keep it away from screenshots, chat and cloud storage.

Read guide →
03

Receive Assets

Confirm the network and receiving address before sharing it with the sender.

Read guide →
04

Send Assets

Review destination, network, asset, amount and gas before submitting an irreversible transaction.

Read guide →
05

Connect to a DApp

Confirm the domain first, then review account, signature and approval requests one by one.

Read guide →

Wallet capabilities, organized by real use

Assets, transfers, mobile use, browser connections and security each require a different kind of attention.

Multi-chain assets

See balances in network context and verify the chain before acting.

Multi-chain network relationships

Send & receive

Check receiving address, network, amount, gas and transaction hash.

imtoken APP

Mobile access to assets, network management, DApps and transaction history.

imtoken App product view

imtoken Web

Understand browser connections, account requests, approvals and disconnecting.

Wallet security

Keep keys offline and review signatures and permissions before approval.

Offline private key and backup principles

Explore blockchain networks

Move between network concepts while keeping each explanation directly available on the page.

Use multiple networks without mixing them up

Balances and transactions remain network-specific even when an address format looks familiar.

Learn multi-chain basics →
Multi-chain overview

How public chains record transactions

Nodes validate and propagate transactions; blocks and explorers make network state observable.

Public chain nodes and blocks

EVM, gas and contracts

Compatible networks share execution concepts while maintaining independent state and assets.

EVM compatible network concepts

Layer 2 and bridging context

Understand bridge direction, waiting periods and destination-network gas before moving assets.

Layer 2 and bridge relationship

Fees and confirmation states

Gas reflects network execution resources, while confirmations indicate how a transaction is anchored in later blocks.

Understand gas and confirmations →

A six-step wallet path

01

Get imtoken

Use the official download entry and install only from a trusted source.

02

Create or import a wallet

Understand whether you are generating new keys or loading an existing account.

03

Back up offline

Keep the seed phrase offline and never disclose the private key.

04

Choose and verify a network

Match the asset, destination and network before receiving or sending.

05

Receive or send assets

Review address, amount, gas and expected result before submission.

06

Check transactions and approvals

Use the transaction hash and review DApp permissions that are no longer needed.

Connect to Web3 one decision at a time

A wallet connection is only the beginning. Domain checks, account requests, signatures and approvals each deserve their own review.

Web3 & DApp guide →
Connecting a wallet does not mean every signature request should be accepted. Review every signature and approval independently.
Visit the DApp
Confirm the domain
Start connection
Review account request
Check signature or approval
Complete the action
Disconnect unused connections

Security is a repeatable practice

Wallet security depends on self-custody of keys, a trusted device, careful review of requests and an understanding that third-party DApps and contracts can carry risk. Keep the seed phrase and private key offline, reject impersonation, review addresses and networks before transfers, and inspect permission scope before approvals.

Open Security Center →
Wallet key security principles
✓ Back up the seed phrase offline
✓ Never disclose private keys
✓ Verify network and address
✓ Review signature requests
✓ Manage DApp approvals
Academy

What Should You Understand Before Using a Digital Wallet?

Start with the relationship between addresses, seed phrases and private keys, then understand networks, gas and transaction hashes before moving into DApps and approvals.

Read the starter guide →
Layer 2

Layer 2 basics

Learn bridging direction, waiting and destination-network context.

Web3

DApp approvals

Review permission scope and revoke access you no longer need.

Ethereum & PoS

Ethereum Staking Fundamentals

Understand PoS, validators, reward sources, network state, withdrawals and exits without treating variable rewards as a guarantee.

Read staking basics →

Know before participating

Validator penalties, smart-contract risk, exit waiting, market volatility and third-party service risk can all affect the experience.

Learn about validators →

Product & security updates

Recent Update

Wallet usage notes

Review network context and transaction details before acting on a new asset or request.

Product Notice

Connection guidance

Account connection, signatures and approvals are separate decisions.

Security Notice

Protect recovery credentials

Never provide a seed phrase, private key or verification code to anyone.

Network

Confirmation awareness

Use transaction hashes and explorers to verify on-chain status.

Frequently asked questions

A wallet manages the cryptographic keys used to authorize activity for blockchain accounts. Assets remain recorded on their networks rather than being stored inside the interface.

The user should keep them. imtoken personnel will not ask for a seed phrase, private key or verification code, and those credentials should never be sent to another person.

An address can look familiar across compatible networks while balances and contracts remain separate. The sender and receiver should agree on the same network.

Gas measures network execution resources. The actual fee depends on network rules, congestion and the complexity of the transaction or contract call.

It is a public identifier for an on-chain transaction. It can be used with a block explorer to inspect status, addresses, token transfers, gas use and block information.

No. Connection, signatures, token approvals and transactions are separate actions and should be reviewed independently.

It is permission for a specified smart contract to use a token within an allowed scope. Review the contract and amount before approving.

Often yes through an on-chain transaction, but the method and fee depend on the network. Disconnecting a site alone does not necessarily revoke an approval.

View all questions →

Ready to use imtoken?

Use the unified download entry and review the security basics before your first transfer.

Download imtoken