Multi-chain assets
The same asset name may exist on different networks. Check the network, contract address and receiving support before moving assets.
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
Learn how multi-chain assets, network selection, sending and receiving, DApp connections, approvals, blockchain networks and wallet security fit together. imtoken focuses on the checks that matter before you submit an on-chain action.
01Create a Wallet
Start from a trusted entry point and understand what keys and addresses a new wallet creates.
View steps →02Back Up a Wallet
Keep the seed phrase offline and out of chats, email and screenshots.
Backup principles →03Receive Assets
Check both the receiving address and network, not just the address text.
Receive safely →04Send Assets
Review the address, network, amount and gas before submitting.
Send safely →05Connect to a DApp
Review every signature, approval and contract request after connecting.
Connect safely →A wallet is more than a balance screen
Real wallet use connects keys, addresses, networks, transactions, approvals and applications. Each capability is presented differently so you can understand what is being verified on-chain, not merely what appears in an interface.
Send & Receive
Receiving addresses, network choice, amounts, gas and transaction hashes form one verifiable on-chain flow.
See the full flow →imtoken App
Use the mobile wallet to review assets, manage networks, inspect transaction history and enter Web3 scenarios.
imtoken Web and wallet security
Browser connections require careful domain, approval-target and session review. Seed phrases and private keys should remain offline and should not be entered into third-party websites.
Web guide · Security centerKeep keys offline
The way recovery material is protected defines the foundation of account control.
Explore blockchain networks
Network choice is not cosmetic. It determines the gas asset, confirmation rules, contract environment and block explorer.
Multi-chain
Across multiple networks, confirm the network name, gas asset, destination and token contract rather than assuming a similar address means the same network.
Public chains
Nodes receive transactions and participate in block production or validation. Block explorers help verify hashes, heights and confirmation status.
EVM networks
EVM networks often share address and smart-contract patterns, while gas assets, chain IDs and network conditions still differ.
Layer 2
Transfers between a Layer 2 system and its base chain may involve bridges, different confirmation paths and waiting periods.
A six-step path from wallet setup to approval review
01
Get imtoken
Use a trusted entry point and avoid unknown installation files.
02
Create or import a wallet
Know whether you are creating or restoring, and never expose recovery material.
03
Back up offline
Keep the seed phrase offline and away from screenshots, cloud chats and public devices.
04
Select and verify the network
Check the network name, gas asset, address and receiving support.
05
Receive or send assets
Review the destination and network, then keep the transaction hash for verification.
06
Review transactions and approvals
Inspect DApp requests before signing and revisit approvals that are no longer needed.
Web3 & DApps: review every step separately
Connecting a wallet does not mean every later request should be approved. Treat each signature and approval as a separate decision.
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 unused sessions
Never enter a seed phrase, private key or wallet recovery phrase into a website.
Security starts with control of your keys
Wallet security is a set of repeatable habits rather than a single switch. Keep seed phrases and private keys under your control, review addresses, networks and amounts before transfers, understand signature requests and revisit old approvals. Public devices, untrusted networks and remote-control sessions can add risk. Because on-chain transactions usually cannot be reversed by the wallet alone, careful review before submission is the stronger control.
Open the security center →- Back up seed phrases offline
- Never disclose private keys
- Check network and address
- Inspect signing requests
- Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
Addresses are public receiving identifiers; seed phrases and private keys control access; networks determine where a transaction occurs; gas affects execution cost; transaction hashes help verify status; and DApp connections and approvals introduce smart-contract permissions. Understanding these relationships matters more than memorizing interface buttons.
Start learning →Public chains and confirmations
How nodes, blocks and confirmations create a verifiable transaction state.
EVM and smart contracts
Understand addresses, gas, tokens and approvals.
Layer 2 basics
Understand base chains, cross-layer movement and bridges.
DApp approvals and wallet safety
Build a complete review path from connection to revocation.
Ethereum staking basics
Ethereum PoS uses validators to participate in consensus. Reward sources, validator status, withdrawals and exit procedures depend on protocol and network conditions.
Learn Ethereum staking →Understand before participating
Staking does not guarantee returns. Rewards may change, exits may involve waiting, validators can be penalized, smart contracts carry technical risk, digital assets can move in price and third-party services can add their own risks.
Learn PoS & validators →Product and security updates
Recent Update
Wallet workflow guidance
A clearer path across creation, backup, network selection, transactions and approvals.
Security Notice
Watch for requests for seed phrases or private keys
Anyone claiming to provide official support should not request recovery material.
Product Notice
Multi-chain network checks
Expanded guidance on network names, gas assets and block explorers.
Network
Cross-layer transfers may involve waiting
Layer 2 and base-chain movement can use different confirmation and exit paths.
Frequently asked questions
No. Legitimate support should never ask for your seed phrase, private key or verification code.
Review the address, network, asset, amount, gas terms and relevant contract information.
No. Each signature, approval and transaction still needs independent review.
Cross-layer paths can use different confirmation and exit mechanisms depending on the network.
No. Rewards can change and validator, technical, market and third-party service risks may apply.
It can be used to inspect transaction status and confirmations in the corresponding block explorer.
Ready to begin with imtoken?
Understand backup, network and security principles first. Downloads and later actions should always be initiated by you.