Multi-chain Assets
Understand network differences, address formats, and confirmations instead of identifying assets by token name alone.
Learn about multi-chain networks →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
From multi-chain asset views, network selection, sending and receiving to DApp connections, signatures, approvals, and network knowledge, imtoken brings wallet use and safety checks into one clear path. Review the address, network, amount, and request details before every sensitive action.
Start with a task
Understand common actions before you execute them
01Create a WalletAfter creation, confirm your backup method and secure the recovery material before using the wallet.→02Back Up a WalletKeep seed phrases and private keys under your control, preferably offline, without screenshots or casual sharing.→03Receive AssetsConfirm the destination network before sharing an address, then verify the incoming transaction on-chain.→04Send AssetsCheck the address, network, asset, amount, and gas. On-chain transactions usually cannot be unilaterally reversed.→05Connect to a DAppA connection only creates an interaction channel; every signature and approval still requires separate review.→
Wallet capabilities
See assets, networks, transactions, and security as one workflow
A wallet interface is the entry point. Reliable use comes from understanding networks, addresses, transaction status, and permissions.
Send & Receive
Receiving addresses, networks, amounts, gas, and transaction hashes form one complete verification chain.
Open the transfer guide →imtoken App
Mobile access for network management, asset views, transaction history, and DApp use.
Explore the App →imtoken Web
Understand browser connections, account requests, approval checks, and disconnecting from services.
View Web guidance →
Wallet Security
Keep seed phrases offline, never disclose private keys, and regularly review DApp approvals you no longer need.
Open Security Center →Blockchain networks
Different networks require different checks
Multi-chain does not mean one network with several names
Each network keeps its own block state, fees, and confirmation process. Confirm the active network before checking addresses and token contracts.
Learn more →
Nodes, blocks, and consensus maintain public chains
After broadcast, a transaction moves through reception, inclusion, and confirmation. A block explorer can independently verify the result.
Understand public chains →
Similar address formats do not mean shared network state
EVM-compatible networks can share a technical model while maintaining separate assets, gas markets, and contract state.
Explore EVM →
Cross-layer transfers need source and destination checks
Bridges, exits, and arrival confirmation may involve several stages. “Submitted” at one stage does not prove the entire flow is complete.
Learn Layer 2 →GASfee · block · confirmation
Gas and confirmations describe different things
Gas reflects network execution cost; confirmations describe how a transaction is recorded and becomes increasingly settled.
Open the gas guide →Wallet journey
Six steps from access to approval review
- 01
Get imtoken
Use the unified download entry and avoid unknown installation files from untrusted pages.
- 02
Create or import a wallet
Confirm the account source and never type sensitive recovery data into a routine website flow.
- 03
Back up offline
Protect the seed phrase and never disclose private keys or verification codes.
- 04
Select and verify the network
Match the asset network, address format, and expected fee environment.
- 05
Receive or send assets
Review the address, network, amount, and gas; consider a small test when appropriate.
- 06
Check transactions and approvals
Use the transaction hash to verify results and periodically remove approvals you no longer need.
Web3 & DApps
A connection is only the beginning; every request needs its own decision
Connecting a wallet does not mean you should accept every signature request. Review the domain, account, network, request target, and permission scope each time.
Open the Web3 guide →- Visit a DApp
- Confirm the domain
- Start a connection
- Review the account request
- Check the signature or approval
- Complete the action
- Disconnect unused connections
Security
Safety comes from verification, not absolute claims
Users remain responsible for seed phrases and private keys, and official personnel should never request them. Independently verify transfers, signatures, approvals, unfamiliar links, and support claims. Third-party DApps and smart contracts can carry risk, and on-chain transactions usually cannot be reversed unilaterally by a wallet.
Open Security Center →- Back up seed phrases offline
- Never disclose private keys
- Check network and address
- Review signature requests
- Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
An address receives assets, seed phrases and private keys relate to account control, the network determines where a transaction executes, gas pays network costs, and a transaction hash helps verify the on-chain result. Web3 adds another layer: connections, signatures, and token approvals are different actions and should be reviewed separately.
Read the beginner guide →NetworkPublic Chains & ConfirmationsNodes, blocks, transaction hashes and confirmation flowContractsEVM & Smart ContractsAddresses, gas, tokens and contract interactionsScalingLayer 2 BasicsBase-layer relationships, bridges and arrival checksWeb3DApp ApprovalsSpenders, allowances and revocationSecurityWallet SecurityBackup, phishing, devices and transaction checksGlossaryBlockchain GlossaryQuick definitions for common wallet and network terms
Ethereum Staking Basics
Understand Ethereum PoS, validator responsibilities, reward sources, network status, withdrawal, and exit mechanisms. Staking does not guarantee returns, rewards can change, and exits may involve waiting.
Learn Ethereum staking →Risk and waiting mechanisms
Validators can face network penalties, smart contracts have technical risk, digital assets can be volatile, and third-party services create independent risks. Participation should reflect your own circumstances.
Understand validators →Product & security updates
Recent guidance with content first
Product NoticeHow to use the unified imtoken download entryRead notice →NetworkWhat to check before transferring across networksRead guide →Security NoticeSpot look-alike domains, fake support, and abnormal approvalsRead guide →ServiceUnderstand reward changes and exit waiting before PoS participationRead guide →
FAQ
Frequently Asked Questions
No. Never send a seed phrase, private key, or wallet verification code to anyone.
Similar address formats can exist across networks while asset state remains separate.
It lets you inspect transaction status, block data, fees, and interactions in a block explorer.
No. Connection, signing, and approval are different actions and each request should be reviewed.
No. Rewards can change, exits can involve waiting, and validator or contract risks may apply.
A cross-layer flow can involve a source chain, bridge state, and destination chain.
Usually not. Address, network, and amount checks are especially important before broadcast.
imtoken
Download imtokenStart with a clear process
After download, back up first, then learn the network, transfer, DApp, and approval checks that support safer use.