Multi-chain assets
The same asset can exist on multiple networks. Confirm the network before checking balances, addresses and confirmations.
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, network selection and transfers to DApp connections, approvals, network concepts and wallet security, imtoken organizes each on-chain action into steps you can verify.
Multi-chain assetsNetwork checksDApp approvalsWallet security
Quick tasks
Start with the task in front of you
You do not need to read everything first. Choose your current task and move through preparation, action and verification.
01
Create a Wallet
Know the difference between creating and importing, and decide how you will back up first.
Create a wallet02
Back Up a Wallet
Keep the seed phrase offline; avoid screenshots, chats and casual cloud storage.
Backup principles03
Receive Assets
Confirm the asset network before copying an address and coordinate with the sender.
Receiving steps05
Connect to a DApp
Verify the domain, account request and later signatures; a connection is not automatic approval.
Connection guideWallet capabilities
Put assets, networks and security into one workflow
Each capability is presented in the format best suited to the checks that matter.
Send & Receive
For receiving, check the address and network. For sending, also review the amount, gas and transaction hash.
View the full workflowimtoken APP
View assets, manage networks, follow transaction history and access Web3 on mobile.
imtoken Web
Browser connections should follow verify site → select account → review request → disconnect when done. Do not treat a connection as a security endorsement.
Understand browser connectionsWallet security
Seed phrases and private keys stay under user custody; official staff should never request them.
Blockchain networks
Choose the network before thinking about fees and finality
Similar-looking addresses do not mean the same chain. The selected network determines where the transaction is broadcast, how fees work and where results are verified.
Multi-chain
Use network names, explorers and token contract information to distinguish networks. Never verify an address by only a few leading characters.
Public Chains
Nodes propagate transactions, blocks record state, and confirmations help indicate how firmly a transaction is recorded.
EVM
EVM networks often use similar address formats, while gas, state, token contracts and approvals remain network-specific.
Layer 2
For cross-layer transfers, verify the entry point, destination network, bridge path and confirmation process.
Gas 与交易确认
Gas prices network execution resources. After broadcast, use the transaction hash on the correct explorer to verify status.
Continue readingUsage path
A six-step wallet workflow with verification points
Each step includes a verification point so network or permission mistakes are caught early.
01
Get imtoken
Use a known entry point for the download page rather than unfamiliar links.
02
Create or import a wallet
Understand the difference between creating and importing, and use a private device environment.
03
Back up offline
Store the seed phrase offline and never reveal private keys or verification codes.
04
Select and verify the network
Confirm the network name, recipient support and the network where the asset exists.
05
Receive or send assets
Check the address, amount and gas; consider a small test when appropriate.
06
Check transactions and approvals
Keep the transaction hash, inspect DApp signing requests and periodically remove stale approvals.
Web3 & DApps
Review every connection, signature and approval separately
A wallet connection is only the first step that lets a DApp request account information or later actions. Message signatures, transactions and token approvals need separate review.
Connecting a wallet does not mean every signing request should be accepted. Review every signature and approval separately.
- Visit the DApp
- Verify the domain
- Start connection
- Review account request
- Inspect signature or approval
- Complete the action
- Disconnect when no longer needed
Security
Control secrets, verify on-chain requests and reduce avoidable risk
Wallet security is a set of habits: keep seed phrases and private keys offline, never expose them in chats or forms, verify signature sources and content, check address/network/amount before sending, review DApp connections and approvals, and use public devices or networks cautiously. Confirmed on-chain transactions generally cannot be reversed by the wallet, and third-party DApps or contracts carry independent risk.
Open Security Center- Back up the seed phrase offline
- Never disclose private keys
- Check network and address
- Review signing requests
- Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases, private keys, networks, gas, transaction hashes, DApp connections and approvals. Understanding how these ideas connect is more useful than memorizing button locations.
Read Getting StartedPublic chains and confirmations
How nodes, blocks and confirmations form verifiable transaction state.
EVM and smart contracts
Understand contract calls, gas, tokens and approvals.
Layer 2 basics
Mainnet relationships, cross-layer transfers and bridge checks.
DApp approvals
Approval targets, limits, revocation and risk review.
Ethereum & PoS
Ethereum Staking Basics
Ethereum PoS uses validators to participate in consensus. Understanding reward sources, validator state, withdrawals and exits helps build a complete risk picture before participation.
Learn Ethereum stakingBefore participating
- Staking does not guarantee returns; rewards may change.
- Exits may involve waiting periods.
- Validators may be subject to network penalties.
- Smart contracts carry technical risk.
- Digital asset prices can fluctuate.
- Third-party services carry independent risks.
Updates
Product, security and network information
No fabricated dates or inflated claims—only changes users need to verify.
Product workflow notes
Actionable checks across creation, backup, transfers, DApps and approvals.
Reconfirm the destination chain before switching networks
Similar addresses do not mean the same network; verify recipient support before cross-network transfers.
Never provide seed phrases or private keys
Official staff should never request recovery secrets through chat, forms or email.
Evaluate third-party services independently
Review status, fees, waiting periods and independent risks before participation.
FAQ
Common questions
Start with the most common network, backup, transfer and approval questions.
Where should I store a seed phrase and private key?
Keep them under your own custody, preferably offline, and never transmit them through chats, email, screenshots or unfamiliar forms.
What should I check before sending?
The full address, destination network, asset type, amount and estimated network fee.
Why do transactions need gas?
Gas is the mechanism used to price network computation and storage; actual fees vary with conditions.
Does connecting a DApp transfer assets?
Connection, signing, transactions and token approvals are separate steps; later requests still require review.
Should token approvals be managed later?
Yes. Know the approval target and limit, and consider revoking permissions you no longer need.
Why do Layer 2 transfers require extra network checks?
Cross-layer transfers may involve bridges, different network states and extra confirmation steps.
Does Ethereum staking guarantee returns?
No. Rewards, waiting periods, penalties, contract risk and asset-price volatility can all affect outcomes.
Get started
Download imtokenUse the official entry point for downloads
Downloads should only begin after your own action. Prepare a secure, private device environment before installation or wallet import.