Multi-chain assets and networks
Before viewing assets across networks, understand how networks differ, how addresses relate, and how confirmations work. A familiar address format does not mean two networks are the same.
Learn more →
imtoken
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, sending and receiving to DApp connections, token approvals, network concepts, and wallet security, imtoken brings day-to-day actions and on-chain verification into one clear learning path.
Quick start
Start with the task you need to complete
01Create a WalletUnderstand preparation, account creation, and how backup fits into the process.→02Back Up a WalletKeep a seed phrase offline and understand the boundary around private-key protection.→03Receive AssetsConfirm the address, asset, and network before sharing receiving information.→04Send AssetsReview the address, network, amount, gas, and transaction status.→05Connect to a DAppCheck the domain, account request, signature, and approval details.→
Wallet capabilities
Connect assets, networks, and security in one practical workflow
Different tasks need different levels of detail. Explore multi-chain assets, mobile use, transfers, browser connections, and security principles from distinct angles.
imtoken APP
View assets, switch networks, inspect transaction history, and confirm the request source before connecting to a DApp from a mobile device.
Send & Receive
Check the network and receiving address; when sending, review the asset, amount, gas, and keep the transaction hash for later verification.
Learn more →imtoken Web
Browser connections make Web3 apps accessible. Review each signature and approval independently rather than trusting later requests simply because a site is already connected.
Learn more →
Wallet security
Seed phrases and private keys remain under the user’s control. Offline backups, approval reviews, device security, and transaction checks work together as everyday safeguards.
Learn more →Blockchain networks
Understand every on-chain action through its network context
Multi-chain
One wallet can participate in multiple networks, but assets, gas, and confirmation records remain network-specific.
Learn more →Public Chains
Nodes use consensus to maintain blocks and transactions, while block explorers let users independently review public chain state.
Learn more →
EVM
EVM-compatible networks share many address and contract concepts, but chain IDs, gas, and assets still need individual verification.
Learn more →
Layer 2
Layer 2 systems have a defined relationship with mainnet; cross-layer transfers may involve bridges, waiting periods, and different confirmation paths.
Learn more →
Gas & Confirmations
Gas reflects execution cost on a network, while confirmation counts help describe how a transaction has progressed after block inclusion.
Learn more →Wallet journey
Six steps for a repeatable wallet routine
Button labels change, but the sequence of understanding, checking, and verifying can be reused across networks and applications.
- 01
Get imtoken
Use the download entry on this site rather than obtaining installation files from unknown sources.
- 02
Create or import a wallet
Use a device environment you control before creating a new account or importing an existing wallet.
- 03
Back up the wallet offline
Keep the seed phrase offline; avoid screenshots, cloud uploads, and sharing private keys.
- 04
Select and verify the network
Confirm that the network name, asset, and destination address belong to the intended environment.
- 05
Receive or send assets
Check receiving information; before sending, review the address, network, amount, and gas.
- 06
Review transactions and approvals
Keep transaction hashes, verify on-chain status, and periodically review DApp approvals you no longer need.
Web3 & DApp
Connection is only the first step; signatures and approvals need separate decisions
Web3 apps can ask a wallet for account access, signatures, or contract interactions. Separating these stages makes permissions and risks easier to understand.
Learn more →- Visit the DApp
- Confirm the domain
- Start the connection
- Review the account request
- Check the signature or approval
- Complete the action
- Disconnect unused sessions
Security
Keep critical credentials under your own control
Wallet security is not a promise of absolute protection. It is a set of repeatable habits: keep seed phrases and private keys under your control; remember that staff will not ask for them; verify the address, network, and amount before transferring; read signature prompts; check approval targets and limits; and review permissions you no longer need. On-chain transactions are generally not reversible by a wallet alone, and third-party DApps or smart contracts can carry risk.
Open the Security Center →- Back up seed phrases offline
- Never disclose private keys
- Check the network and address
- Read signature requests
- Manage DApp approvals
Academy
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases, private keys, networks, and gas. Then connect those basics to transaction hashes, DApps, and approvals. The goal is to know when an action is expected and when you should stop to verify it.
Read the getting-started guide →Ethereum
Ethereum Staking Basics
Ethereum PoS uses validators to participate in network consensus. Understanding reward sources, network state, withdrawals, and exits is more useful than focusing only on a headline rate. Staking does not guarantee returns, rewards can change, and exits can involve waiting periods.
Learn more →Product & security updates
Recent guidance and important reminders
Product NoticeWallet learning paths continue to improve
Content is organised around assets, networks, transactions, and security checks.
→Network NoticeVerify the destination chain before cross-network actionsA similar address format does not mean assets exist on the same network.
→Security NoticeNever give a seed phrase or private key to anyoneStaff will not ask for these credentials or require them in a web form.
→Service NoticeDownloads use the single download.html entryA download begins only after the user actively selects a download button.
→FAQ
Frequently asked questions
Will imtoken ask for my seed phrase or private key?
No. Staff will not ask for your seed phrase, private key, or verification code.
What should I check before sending?
Confirm the address, network, asset, amount, gas, and the exact transaction request.
Why keep a transaction hash?
It lets you review transaction status and confirmations in the correct block explorer.
Does connecting to a DApp equal approving it?
No. Connection, signing, approval, and transfer are separate actions and should be reviewed separately.
Why does Layer 2 require careful network checks?
Each Layer 2 can have a different asset path, bridge, and confirmation process.
Does Ethereum staking guarantee returns?
No. Rewards can change and participation may involve exit delays, protocol penalties, technical risk, and price volatility.
imtoken
Start using imtoken with clear network and security checks
All download buttons lead to this site’s download.html entry. Before you begin, understand seed-phrase backup, network selection, and transaction checks.