Multi-chain assets
Networks can differ in assets, gas rules and confirmation timing. Check the network and contract rather than relying on a token name alone.
Understand multi-chain use →
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
Bring multi-chain assets, network selection, sending and receiving, DApp connections, token approvals, network knowledge and wallet security into one practical workflow.
Quick tasks
Start with what you need to do
01Create a WalletUnderstand accounts, networks and backup responsibility before you create one.02Back Up a WalletKeep seed phrases and private keys offline and under your control.03Receive AssetsCheck the receiving address, destination network and asset together.04Send AssetsReview the address, network, amount, gas and request before confirming.05Connect to a DAppContinue reviewing each signature, transaction and approval after connection.
Wallet capabilities
Use one framework for assets, networks, connections and security
imtoken App
Mobile access for network management, asset views, transaction history and DApp use.
Explore the App →Send & receive
- Address
- Check important parts before submitting
- Network
- Confirm both sides expect the same network
- Gas
- Understand fees as network execution costs
- Transaction hash
- Use on-chain records to verify status
imtoken Web
A browser connection does not approve later requests. Account access, signatures, transactions and approvals should be reviewed separately.
Learn about web connections →Wallet security
Keep seed phrases and private keys under your own control. Official personnel will not ask for them or for verification codes.
Visit Security →
Explore blockchain networks
Identify the network before deciding how to move assets
Multi-chain does not merge every asset into one network
Each chain keeps its own state and transaction history. Identify where the asset actually lives and whether the recipient supports that network.
Learn more →
Public network state is collectively maintained
Nodes, blocks, transactions and confirmations create an on-chain history you can independently inspect.
Public chain basics →
EVM compatibility does not make networks identical
Address formats can look similar while network IDs, gas assets, contract deployments and bridge routes differ.
Understand EVM networks →
Cross-layer moves have a source, destination and waiting stage
Layer 2 improves scaling, but bridging still requires careful checks of routes, networks and settlement steps.
Learn Layer 2 →GasExecution cost→BlockNetwork record→ConfirmLater blocks
Fees and confirmations answer different questions
Gas describes execution cost; confirmations describe how a transaction is recorded and followed by later blocks.
Gas & confirmations →Wallet journey
From getting imtoken to reviewing ongoing approvals
- 01
Get imtoken
Use the site download entry and confirm the brand and page source.
- 02
Create or import
Understand recovery credentials and never submit a seed phrase to a website.
- 03
Back up offline
Keep the seed phrase offline and never disclose private keys or verification codes.
- 04
Select and verify a network
Match the destination asset and recipient requirements before proceeding.
- 05
Receive or send assets
Review the amount, gas and destination before sending; confirm the network when receiving.
- 06
Review transactions and approvals
Inspect DApp signatures and remove approvals you no longer need.
Web3 & DApps
A wallet connection is only the first step
The important decisions come after connection: account requests, signatures, token approvals and contract interactions should each match what you intended to do.
Read the full Web3 guide →Visit the DApp↓Confirm the domain↓Start the connection↓Review account requests↓Check signatures or approvals↓Complete the action↓Disconnect unused sessions
Security
Security comes from repeated verification, not absolute promises
A digital wallet gives users direct control over on-chain accounts, which also means key custody and transaction decisions matter. Keep seed phrases and private keys private and preferably offline; verify addresses, networks and amounts before transfers; inspect signatures and approvals after connecting to DApps; and be cautious with shared computers, public networks, remote-control tools and clipboard contents. On-chain transactions generally cannot be reversed by a wallet alone, so the best place for a check is before confirmation.
Visit Security →- Back up seed phrases offline
- Never disclose private keys
- Verify network and address
- Review signature requests
- Manage DApp approvals
Academy · Featured guide
What Should You Understand Before Using a Digital Wallet?
An address receives assets; a seed phrase and private key control accounts; the network determines where a transaction happens; gas pays for execution; a transaction hash lets you verify activity on-chain; and DApps can request connections, signatures and approvals. The relationships between these ideas matter more than memorizing any one term.
Start learning →Public chains & confirmations
Understand transaction state through nodes, blocks and confirmations.
EVM & smart contracts
Learn how addresses, gas, tokens and contracts relate.
Layer 2 basics
Explore base-layer relationships, bridges and arrival stages.
DApp approvals
Review spenders, allowances and permissions you no longer need.
Wallet security
Build habits around keys, devices, transfers and signatures.
Blockchain glossary
Connect common terms to the actions where they matter.
Ethereum & PoS
Ethereum Staking Basics
Ethereum PoS relies on validators for consensus. Rewards come from protocol rules and network activity, while withdrawals, full exits and waiting periods are separate stages to understand.
Learn Ethereum staking →Know the risks before participating
- Validators can face protocol penalties
- Withdrawals and exits may involve waiting
- Smart contracts carry technical risk
- Third-party services have independent risk
- Digital asset prices can fluctuate
Staking does not guarantee returns. Rewards can change, and participation should fit your own circumstances.
PoS & validators →Product & security updates
Notices focused on practical impact
Multi-chain asset display and network checks
Review the active network and contract source instead of relying on a token name alone.
Confirmation timing depends on network state
If activity is delayed, check the transaction hash and block status before trying again.
Signatures and token approvals are separate decisions
A DApp connection does not approve later requests. Review each one individually.
Downloads use one dedicated entry
All download buttons point to the same download page to avoid inconsistent paths.
FAQ
Common questions
Can I send my seed phrase to support for recovery?
No. Keep seed phrases and private keys under your own control. Official personnel will not ask for them.
Should I approve every signature after connecting a DApp?
No. Review the source, content and intended purpose of every signature request.
Why does the network matter for similar asset names?
Assets with similar names can exist on different networks and contracts.
Does a higher gas fee make a transaction safer?
Gas primarily reflects execution cost and network conditions, not a direct measure of safety.
Why can Layer 2 transfers take time?
Cross-layer and settlement flows differ by network and may include waiting stages.
Are staking rewards fixed?
No. Rewards can change with protocol and network conditions and are not guaranteed.
imtoken
Start with a clear first step
Use the dedicated download page and keep verifying networks, addresses and requests. Never send a seed phrase, private key or verification code to anyone.