Create a Wallet
Understand the wallet, address and recovery credentials first, then create or import only in a trusted environment.
Creation guide →
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
Manage assets across multiple networks while keeping network selection, receiving, sending, DApp connections, approvals and wallet security understandable. Before an on-chain action, review the address, network, fees and exact request rather than relying on a familiar interface alone.
Quick Tasks
Choose the next step by what you want to do
Back Up a Wallet
Keep the seed phrase offline. Do not screenshot it, upload it to cloud storage or send it to another person.
Backup principles →Receive Assets
Share the receiving address together with the intended network and verify both before assets are sent.
Receiving checks →Send Assets
Review the recipient, network, asset, amount and gas before confirming, then keep the transaction hash for verification.
Transfer checklist →Connect to a DApp
Verify the domain first, then treat connection, signature and token approval as separate requests that each require review.
Connection steps →Wallet Capabilities
Bring asset and Web3 decisions into one clear view
A wallet can help read on-chain state and prepare requests, but the user still needs to verify networks, transfers, signatures and approvals before confirming them.
Multi-chain Assets
Understand which network an asset belongs to, verify addresses and contracts, and separate transaction confirmation from local display state.
Understand multi-chain use →
imtoken App
Review assets, switch networks, inspect transaction history and access DApps from a mobile wallet workflow.
Explore the app →Send & Receive
Check the address, network, amount, gas and transaction hash in a consistent order.
Transfer guide →imtoken Web
Verify the DApp domain before connecting, then review each signature or approval on its own merits.
Using imtoken Web →Wallet Security
Keep seed phrases and private keys offline, review DApp permissions and remove approvals that no longer serve a purpose.
Security center →
Explore Blockchain Networks
Identify the network before interpreting assets and transactions
Multi-chain does not mean automatic cross-chain movement
A wallet can organize several networks, but each network maintains its own state. Confirm the source and destination network before moving an asset.
Multi-chain guide →
Public chains maintain shared state through network rules
Transactions are validated by the network and included in blocks. A transaction hash provides a direct way to inspect the recorded state.
Public-chain basics →
A familiar address does not make two EVM networks the same
EVM-compatible networks may use the same address format while gas assets, contracts and balances remain separate.
Understand EVM networks →
Understand the relationship with mainnet before bridging
Bridge direction, withdrawal mechanisms and waiting periods can differ. Verify which layer currently holds the asset and where it should arrive.
Layer 2 guide →Gas → Block → Confirm
Fees and confirmations answer different questions
Gas reflects resources needed to execute a request; confirmations describe what happened after the network accepted and included the transaction.
Gas & confirmation guide →Wallet Journey
Build a repeatable six-step security habit
- 01
Get imtoken
Use the official download entry point and review the source before installing.
- 02
Create or Import a Wallet
Use a trusted device and understand which recovery credentials control the wallet.
- 03
Back Up Offline
Keep the seed phrase offline and never disclose the private key to another person.
- 04
Select and Verify the Network
Confirm the network required by the recipient, asset, DApp or contract.
- 05
Receive or Send Assets
Review the address, network, amount and gas before confirming a transfer.
- 06
Review Transactions and Approvals
Inspect signatures before approving them and periodically remove permissions you no longer need.
Web3 & DApps
Review every request as a separate decision
Connecting a wallet does not mean every later request should be accepted. Each signature, transaction and approval needs its own review.
Open the Web3 guide →Open the DAppVerify the domainStart the connectionReview the account requestInspect the signature or approvalComplete the intended actionDisconnect sessions no longer needed
Security
Security is a repeatable review process
Keep seed phrases and private keys under your own control. imtoken staff will never ask for a seed phrase, private key or verification code. Verify the address, network and amount before a transfer; inspect the target and scope before an approval; and use extra care on public devices or networks. On-chain transactions generally cannot be reversed unilaterally by a wallet, and third-party DApps or smart contracts may introduce independent risks.
Open the security center →- Back up the seed phrase offline
- Never disclose a private key
- Verify the network and address
- Review each signature request
- Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
Start by separating wallets, addresses, seed phrases and private keys. Then learn networks, gas and transaction hashes. Before using a DApp, understand that connection, signature and approval are three distinct actions.
Read the beginner guide →Ethereum Staking Fundamentals
Understand Ethereum PoS, validator duties, sources of protocol rewards, network state, withdrawals and exits. Staking does not guarantee returns, and rewards can change over time.
Ethereum staking guide →Know the risks before participating
- Validators may face protocol penalties
- Exits and withdrawals can involve waiting periods
- Smart contracts carry technical risk
- Digital-asset prices can fluctuate
- Third-party services carry separate risk
Updates
Product, network, security and service notices
A consistent wallet-review path
Use network, address, transaction hash and approval information together instead of relying on a single status label.
Confirm the destination chain before cross-network actions
A similar address format does not mean assets move automatically between independent networks.
Never enter a seed phrase or private key into an ordinary webpage
imtoken staff will not request these recovery secrets or verification codes.
Staking guidance includes exit and risk information
Rewards may change, exits can involve waiting, and validator, contract and market risks remain.
FAQ
Common Questions
Seed phrases and private keys should remain under the user’s own control.
Different networks maintain independent on-chain state even when address formats look similar.
It identifies a transaction so you can inspect its recorded status and confirmations on the relevant network.
No. Connection, signature and token approval are separate actions and should be reviewed independently.
No. Rewards can change and staking includes validator, exit, contract and market risks.
No. imtoken staff will never ask for a seed phrase, private key or verification code.
imtoken
Download imtokenStart with a clear verification habit
Understand the network, address, transaction and approval details before each on-chain action.