Multi-chain assets
Identify which network holds an asset and understand how addresses, fees and confirmation status fit together.
Explore networks →imtoken
Manage Multi-chain Assets and Connect to Web3 with Clarity
A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken
imtoken brings multi-chain assets, network selection, transfers, DApp connections, token approvals and wallet security into one clear learning path. The goal is to help users understand what they are confirming before every signature, not simply click through prompts.
Start with a task
Start with the task you need to complete
01Create a Wallet
Use a trusted device and make an offline seed-phrase backup immediately after creation.
→02Back Up a WalletAvoid screenshots and cloud uploads; make sure the backup is readable and stored under your control.
→03Receive AssetsVerify the receiving address, network and token context before sharing an address.
→04Send AssetsConfirm address, network, amount and gas; use a small test first when the transfer is significant.
→05Connect to a DAppVerify the domain and source, then review connection, signature and approval requests independently.
→Wallet capabilities
Connect assets, networks, transactions and security in one workflow
imtoken APP
Review assets, switch networks, inspect transaction history and verify request origins before using DApps.
imtoken Web
Use browser sessions for Web3 access while reviewing account connections, signatures and approval scope independently.
Learn web connections →
Wallet security
Keep seed phrases and private keys under your own control, prefer offline backups and review DApp permissions regularly.
Multi-chain
First determine which chain actually holds the asset
A multi-chain wallet can provide one interface, but the state of each network remains separate. Verify the network, address and contract before switching chains or moving assets.
Read the guide →Public Chains
Use nodes, blocks and confirmations to understand status
Public chains propagate transactions through nodes and record them in blocks. Block height, confirmations and transaction hashes help verify whether a transfer has been recorded.
Read the guide →
EVM
Understand addresses, gas, token contracts and approvals
EVM networks share many execution and address conventions, but each chain maintains separate assets, contracts and fee conditions. Check the token contract and approval spender.
Read the guide →
Layer 2
Scaling networks still have clear boundaries with a base layer
Layer 2 systems may rely on a base network for settlement or data availability. Deposits and withdrawals can involve extra steps and waiting periods.
Read the guide →
Gas & Confirmations
Fees and confirmation speed change with network conditions
Gas reflects execution resources, while congestion and complexity influence the fee. After broadcast, use a transaction hash to verify the actual result.
Read the guide →Wallet journey
From setup to transaction and approval checks, every step can be verified
- 01
Get imtoken
Use the official download entry rather than a link from an unsolicited message or ad.
- 02
Create or import a wallet
Avoid public computers and remote-control environments when creating or importing a wallet.
- 03
Back up the wallet offline
Keep seed phrases and private keys offline; do not screenshot, upload or send them to anyone.
- 04
Choose and verify the network
Select the network where the asset actually exists and verify the address, token and chain.
- 05
Receive or send assets
Check the destination, amount, gas and network. A small test can reduce mistakes before a large transfer.
- 06
Check transactions and approvals
Keep the transaction hash, review confirmations, and periodically remove DApp permissions you no longer need.
Web3 & DApp
A connection is only the beginning; signatures and approvals need separate review
A DApp may first request an account connection and later ask for a message signature, transaction signature or token approval. Treating each action separately helps prevent "connected" from becoming a blanket permission for everything that follows.
Open the Web3 guide →1
Open the DApp and verify the domain
2
Check the source before connecting
3
Review the account connection request
4
Distinguish message and transaction signatures
5
Check token approval spender and amount
6
Verify the on-chain result after the action
7
Disconnect sessions you no longer need
Security
Wallet security comes from repeatable checks, not absolute promises
Good wallet security reduces key exposure, verifies destinations, reads signing requests and removes permissions that are no longer needed. imtoken will never ask for your seed phrase, private key or verification code. Blockchain transactions are generally not reversible by a wallet provider, so a stable pre-signing checklist matters more than post-event promises. Third-party DApps, smart contracts, public devices and untrusted networks can all add risk.
Go to Security →- Keep seed phrases offline
- Never disclose private keys or verification codes
- Verify network, address and amount
- Review every signing request
- Remove DApp approvals you no longer need
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases and private keys, then learn networks, gas and transaction hashes. After basic transfers make sense, move into DApps, signatures and approvals. This order mirrors real wallet use and makes troubleshooting more grounded.
Read getting started →Ethereum Staking Basics: PoS, Validators and Exit Mechanics
A useful staking introduction starts with Ethereum PoS, validator duties, reward sources, withdrawals and exits. Rewards are not fixed or guaranteed. Exit timing can vary, and validators can face penalties, technical failures, smart-contract risk and market volatility.
Learn Ethereum staking →Updates
Follow product notes, network changes and security reminders
Wallet workflow guidance
A clearer path for creation, backup, receiving, sending and transaction checks, organized by user task.
Network and address verification
Across EVM and Layer 2 environments, similar address formats do not mean the networks are the same.
Reject requests for seed phrases
Any page or person asking for a seed phrase, private key or verification code should be treated as unsafe.
Staking knowledge update
Additional PoS, validator, exit and penalty explanations without fixed-return claims.
FAQ
Start troubleshooting with verifiable on-chain facts
For balance, network, transfer, DApp or approval questions, first verify the network and transaction hash, then decide whether the issue is on-chain state, display, or permissions.
View full FAQ →A digital wallet helps manage on-chain accounts, addresses and signing actions. Assets are recorded on blockchains; the wallet mainly helps the user manage keys and interact with networks.
A private key directly controls a specific account. A seed phrase is commonly used to derive multiple private keys. Both are highly sensitive and should be kept offline by the user.
No. Support should not possess or ask for a user’s seed phrase or private key. Without a usable backup, a wallet service generally cannot restore control of an on-chain account.
Different networks can use similar address formats while keeping separate assets and contracts. A mismatch between the sending and receiving network can make recovery difficult.
Gas is a way to account for the resources needed to execute a transaction or contract call. Fees can vary with network rules, transaction complexity and congestion.
A transaction hash is a public identifier that can be checked in a block explorer to review status, block inclusion, fees and confirmation progress.
First confirm that you are checking the correct network, then use the transaction hash in a block explorer. Congestion, fee settings and node synchronization can all affect what the wallet displays.
imtoken
Download imtokenWhen you are ready, start with a secure backup and network check
After downloading, create or import a wallet, make an offline backup, and only then move to receiving, sending or DApp activity. No one should ask you for a seed phrase, private key or verification code.