Multi-chain assets
Assets with the same symbol can exist on different networks, with different contracts, fees and confirmation rules. Start with the network before interpreting a balance.
Understand multi-chain →Official imtoken multi-chain wallet website
Manage Multi-chain Assets and Connect to Web3 with Clarity
A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken
Learn how multi-chain assets, network selection, transfers, DApp connections, approvals, network mechanics and wallet security fit together before you act on-chain.
Start with a task
Focus on the next action you need
01Create a WalletUnderstand creation versus import, then plan an offline backup from the beginning.→02Back Up a WalletKeep the seed phrase offline instead of sending it through screenshots, chat or cloud documents.→03Receive AssetsConfirm the network and receiving address before sharing the public address.→04Send AssetsReview address, network, amount, gas and token contract before signing.→05Connect to a DAppVerify the domain, then review account requests, signatures and approval scope.→
Wallet capabilities
See assets, networks, transactions and security as one operating context
Send & Receive
Check the address and network when receiving; add amount, gas, transaction hash and final confirmation when sending.
Review transfer flow →imtoken App
Manage networks, review balances and transaction history, and read every request before signing on mobile.
Explore the App →imtoken Web
A browser connection is only a session. Each later signature, approval or contract interaction still needs independent review.
Understand Web connections →
Wallet security
Seed phrases and private keys remain under the user's control. Support should never ask for them.
Open Security →Multi-chain
Networks have different fees, confirmation behavior and asset environments. Confirm which network the recipient supports and verify the token contract.
Public Chains
Nodes propagate transactions, blocks record state and explorers let users verify results using public data.
EVM Networks
EVM-compatible networks share familiar address, gas, contract and approval concepts while maintaining separate chain state.
Layer 2
Layer 2 systems settle or anchor to a base chain in different ways, so bridges and cross-layer transfers may introduce extra steps and waiting.
Wallet journey
Build one repeatable process in six steps
- 01
Get imtoken
Use the official download entry rather than copying installation links from unfamiliar pages.
- 02
Create or import
Know whether you are creating a new wallet or restoring an existing one, and handle secrets only on a trusted device.
- 03
Back up offline
Store the seed phrase offline and never reveal private keys or verification codes.
- 04
Select the network
Distinguish public chains, EVM networks and Layer 2 systems, then match the network to the asset contract.
- 05
Receive or send
Review address, network, amount and gas; consider a small test before a larger transfer.
- 06
Review transactions and approvals
Keep transaction hashes, read DApp requests before signing and periodically review permissions you no longer need.
Web3 & DApps
A connection is only the beginning
Keep the context clear from the first visit to completion: verify the domain, account, network, signature text, transaction parameters and approval target.
Connecting a wallet does not mean every signing request should be accepted. Review each signature and approval on its own.
Open the Web3 guide →- Visit a DApp
- Verify the domain
- Start a connection
- Review the account request
- Check the signature or approval
- Complete the intended action
- Disconnect unused sessions
Security
Turn security into repeatable checks
Wallet security does not come from claims of absolute protection. It comes from concrete habits: protecting keys, keeping devices maintained, verifying domains, reading signatures and checking transfers. Seed phrases and private keys remain under the user's control, and confirmed blockchain transactions are generally not something a wallet can unilaterally reverse.
When using a third-party DApp, review the connection, signature, approval and contract action separately. Consider removing approvals that are no longer needed, and be cautious with shared computers, public networks and remote-control sessions.
Open the Security Center →- Back up the seed phrase offline
- Never disclose a private key
- Verify network and address
- Read signing requests
- Manage DApp approvals
Academy
What Should You Understand Before Using a Digital Wallet?
An address identifies an account for receiving assets; seed phrases and private keys control and recover a wallet; the network determines where a transaction occurs; gas prices execution; a transaction hash helps track results; and DApp connections and approvals require independent review.
Start the learning path →LearnPublic chains & confirmationsNodes, blocks and confirmation countsLearnEVM & smart contractsGas, contracts and token approvalsLearnLayer 2 basicsBase-chain relationships, bridges and waitingLearnDApp approvalsTargets, allowance scope and contractsLearnWallet securitySecrets, devices and transaction checksLearnBlockchain glossaryCommon on-chain terms in plain language
Ethereum & PoS
Ethereum Staking Basics
Ethereum PoS uses validators for proposing and attesting to blocks. Rewards follow protocol rules and network activity; withdrawals and exits follow network mechanisms and can be affected by queues or validator state.
Understand Ethereum staking →Product & security updates
Recent notices
ProductHow to interpret networks and asset display in a walletRecent UpdateNetworkPublic information to review when a transaction stays pendingNetwork NoticeSecurityVerify the domain and signing context before connecting to a DAppSecurity NoticeSecurityWhy unused token approvals are worth reviewingSecurity Notice
FAQ
Common questions
Does a wallet store my on-chain assets?
Assets are recorded on blockchain networks; a wallet manages keys and addresses and helps submit transactions.
Can I send my seed phrase to support?
No. Support should never ask for a seed phrase or private key; public addresses and transaction hashes are enough for most troubleshooting.
Does a DApp connection mean I already approved it?
No. Connection, signing, transactions and token approvals are separate actions that should be reviewed independently.
Why does network selection matter?
The same asset symbol can exist on different networks, affecting delivery, fees and how you verify a result.
Can a confirmed transaction be reversed?
A wallet generally cannot unilaterally reverse a valid confirmed transaction, so pre-signing checks matter.
Does staking guarantee a return?
No. Rewards, waiting times, network penalties, contract risk and market prices can all change outcomes.
imtoken
Start with a clear understanding of each wallet action
The download entry leads to the dedicated download page. Verify the source before installation, then prioritize offline backup and network basics.