Create a Wallet
Start with a clean account setup and understand what is created locally before any funds are involved.
Learn more →A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken
Manage Multi-chain Assets and Connect to Web3 with Clarity
Keep asset management, network selection, sending and receiving, DApp access, approvals, network knowledge and wallet security in one clear learning path. imtoken helps you understand what each request means before you confirm it.
Start with a task
Five common actions, one consistent review habit
Back Up a Wallet
Record recovery information offline and verify that your backup can be understood without exposing it.
Learn more →Receive Assets
Match the receiving address with the correct network and asset before sharing it.
Learn more →Send Assets
Review destination, network, amount, gas and transaction details before submission.
Learn more →Connect to a DApp
Verify the domain, requested account access and every later signature or approval.
Learn more →Wallet capabilities
See the relationship between assets, networks and permissions
Multi-chain assets
View assets across multiple networks while keeping network identity, address checks and confirmation state in context.
imtoken App
Manage networks, assets and transaction history from a mobile wallet context.
Send & Receive
Match address, network, amount, gas and transaction hash through the full transfer lifecycle.
Transfer guide →imtoken Web
Review browser connections, requested accounts, approvals and disconnection when using Web3 services.
Wallet security
Keep recovery secrets offline, inspect approval scope and avoid treating a connection as blanket permission.
Explore networks
Know where a transaction actually lives
Multi-chain
A multi-chain wallet can display accounts and assets across several networks, but network identity still matters for fees, explorers and transaction finality.
Read the guide →Public Chains
A public chain is an open network where nodes verify and share blocks. Wallets prepare transactions; the chain records the result after consensus.
Read the guide →
EVM
EVM-compatible networks share a familiar account and contract model. Similar addresses do not merge balances across separate networks.
Read the guide →
Layer 2
Layer 2 networks extend capacity while maintaining a defined relationship with a base chain. Cross-layer transfers may involve bridges and waiting periods.
Read the guide →
Gas & Confirmations
Gas represents network execution cost. A transaction can be validly signed yet remain pending or fail if fee and network conditions are not sufficient.
Read the guide →Wallet journey
From first install to ongoing permission review
- 01
Get imtoken
Use the official entry point and keep the application source clear.
- 02
Create or import a wallet
Understand whether you are creating a new account or importing an existing one.
- 03
Back up the wallet offline
Keep the seed phrase offline and never disclose the private key to anyone.
- 04
Choose and verify the network
Check the intended network before relying on an address or token label.
- 05
Receive or send assets
Verify address, network, amount and gas before confirming the transfer.
- 06
Review transactions and approvals
Use the transaction hash to verify results and revisit approvals that are no longer needed.
Web3 & DApps
Treat every request as a separate decision
Connecting a wallet does not mean every later signature or token approval should be accepted. Verify each request on its own.
Read the Web3 guide →- Open the DApp
- Verify the domain
- Start the connection
- Review account requests
- Inspect signatures or approvals
- Complete the intended action
- Disconnect unused sessions
Security
Security starts before a signature is requested
A safer wallet routine combines offline recovery backups, domain verification, network and address checks, careful signature review and permission cleanup. No wallet can remove the risks of a malicious contract, compromised device or user-approved transfer, so the quality of each confirmation matters.
Go to Security →- Back up seed phrases offline
- Never disclose private keys
- Verify network and address
- Inspect signature requests
- Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
Learn how addresses, seed phrases, private keys, networks, gas, transaction hashes, DApps and approvals fit together before you move value on-chain.
Read the starter guide →NetworksPublic chains and confirmationsUnderstand nodes, blocks and why confirmation depth matters.EVMEVM and smart contractsConnect addresses, gas, contracts and token approvals.Layer 2Layer 2 fundamentalsLearn mainnet relationships, bridges and arrival checks.DAppToken approvalsReview targets, allowance scope and revocation.
Ethereum staking fundamentals
Understand PoS, validators, reward sources, network status, withdrawals and the exit process without treating variable rewards as guaranteed returns.
Learn about staking →Updates
Product, network, security and service notices
Navigation and learning paths are organized around common wallet tasks.
Similar-looking addresses can exist on different EVM networks.
A wallet connection is not blanket permission for later requests.
Transaction hashes and network context make support questions easier to diagnose.
FAQ
Common questions before you confirm
imtoken helps users organize multi-chain accounts and assets, prepare transfers, review transaction history and connect to DApps after explicit user confirmation. Final transaction state is determined by the relevant blockchain network.
A seed phrase can commonly restore a set of wallet accounts, while a private key provides signing control for a specific account. Both are highly sensitive and should stay offline and undisclosed.
Many EVM-compatible networks use the same address format, but their assets and transaction histories are separate. An address check is incomplete without a network check.
Gas is the network accounting mechanism for the computational resources used by a transaction or contract call. The cost can change with network conditions and the complexity of the action.
A transaction hash is a primary reference for looking up an on-chain transaction on the correct network explorer, including status, block data, fees and failure information.
Once a transaction is confirmed by the network, a wallet generally cannot reverse it unilaterally. Verify address, network and amount before sending.
No. A connection normally creates an interaction session. Token approvals, signatures and transactions are separate requests that should each be reviewed.
imtoken
Download imtokenStart with a clear wallet workflow
Download from the dedicated entry point, then continue with the getting-started and security guides.