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 & Web3 knowledge

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, receiving and sending, DApp connections, token approvals and wallet security with practical guidance tied to verifiable on-chain behavior.

Multi-chain assetsEVMLayer 2DAppApproval review
imtoken app product interface
01

Create a Wallet

Prepare a private environment before generating or importing wallet credentials.

Read guide →
02

Back Up a Wallet

Keep recovery material offline and separated from day-to-day devices.

Read guide →
03

Receive Assets

Match the receiving address with the exact network and asset.

Read guide →
04

Send Assets

Check address, network, amount and estimated gas before signing.

Read guide →
05

Connect to a DApp

Verify the domain, then review each request separately.

Read guide →

Wallet capabilities, organized by real tasks

Different functions answer different questions: where assets are recorded, how transfers are signed, how DApps request permissions and how private credentials are protected.

Multi-chain assets

Compare networks, verify addresses and track confirmation status before moving assets.

Multi-chain network illustration

Send & Receive

Review receiving addresses, networks, amounts, gas and transaction hashes as one complete flow.

imtoken APP

Mobile asset viewing, network management, transaction history and DApp access.

imtoken App

imtoken Web

Treat account requests, signatures, approvals and disconnect actions as separate decisions.

Wallet security

Keep seed phrases and private keys under your control and review every approval.

Explore blockchain networks

Understand multi-chain, public-chain, EVM, Layer 2, gas and confirmation concepts in context.

Network matching comes first

Each blockchain network maintains its own nodes, blocks and state. Even when two networks share a similar address format, their asset records and fee systems remain separate, which is why network selection must be verified before sending funds.

Multi-chain

How public chains confirm activity

Nodes propagate transactions, blocks record state changes and later blocks build confirmations.

Public chain

EVM addresses, gas and contracts

EVM-compatible networks can share address patterns while maintaining separate state and fee markets.

EVM

Layer 2 and settlement

Cross-layer transfers can involve bridging, additional confirmations and waiting.

Layer 2

Fees and confirmations change

Gas or network fees compensate the network for processing and recording activity. The amount can vary with congestion, execution complexity and available block space, so a fee observed at one moment should never be treated as a permanent rate.

Gas

A practical wallet path

Move through creation, backup, network checks, transfers and approval review in a sequence that keeps sensitive credentials protected.

01

Get imtoken

Keep each step verifiable before moving on.

02

Create or import a wallet

Keep each step verifiable before moving on.

03

Back up the wallet offline

Keep each step verifiable before moving on.

04

Choose and verify the network

Keep each step verifiable before moving on.

05

Receive or send assets

Keep each step verifiable before moving on.

06

Review transactions and approvals

Keep each step verifiable before moving on.

Web3

Connect to DApps one decision at a time

Connecting to a DApp creates an interaction channel and may reveal selected account information, but it is not blanket approval for every future request. Each signature, transaction or approval still needs its own review.

Open the Web3 guide →
01
Visit the DApp
Start from the intended domain.
02
Confirm the domain
Watch for spelling differences and imitation pages.
03
Start connection
Review which account information is requested.
04
Review account request
Connection is not blanket signing permission.
05
Check signature or approval
Read the request, spender and amount.
06
Complete the action
Keep the transaction hash when one is created.
07
Disconnect when finished
Remove sessions and review old approvals.
Connecting a wallet does not mean you should approve every signature. Review every signature and approval independently.

Security

Protect credentials first, then verify every action

Pre-transaction checks are more effective than trying to reverse an error after confirmation. Blockchain transfers are generally irreversible by the wallet alone, and third-party DApps and smart contracts can introduce independent risks that must be assessed separately.

Open Security Center →
Security
  • Back up seed phrases offline
  • Never disclose private keys
  • Verify network and address
  • Review signature requests
  • Manage DApp approvals

Academy · Getting Started

What Should You Understand Before Using a Digital Wallet?

The most useful way to learn wallet operations is to follow the order in which concepts appear in real use: understand addresses and keys first, then networks and fees, then receiving, sending and transaction verification.

Read the starter guide →
Networks

Public chains and confirmations

Nodes, blocks and explorers help verify finality.

EVM

EVM and smart contracts

Understand gas, contracts and token interaction.

Layer 2

Layer 2 fundamentals

Learn settlement relationships and bridging.

Web3

DApp approvals

Treat connections, signatures and approvals separately.

Security

Wallet security

Protect credentials and reduce exposure.

Glossary

Blockchain glossary

Look up common terms in plain language.

Ethereum and Proof of Stake

Understand validators, reward sources, exits and network penalties before deciding whether staking fits your circumstances.

Ethereum Staking Basics

Proof of Stake and validator participation involve network state, reward distribution, exit mechanics and possible penalties. The mechanics should be understood before considering returns because reward levels and queue times can change with network conditions.

Learn staking mechanics →

What to Understand Before Participating

Staking does not guarantee returns, and digital asset prices can move independently of staking rewards. Validators may face network penalties, while smart contracts and third-party services introduce additional technical and operational risks.

Validator guide →

Product and security updates

Updates are presented by topic without inventing dates, partnerships or market claims.

Recent Update

Wallet guidance refreshed

Wallet operations are organized around real tasks.

Network Notice

Network checks emphasized

Verify network and address before transfers.

Security Notice

Credential safety reminder

Never share seed phrases, private keys or verification codes.

Product Notice

PoS knowledge updated

Validator content emphasizes variable rewards and risks.

Frequently asked questions

Short answers to common wallet, network, Web3, security and staking questions.

An address is a public identifier used to receive assets on a specific network. It is not a seed phrase or private key.

Networks maintain separate state, so an address that looks valid can still be used on the wrong network.

Gas is the network fee for processing an on-chain action and can vary with network conditions.

No. Connection, signatures, transactions and approvals are separate requests.

No. Private keys and seed phrases remain under user control and should never be sent to support staff.

No. Rewards can change, exits may involve waits and validators, contracts and asset prices all carry risk.

View all FAQs →

Ready to continue?

Use the unified download entry. Never provide a seed phrase, private key or verification code during setup.

Download imtoken