Multi-chain assets
Different networks can represent assets independently. Confirm the network, address and transaction state before moving value.
- Network differences
- Address checks
- Transaction confirmations
Multi-chain wallet · Networks · Web3
Manage Multi-chain Assets and Connect to Web3 with Clarity
A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken
View assets across supported networks, check receiving and sending details, understand gas and transaction history, connect to DApps deliberately, and review every signature or approval with security in mind.
Start with the task in front of you
Five common wallet tasks
Each action has a different review point. Move through them deliberately instead of treating every prompt as routine.
01
Create a Wallet
Start with a trusted device, understand what recovery material controls, and record it offline.
Learn more →02
Back Up a Wallet
Keep recovery material offline and never send it through chat, email or support forms.
Learn more →03
Receive Assets
Match the receiving address with the intended network and asset before sharing it.
Learn more →05
Connect to a DApp
Verify the domain and review each account, signature and approval request separately.
Learn more →Wallet capabilities
A clearer way to manage assets and permissions
Understand the network first, then the asset, transaction and third-party request.
imtoken APP
View assets, switch networks, review transaction history and connect to DApps from a mobile workflow.
Send & receive
Check the receiving address, selected network, amount, gas and transaction hash as one continuous workflow.
Transfer guide →imtoken Web
Browser connections should be deliberate. Review the requested account, approval scope and when to disconnect.
Understand Web access →Wallet security
Keep seed phrases and private keys private, offline and outside third-party support flows.
Blockchain networks
Explore networks by the decision you need to make
The same-looking address can exist across different contexts. Network identity and public state matter.
Multi-chain
Different networks maintain independent state. Match the asset, address and selected network before moving value.
Understand this network concept →Public Chains
Nodes publish and verify transactions in blocks, making status and confirmations independently checkable.
Understand this network concept →
EVM
EVM networks can share address conventions while keeping separate balances, gas and contract state.
Understand this network concept →
Layer 2
Layer 2 systems add execution capacity while maintaining defined relationships with their base layer.
Understand this network concept →
Gas & Confirmations
Fees and confirmation timing depend on the selected network, transaction demand and protocol rules.
Understand this network concept →Wallet journey
Six steps from setup to review
Keep recovery material offline, verify the network before sending, and review DApp requests one by one.
Get imtoken
Use the official download entry and keep recovery material private.
01
Create or import
Understand whether you are creating new keys or importing existing recovery material.
02
Back up offline
Store the seed phrase offline and never disclose a private key.
03
Choose the network
Match the network to the asset and destination before moving funds.
04
Receive or send
Review the address, amount and gas before signing.
05
Review activity
Check transaction hashes and remove permissions you no longer need.
06
Web3 & DApp
A connection is the start of review, not the end
Connecting a wallet does not mean every signature or approval should be accepted. Treat each request as a new decision.
Verify the domain first. Then review the account request, signature content, approval target and permission scope.
- Visit the DApp
- Verify the domain
- Start the connection
- Review account requests
- Check signatures or approvals
- Complete the intended action
- Disconnect unused sessions
Security
Security is a repeatable set of checks
Protect recovery material, review transaction details, keep devices trustworthy and treat third-party permissions as separate decisions. Seed phrases and private keys remain under the user’s control; official personnel will not ask for them. On-chain transactions generally cannot be reversed by a wallet provider, and third-party DApps or smart contracts may contain technical or fraudulent risk.
Open the security center →- Back up the seed phrase offline
- Never disclose a private key
- Verify the network and address
- Review every signing request
- Manage DApp approvals
Academy
Learn in the order you actually use a wallet
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases, private keys and networks, then add gas, transaction hashes, DApps and approvals. The goal is to know which prompts can change on-chain state and which information must remain private.
Read the guide →Guide
Public chains and confirmations
How blocks and confirmations create a public transaction history.
Guide
EVM and smart contracts
Why compatible networks still keep separate state.
Guide
Layer 2 basics
How base-layer relationships affect transfers.
Guide
DApp approvals
Why permission scope matters after connection.
Guide
Wallet security
Protect recovery material and verify every action.
Guide
Blockchain glossary
Build a practical vocabulary for wallet use.
Ethereum · PoS
Understand staking before evaluating participation
How Ethereum proof of stake works
Study validators, reward sources, network status, withdrawal mechanics and exit queues without treating rewards as fixed interest.
Staking basics →Risk, waiting periods and validator state
Staking does not guarantee returns. Rewards can change, exits can involve waiting, validators may face penalties, smart contracts carry technical risk and digital asset prices can fluctuate.
PoS & validators →Updates
All updates →Product, network, security and service information
ProductView
Wallet workflow clarification
A clear path for network selection, transfers and transaction review.
NetworkView
Check the network before moving assets
Address compatibility does not mean balances are shared across networks.
SecurityView
Review every approval separately
Connection does not mean every later request should be trusted.
ServiceView
Self-service transaction checks
Use a public transaction hash and the correct network explorer to verify status.
FAQ
View all questions →Common questions before the next action
A wallet manages blockchain accounts and signing authority. Whether you personally control the private keys depends on the product model, so understand custody, recovery and supported networks first.
It is not recommended. Screenshots can be synced to cloud services or exposed to other software. Keep recovery material offline and never send it through chat, email or cloud notes.
Treat the wallet as no longer having a reliable security boundary. Create a new wallet on a trusted device and, if possible, move assets you still control. Do not reuse exposed recovery material.
No. Several EVM networks can use similar address formats while maintaining completely separate state. Always verify both the network and the asset network before sending.
Gas is the fee concept used to account for computation and network resources when transactions or contract calls are processed. The cost can change with network conditions and transaction complexity.
A transaction hash is a public identifier that lets you inspect status, sender, recipient, fees and confirmations on the corresponding network’s block explorer.
Congestion, fee settings, transaction ordering or propagation can affect confirmation. Check the public status on the correct network before submitting duplicate transactions.
Get imtoken
Use the unified download entry. Review the source and keep recovery material private before creating or importing a wallet.