Multi-chain
The active network determines gas assets, explorers, contracts and transfer routes. Check that both sender and receiver support the intended network.
imtoken · Multi-chain wallet and Web3 knowledge hub
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 and network selection to receiving, sending, DApp connections, approvals, network concepts and wallet security, imtoken brings the main decisions into one understandable flow so every on-chain request can be reviewed before confirmation.
Networks · Assets · Transactions · Web3Common tasks
Start with the goal, then verify each step
01
Create a Wallet
Understand seed phrases and private keys before creating or importing a wallet.
Open guide →02Back Up a Wallet
Keep the seed phrase offline and do not send it through chat or store it as a screenshot.
Open guide →03Receive Assets
Confirm the receiving network and asset type before sharing an address.
Open guide →04Send Assets
Verify the address, network, amount and gas information before confirming.
Open guide →05Connect to a DApp
Check the domain, account and network, then review every signature or approval separately.
Open guide →Multi-chain assets
Asset symbols are not enough — verify the network
Different networks can use similar address formats and can host tokens with the same symbol. Verify the network, token contract and receiving support together.
Understand multi-chain assets →imtoken App
View networks, assets and transaction history on mobile
Use a clear wallet view for everyday tasks while keeping independent judgment over networks, gas and signature requests.
Explore the App →imtoken Web
Browser connections still require individual decisions
Verify the DApp domain first. After connecting, confirm the account and network, review signatures and approvals separately, and disconnect sessions you no longer need.
Read Web guidance →
Wallet security starts with key custody
Keep seed phrases and private keys under your own control. Prefer offline backups, avoid screenshots or plaintext cloud storage, and review unused approvals regularly.
Open Security Center →Explore blockchain networks
Understand the network before taking action
Public Chains
Nodes maintain a shared ledger, transactions enter blocks and gain confirmations over time. The transaction hash is a key reference for verification.
EVM Networks
EVM networks share a similar execution model, but gas assets, network parameters and deployed contracts remain network-specific.
Layer 2
Layer 2 systems have their own settlement, data and bridging mechanisms. Understand where the asset lives and how it moves between layers.
Gas & Confirmations
Gas pays for network execution. Fees vary with network conditions, and a broadcast transaction may still need additional confirmations before it is considered final enough for your use case.
Learn more →Wallet journey
Six steps for repeatable checks
- 01
Get imtoken
Use a trusted entry point and avoid install links from unfamiliar messages.
- 02
Create or import a wallet
Understand who controls the seed phrase and private keys before importing.
- 03
Back up offline
Keep the seed phrase offline and never disclose private keys or verification codes.
- 04
Select and verify the network
Check the asset network, target network and required gas asset.
- 05
Receive or send assets
Verify the address, network and amount; consider a small test for important routes.
- 06
Review transactions and approvals
Read DApp requests before signing and revoke permissions you no longer need.
Web3 & DApps
A connection is only the beginning
Connecting a wallet does not make later requests trustworthy. Check the domain, account, network, request target and permission scope each time.
Open Web3 guide →- Visit the DApp
- Verify the domain
- Start the connection
- Review account requests
- Check signatures or approvals
- Complete the action
- Disconnect unused sessions
Security
Move security checks before the confirm button
Many wallet risks come from the wrong site, the wrong network, excessive approval scope or misunderstood signatures rather than a weak password. Keep seed phrases and private keys under your own control; legitimate support should never request them. Because on-chain transactions generally cannot be reversed unilaterally, checking the address, network, amount, spender and permission scope before confirmation is a stronger everyday defense.
Open Security Center →- Back up the seed phrase offline
- Never disclose private keys
- Verify network and address
- Review signature requests
- Manage DApp approvals
Academy · Featured starter
What Should You Understand Before Using a Digital Wallet?
An address receives assets; a seed phrase and private keys control access; the network determines where a transaction executes; gas pays for execution; a transaction hash lets you verify the record; and a DApp can ask for connections, signatures, transactions or approvals. Understanding how these ideas interact matters more than memorizing button locations.
Start learning →NetworkPublic Chains & ConfirmationsUnderstand the key concept and how to verify it in practice.NetworkEVM & Smart ContractsUnderstand the key concept and how to verify it in practice.NetworkLayer 2 BasicsUnderstand the key concept and how to verify it in practice.Web3DApp ApprovalsUnderstand the key concept and how to verify it in practice.SecurityWallet SecurityUnderstand the key concept and how to verify it in practice.BasicsBlockchain GlossaryUnderstand the key concept and how to verify it in practice.
Ethereum & PoS
Ethereum Staking Basics
Ethereum PoS uses validators to participate in proposing and attesting to blocks. Rewards are protocol-driven and can change with network conditions; withdrawals and exits can involve waiting periods.
Learn about Ethereum staking →Product and security updates
Make important changes easy to understand
Download entry points and basic usage guidance organized for clarity
Verify the destination network and asset route before cross-network actions
No legitimate party should ask for your seed phrase or private key
Staking rewards, exit queues and network state can change
FAQ
Resolve key questions before you start
A seed phrase is commonly used to derive and recover wallet accounts, while a private key directly controls a specific account. Both are highly sensitive and should never be sent to anyone.
Check the receiving address, destination network, asset type, amount and gas information. For important routes, a small test transfer can reduce uncertainty.
A transaction hash lets you inspect whether a transaction was broadcast, included, successful or failed, and how many confirmations it has.
A connection does not make later requests trustworthy. Verify the domain and review each signature, transaction and approval independently.
A token approval gives a specific contract permission to use tokens within an allowance. Review the spender and amount, and revoke permissions you no longer need.
Layer 2 systems extend transaction capacity while maintaining a settlement or data relationship with mainnet. Moving assets between layers can involve bridges and waiting periods.
No. Rewards change, exits can take time, and validator, contract, service and market risks remain.
imtoken
Manage digital assets from an understanding of networks and risk
Learn the basics of seed phrases, networks, gas, signatures and approvals so each confirmation is based on information you can interpret.