Multi-chain assets
When viewing assets across networks, distinguish the network, token contract and confirmation state. The same name does not mean the same on-chain asset.
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
From multi-chain assets and network selection to sending, receiving, DApp connections, approvals and wallet security, imtoken brings key actions and on-chain knowledge into one clear path so users can understand what is happening before they sign.
01
Create a Wallet
Start from a trusted entry point and make sure the creation flow never asks you to send a seed phrase to a server.
Read guide →02
Back Up a Wallet
Keep the seed phrase offline and avoid screenshots, cloud sync and messaging apps.
Read guide →03
Receive Assets
Verify the receiving address and network so the sender uses the same chain you selected.
Read guide →04
Send Assets
Before submission, check the address, network, amount and gas, then keep the transaction hash.
Read guide →05
Connect to a DApp
A connection grants account access context; it does not mean every later signature or approval should be accepted.
Read guide →Wallet capabilities built around real tasks
Each capability is organized around how it is actually used, highlighting relationships between assets, networks, transactions, DApps and security instead of repeating identical cards.
Send & receive
Verify the receiving address, network, amount, gas and transaction hash, and understand the full path from signing to confirmation.
View workflow →imtoken APP
View assets, manage networks, review transaction history and connect to DApps when needed.
imtoken Web
Browser connections make domain checks, account requests, signature details and approval targets especially important. Disconnect sessions you no longer use.
Wallet security
Users remain responsible for seed phrases and private keys. Official staff will not request them or ask users to submit them through a website.
Explore blockchain networks
From multi-chain and public chains to EVM, Layer 2, gas and confirmations, understand the network before moving assets.
Keep networks distinct
A multi-chain experience does not merge networks; it keeps each network’s assets, fees and transaction state clearly separated in one interface.
Public chains are maintained by nodes
After broadcast, a transaction must enter blocks and receive confirmations according to that network’s rules. Block explorers help verify public state.
EVM connects addresses, gas and contracts
EVM networks share account and contract concepts, but network IDs, gas assets, deployments and token addresses still need independent checks.
Layer 2 requires cross-layer awareness
Cross-layer transfers may involve bridges, waiting periods and different confirmation logic. Do not infer the network from how an address looks.
Gas & Transaction confirmations
Gas reflects the network cost of execution, while confirmation count reflects how far a transaction has progressed after inclusion in a block. Both may change with congestion.
A practical wallet path
Each step corresponds to information you can verify before taking action.
Get imtoken
Use a confirmed entry point to reach the download page and avoid installation links from unknown sources.
Create or import a wallet
Understand the difference between creation and import, and never submit a seed phrase to a website or chat.
Back up offline
Keep the seed phrase offline and avoid screenshots or cloud sync.
Choose and verify a network
Confirm the asset network, address and network details.
Receive or send assets
Before transferring, check the address, network, amount and gas.
Review transactions and approvals
Use the transaction hash to verify status and periodically review approvals you no longer need.
Web3 & DApp
Review every signature separately
Connecting a wallet does not mean every signature request should be accepted. Verify the domain before visiting a DApp, then review account requests, signature details and approval scope.
Connecting a wallet does not mean you should accept every signature request. Review each signature and approval on its own.
- Visit the DApp
- Verify the domain
- Start a connection
- Review account requests
- Review the signature or approval
- Complete the action
- Disconnect when no longer needed
Security
Put security checks before the action
Seed phrases and private keys remain under the user’s control; official staff will not ask for them. Before transferring, signing or approving, verify the network, address, amount, target and permission scope. Public devices, public Wi‑Fi, remote-control tools, clipboard substitution and lookalike domains can increase risk. Because on-chain transactions generally cannot be reversed by a wallet alone, checking first is the more reliable habit.
Open Security Center- Back up the seed phrase offline
- Never disclose a private key
- Verify network and address
- Review signature requests
- Manage DApp approvals
Academy
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases, private keys, networks, gas, transaction hashes, DApps and approvals before moving real assets. Addresses identify accounts, seed phrases and private keys establish control, the network determines where a transaction executes, and gas plus transaction hashes help explain cost and status. DApps and approvals add a separate permission layer that must be reviewed on its own.
Start learning →Ethereum
Ethereum Staking Basics
Understand PoS, validators, reward sources, network state, withdrawals and exits. Staking does not guarantee returns, and reward levels or waiting periods may change.
Learn staking mechanics →PoS
What to know before participating
Validators may be subject to network penalties, smart contracts and third-party services involve technical risk, and digital asset prices may fluctuate. Participation should reflect your own circumstances.
Learn about validators →Product and security updates
Content-first updates without invented dates, partnerships, funding or market claims.
Frequently asked questions
Core questions covering wallets, networks, transfers, Web3, security and PoS.
No. Keep seed phrases and private keys under your own control and never send them through a website, chat or other channel.
The same asset name may exist on different networks. Check the destination address, network and amount together before you sign.
Gas represents the network fee concept used to execute transactions or contract operations. The actual cost varies with network conditions and complexity.
A transaction hash is a key identifier for checking on-chain status, block height, network and counterparties in a block explorer.
No. A connection does not authorize every later request. Review each signature, transaction and token approval separately.
Many networks allow you to change or revoke an approval with another on-chain transaction. Verify the contract, network and permission scope first.
Layer 2 systems typically provide different execution and fee characteristics while maintaining a security or settlement relationship with the base layer. Cross-layer transfers require bridge and confirmation checks.
No. Rewards, waiting periods, validator status, penalties, contract risk and asset prices may all change.
Start with clear network and security checks
All download actions go through download.html.
Download imtoken