Multi-chain Assets
Check the network, address context and confirmation state rather than relying only on a token name.
- Assets across networks
- Address and network checks
- Confirmations and block records
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 assets and network selection to sending, receiving, DApp connections and approval management, imtoken brings wallet use and on-chain knowledge into one clear path. Learn how networks differ, how to review transactions and gas, and how seed phrases, private keys and approval security fit into every action.
Start with the task you need to do
Common wallet tasks are separated into a real workflow: understand the action, perform it, and then verify the result.
01
Create a Wallet
Understand addresses, seed phrases and private keys before creating a wallet.
Learn the basics →02
Back Up a Wallet
Keep recovery information offline, avoid screenshots, and never send it to anyone.
Backup principles →04
Send Assets
Review address, network, amount and gas, then keep the transaction hash.
Transfer checks →Wallet capabilities organized by real use cases
Assets, transactions, mobile use, browser connections and security are related, but they are not the same decision.
Send & Receive
Address, network, amount, gas and transaction hash form a complete verification path.
See the full flow →imtoken App
For mobile wallet use, network management, asset views, history and DApp access.
imtoken Web
Review account requests, DApp origin, signatures and approvals, then disconnect unneeded access.
Explore Web connections →Wallet Security
Seed phrases and private keys remain under the user’s control throughout the wallet lifecycle.
Explore blockchain networks
Public chains, EVM networks and Layer 2 differ in confirmation logic, fees and cross-layer movement.
Multi-chain
A multi-chain wallet works across separate blockchain environments. Verify the network, address, asset contract and expected delivery path.
Learn more →
Public Chains
Nodes propagate transactions, blocks record state, and block explorers help verify hashes, heights and execution results.
Understand public chains →
EVM Networks
EVM-compatible networks may use similar address formats while maintaining independent gas, network IDs, contracts and asset states.
Explore EVM →
Layer 2
Cross-layer movement can involve bridges, waiting periods and different confirmation rules.
Explore Layer 2 →Gas & Confirmations
Gas reflects execution resources on-chain. Use the transaction hash, status and confirmations to determine whether an action is complete.
Read the guide →A six-step wallet path
From getting imtoken to reviewing transactions and approvals, each stage has a practical verification point.
01
Get imtoken
Use the unified download entry.
02
Create or import a wallet
Handle recovery information only in a trusted environment.
03
Back up offline
Keep the seed phrase offline and never disclose a private key.
04
Select and verify the network
Check the asset network, recipient support and gas asset.
05
Receive or send assets
Review address, network and amount, then keep the transaction hash.
06
Review transactions and approvals
Inspect DApp requests before signing and review permissions you no longer need.
Web3 & DApps
Review every connection, signature and approval independently
Connecting a wallet does not mean every later request should be accepted. Separate the domain, account request, signature content and approval target.
Open the Web3 guide- Visit the DApp
- Verify the domain
- Start the connection
- Review account requests
- Inspect the signature or approval
- Complete the action
- Disconnect unneeded access
Safety note: Review each signature and approval separately.
Security
Put security checks inside every on-chain action
Users remain responsible for seed phrases and private keys. DApp approvals need a clear target and permission scope, while transfers require address, network and amount checks together. Confirmed on-chain transactions usually cannot be unilaterally reversed by a wallet, and third-party contracts can introduce independent risks.
Open Security- Back up seed phrases offline
- Never disclose private keys
- Verify network and address
- Review signature requests
- Manage DApp approvals
Academy
Follow a real learning order: wallet concepts, addresses and networks, transactions, DApps, approvals and security management.
What Should You Understand Before Using a Digital Wallet?
An address identifies where assets can be received; seed phrases and private keys relate to recovery and control; the network determines where a transaction executes; gas reflects execution cost; a transaction hash identifies the record; and DApps and approvals introduce third-party contract permissions.
Read the guideEthereum & PoS
Learn staking and validators without guaranteed-return language.
Ethereum Staking Basics
Validators participate in consensus. Reward sources, network state, withdrawals and exit flows are influenced by protocol rules and network conditions.
- Ethereum PoS and validator responsibilities
- Reward sources and variability
- Withdrawal and exit mechanisms
What to understand before participating
Staking does not guarantee returns. Exits may involve waiting, validators can face penalties, smart contracts and third-party services can introduce technical risk, and digital asset prices can move materially.
- Validator status and penalties
- Waiting periods and service fees
- Contract, market and third-party risk
Product and security updates
No invented dates, partnerships, financing or market rankings.
Recent Update
Multi-chain network review flow
Check network, address and asset state when sending or receiving.
Security Notice
Review signatures and approvals one by one
A DApp connection does not remove the need to review each request.
Network
Confirm the destination chain before cross-network movement
Bridge and Layer 2 flows can use different confirmation timing.
Frequently asked questions
The complete FAQ covers 16 wallet, network, Web3, security and PoS topics.
A digital wallet helps manage blockchain addresses, signing permissions and asset views. The interface does not physically store on-chain assets; it helps users interact with networks using keys they control.
Both are highly sensitive recovery or control information. Generation methods vary, but the practical rule is the same: keep them under your control, back them up offline, and never send them to anyone.
An asset with the same name may exist on different networks. Whether the recipient supports the selected network affects delivery and recovery options, so verify network, address and amount together.
Gas measures computation or transaction usage on a blockchain. Actual fees depend on the network mechanism and current demand, so unexpected changes should prompt a review of the network and transaction details.
A transaction hash is a key identifier for finding an on-chain record. On the correct block explorer, it can show status, block height, sender, recipient and execution result.
No. A connection normally establishes an account interaction. Signatures, transactions and approvals should still be reviewed separately, and a connected DApp should not be treated as automatically trustworthy.
Ready to use imtoken
The unified download entry is /download.html. Keep reviewing every transfer, signature and approval before confirming.