Multi-chain assets
Each blockchain has its own network state, gas model and contract deployments. When checking an asset, review its network and contract context as well as the token name.
Understand 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
Move from multi-chain assets and network selection to sending, receiving, DApp connections, token approvals and wallet security in one coherent workflow. Every transfer, signature and approval deserves a review of the address, network and request details before you proceed.
Common tasks
Start with what you need to do right now
- 01
Create a Wallet
Understand what a seed phrase and a private key control before creating a new blockchain account.
See the steps → - 02
Back Up a Wallet
Keep recovery information offline and avoid screenshots, cloud sync and chat messages for sensitive data.
Backup principles → - 03
Receive Assets
Verify the address and network together rather than checking only a few visible characters.
Receiving guide → - 04
Send Assets
Review the address, network, amount and gas, then use the transaction hash to check the result.
Transfer checks → - 05
Connect to a DApp
A connection is not blanket consent. Review every later signature and approval independently.
Connection guide →
Wallet capabilities
View assets, networks, transactions and security as one operating context
Send & receive
Receiving starts with the address and network. Sending adds amount, gas and post-transaction verification through the transaction hash.
Review the transfer flow →imtoken App
Review assets, switch networks, prepare transactions and access DApps on mobile while keeping the device and network environment trustworthy.
imtoken Web
Browser use centers on account requests, domain checks, approval review and disconnecting sessions you no longer need.
Explore web connections →
Wallet security
Seed phrases and private keys remain under the user’s control. Official staff will not ask for them or for a verification code.
Open the security center →Multi-chain does not mean every asset lives on the same chain
Matching token names do not imply matching network state. Verify the source network, destination network and address support before moving assets.
Multi-chain guide →
Public chains are maintained through nodes, blocks and consensus
Understanding broadcast, inclusion and confirmation helps separate “submitted by the wallet” from “confirmed by the network.”
Public chain basics →
EVM networks can share tooling while remaining separate networks
Similar address formats do not make assets automatically interchangeable. Gas assets, contract addresses and network parameters still need separate checks.
EVM guide →
Layer 2 requires an understanding of both mainnet and cross-layer paths
Moving assets can involve bridges, waiting periods and multiple confirmation stages. A balance change alone may not describe final settlement.
Layer 2 basics →Gas→Broadcast→Block→Confirm
Gas and confirmation describe different parts of transaction status
Fees influence processing conditions, while confirmations describe where the transaction sits in network history. Use the transaction hash and network state when troubleshooting.
Gas & confirmations →Wallet journey
Six steps for a repeatable operating habit
- 01
Get imtoken
Use the website download entry point intentionally and avoid installation files from unknown sources.
- 02
Create or import a wallet
Know whether you are creating a new account or restoring an existing one, and never submit a seed phrase to a web form.
- 03
Back up offline
Keep recovery information offline rather than leaving long-lived screenshots or chat copies.
- 04
Select and verify the network
Check the network name, gas asset, address and application support before acting.
- 05
Receive or send assets
Verify address, network and amount before sending; a small test can be useful when uncertainty remains.
- 06
Review transactions and approvals
Use the transaction hash to inspect results and periodically review DApp permissions you no longer need.
Web3 & DApps
Connecting a wallet is only the beginning; every signature and approval deserves its own review
Check the full DApp domain before connecting. Once connected, examine account requests and treat message signatures, transaction signatures and token approvals as distinct actions with different consequences.
Security note
Open the Web3 guide →Connecting a wallet does not mean every signature request should be accepted. Review every signature and approval independently.
- Visit the DApp
- Verify the domain
- Start the connection
- Review the account request
- Check the signature or approval
- Complete the action
- Disconnect unused sessions
Security
Make “review first, sign second” a normal habit
Wallet security goes beyond protecting one password. Seed phrases and private keys control accounts, DApp approvals can leave long-lived permissions, and phishing pages or fake support messages often rely on urgency. Use one process that includes offline backup, domain verification, approval review, address and network checks, and a trusted device environment. imtoken staff will not ask for a seed phrase, private key or verification code and cannot restore a user’s private key. Because on-chain transactions generally cannot be reversed by a wallet alone, the most important checks happen before signing or sending.
Open the security center →- Back up seed phrases offline
- Never disclose private keys
- Verify the network and address
- Inspect signature requests
- Manage DApp approvals
Academy
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases and private keys, then add networks, gas, transaction hashes, DApps and approvals. Learning them in the same order that real actions happen makes it easier to know when to check a network, when to inspect a permission and when to stop.
Start learning →Network basicsPublic chains & confirmationsNodes, blocks, broadcast and confirmation stateSmart contractsEVM & smart contractsAddresses, gas, calls and tokensScalingLayer 2 basicsMainnet links, bridges and cross-layer statusWeb3DApp approvalsSpenders, allowance limits and revocationSecurityWallet securityKeys, phishing, devices and transaction checksGlossaryBlockchain glossaryQuick explanations of common terms
Ethereum & PoS
Ethereum Staking Basics
Learn Ethereum PoS, validator duties, reward sources, network status, withdrawals and exits. Staking does not guarantee returns; rewards can change and exits can involve waiting.
Staking basics →Understand before participating
- Validators can face network penalties
- Exits and withdrawals may involve waiting
- Smart contracts carry technical risk
- Digital-asset prices can move materially
- Third-party services add separate risk
Product & security updates
Recent notes and risk reminders
Product · Recent UpdateWallet and network knowledge structure improvedNetwork · Network NoticeRecheck gas and the receiving network before cross-network actionsSecurity · Security NoticeBe cautious of any request for a seed phrase or private keyService · Product NoticeDownloads continue to require an intentional clickSecurity · Recent UpdateReview DApp approvals you no longer need
FAQ
Common questions
Can I give a seed phrase to official support for recovery?
No. Seed phrases and private keys should stay under the user’s control, and official staff will not ask for them.
What should I verify before sending?
At minimum, review the complete address, destination network, amount and gas, and make sure the action matches your intent.
Can I sign immediately after connecting to a DApp?
No. A connection only establishes interaction. Every later signature, transaction and approval request should be reviewed separately.
What can a transaction hash tell me?
It lets you inspect whether a transaction was broadcast, confirmed, failed or is still pending on the relevant network.
Is Layer 2 the same network as mainnet?
No. Layer 2 systems use specific settlement or bridging mechanisms, so transfers and confirmations follow the rules of the networks involved.
Does staking provide a fixed annual return?
No return is guaranteed. Rewards can change and staking can involve waiting, network penalties, contract risk and asset-price volatility.
imtoken