Multi-chain assets
Different networks have separate states, fee assets and confirmation paths. Verify the network and address context before moving value.
imtoken
Manage Multi-chain Assets and Connect to Web3 with Clarity
A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken
Manage assets across networks, choose the intended chain before sending or receiving, review gas and confirmation details, and connect to DApps with a clear understanding of signatures and approvals. imtoken combines practical wallet guidance with network knowledge and security education so each action can be checked before and after it reaches the blockchain.
Quick paths
Start with the action you want to complete
01Create a Wallet
Understand what a new wallet creates and what you must protect from the first step.
Open guide →02Back Up a WalletKeep recovery information offline and private, then verify that your backup can be understood later.
Open guide →03Receive AssetsConfirm the receiving address and network before sharing payment details.
Open guide →04Send AssetsReview destination, network, amount, gas and transaction details before confirming.
Open guide →05Connect to a DAppVerify the domain, account request, signature and approval scope separately.
Open guide →Wallet capabilities
One wallet workflow, multiple kinds of decisions
Send & receive
Check receiving address, network, amount, gas and transaction hash as a continuous flow.
Read guide →imtoken APP
Manage networks, view assets and review transaction records from a mobile workflow.
imtoken Web
Browser-based connection guidance focuses on account requests, approvals, DApp access and disconnecting sessions you no longer need.
Wallet security
Keep recovery secrets private and review every external request separately.
Understand what changes when the network changes
A multi-chain wallet can present assets from several networks, but each network still has its own ledger state, fee rules and confirmation path. The same-looking address does not merge those networks.
Nodes, blocks and confirmations
Public chains rely on distributed network participants to validate and record state changes. Block explorers help users verify where a transaction was included and how many confirmations followed.
EVM, gas and contract calls
EVM-compatible networks share execution concepts such as contract calls and gas, yet they remain separate networks with separate assets and fee conditions.
Layer 2 and cross-layer movement
Moving between a Layer 2 and its settlement network can involve bridges, waiting periods and different confirmation checkpoints. Read the route before moving assets.
Gas reflects network execution conditions
Fees can change with network demand and transaction complexity. A successful broadcast is not the same as final confirmation, so keep the transaction hash for verification.
Wallet journey
A six-step path from setup to review
- 01
Get imtoken
Use the official download entry and review the product page before installation.
- 02
Create or import a wallet
Understand whether you are creating a new account or restoring an existing one.
- 03
Back up the wallet offline
Keep seed phrases and private keys offline; never send them to another person.
- 04
Choose and verify the network
Confirm the intended network before sharing an address or preparing a transaction.
- 05
Receive or send assets
Review address, network, amount and gas before signing.
- 06
Review transactions and approvals
Keep the transaction hash, check the on-chain result and remove approvals you no longer need.
Web3 & DApp
A connection is only the beginning of the review
Each connection, signature and approval is a separate decision. A connected wallet does not mean every later request should be accepted.
Open the Web3 guide →- Visit the DApp
- Verify the domain
- Start the connection
- Review the account request
- Inspect the signature or approval
- Complete the intended action
- Disconnect unused sessions
Connecting a wallet does not mean you should approve every signature request. Review each signature and approval on its own.
Security
Protect the information that controls the wallet
Seed phrases and private keys should remain under your control. Avoid screenshots and public devices, be cautious with cloud backups, verify domains and transaction details, and treat third-party DApps and smart contracts as independent risk sources. No support process should require you to disclose a seed phrase or private key.
Open Security Center →- Back up seed phrases offline
- Never disclose private keys
- Verify network and address
- Inspect signature requests
- Manage DApp approvals
Academy
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases, private keys and network selection, then move to gas, transaction hashes, DApps and approvals. These concepts form one practical chain of reasoning: identify who controls the wallet, where an action will happen, what it may cost, what permission is being requested and how to verify the final result.
Read the beginner guide →GuidePublic chains & confirmations
Understand the concept, its practical use and what to verify.
GuideEVM & smart contractsUnderstand the concept, its practical use and what to verify.
GuideLayer 2 basicsUnderstand the concept, its practical use and what to verify.
GuideDApp approvalsUnderstand the concept, its practical use and what to verify.
GuideWallet securityUnderstand the concept, its practical use and what to verify.
GuideBlockchain glossaryUnderstand the concept, its practical use and what to verify.
Ethereum
Ethereum Staking Basics
Ethereum uses proof of stake, where validators perform protocol duties and may receive network rewards. Reward levels, validator state, withdrawal mechanics and exit timing can change with network conditions and protocol rules.
Learn staking basics →Updates
Product information, network reminders and security education
Product notice
Review wallet functions and current usage guidance before starting a new workflow.
Network reminder
Network congestion and confirmation timing can change; keep the transaction hash for verification.
Security notice
Seed phrases, private keys and verification codes should never be disclosed to another person.
Service notice
Third-party services can have independent terms, risks and availability conditions.
Approval reminder
Review token allowances periodically and consider revoking permissions you no longer need.
FAQ
Questions worth understanding before you act
What is the imtoken wallet?
imtoken presents multi-chain asset management, network usage, Web3 connections and wallet security knowledge. Users remain responsible for protecting their own seed phrases and private keys.
Where should I store a seed phrase?
Prefer an offline, private and durable backup method. Do not send a seed phrase through chat, email or public cloud documents, and never give it to someone claiming to be support.
How are private keys and seed phrases related?
Both are highly sensitive control credentials. Implementations vary, but the key principle is the same: someone who obtains them may gain control over the corresponding on-chain assets.
Why should I verify the network before sending?
The same asset name can exist on multiple networks and addresses may look similar. A network mismatch can prevent assets from arriving where you expect.
What is gas?
Gas measures the computational resources used by a transaction or smart-contract action. The final fee depends on network rules, transaction complexity and congestion.
What is a transaction hash used for?
A transaction hash is an important on-chain reference that can be used in a block explorer to check status, block data, sender, recipient and execution results.
Why is my transaction waiting for confirmation?
After broadcast, a transaction has to be included by the network and may need additional confirmations. Congestion, fee settings and block timing can affect the wait.
imtoken
Ready to continue?
Use the unified download entry. Review network, address and request details before any transfer, signature or approval.