Create a Wallet
Understand addresses, seed phrases, private keys and networks before creating a wallet on a trusted device.
Open guide →imtoken
Manage Multi-chain Assets and Connect to Web3 with Clarity
A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken
Understand multi-chain assets, network selection, sending and receiving, DApp connections, signatures, approvals, network concepts and wallet security in one clear workflow. Each action should be based on information you can verify.
Quick tasks
Start with what you need to do
Common actions are separated into clear paths with the checks that matter at each step.
Back Up a Wallet
Keep the seed phrase complete, ordered and offline; do not share it through chats, screenshots or plaintext cloud storage.
Open guide →Receive Assets
Confirm the target network and asset type before sharing an address; a small test can reduce uncertainty.
Open guide →Send Assets
Review the recipient, network, amount and gas, then read the transaction again before signing.
Open guide →Connect to a DApp
A connection is only a session; signatures, approvals and transactions still require separate review.
Open guide →Wallet capabilities
One framework for assets, networks, records and security
Multi-chain assets
Multi-chain management works best when each network’s assets, addresses, fees and confirmations stay clearly separated.
imtoken APP
View assets, manage networks, review history and inspect each DApp request on mobile.
Send & Receive
Verify the recipient, network, amount, gas and transaction hash before and after sending.
imtoken Web
Understand browser connections, approvals and session cleanup without treating a connection as consent to later requests.
Wallet security
Seed phrases and private keys remain under user control; signatures and approvals should be reviewed by target, network and scope.
Network explorer
Choose the network question first
Multi-chain
Each network has separate state. When switching, verify the network name, native gas asset, destination address and matching explorer.
Learn more →Public Chains
Public chains record transactions through nodes, blocks and consensus. Transaction hashes and confirmations provide an independent view of results.
Learn more →
EVM
EVM networks often share address formats, while assets, gas, token contracts and approvals remain network-specific.
Learn more →
Layer 2
Layer 2 systems relate to mainnet through settlement or data mechanisms. Cross-layer transfers can involve bridges, confirmations and waiting.
Learn more →
Gas & Confirmations
Gas reflects network resource use, while confirmations show block inclusion. Pending and failed transactions require different checks.
Learn more →Usage path
Six steps for a repeatable wallet workflow
Get imtoken
Use the dedicated download entry instead of unknown links.
Create or import a wallet
Use a trusted device and confirm the resulting address.
Back up the wallet offline
Keep the seed phrase offline and never disclose private keys or verification codes.
Select and verify the network
Verify the network name, address and gas asset to avoid wrong-network actions.
Receive or send assets
Verify recipient, network and amount; use a small test when appropriate.
Review transactions and approvals
Keep transaction hashes, inspect DApp signatures and review old approvals regularly.
Web3 & DApp
A connection is only the beginning
Connecting a wallet does not mean every signature should be accepted. Review each signature and approval independently, including the domain, network and target contract.
A wallet connection does not imply consent to every later request. Inspect each signature and approval separately.
- Visit the DApp
- Verify the domain
- Start a connection
- Review account access
- Inspect signatures or approvals
- Complete the action
- Disconnect unused sessions
Security
Turn security principles into repeatable checks
Wallet security is an ongoing set of habits rather than a one-time setting. Seed phrases and private keys remain under user control and should never be sent to anyone. Review the address, network and amount before transferring; on-chain transactions often cannot be reversed by a wallet alone. When using third-party DApps or smart contracts, inspect signature content, approval targets and permission scope, and remove permissions you no longer need. Shared devices, public networks and remote-control environments require extra care.
Back up seed phrases offlineNever disclose private keysVerify network and addressReview signature requestsManage DApp approvals
Academy
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases, private keys, networks, gas, transaction hashes, DApps and approvals before creating a wallet or moving assets. This makes unfamiliar requests easier to evaluate.
Read the starter guide →Ethereum & PoS
Understand the mechanism before deciding
Ethereum Staking Basics
Understand Ethereum PoS, validators, reward sources, network state, withdrawals and exits. Rewards can vary and exits can involve waiting periods.
Read staking basics →Before participating
Consider protocol penalties, validator status, smart-contract risk, waiting periods, asset-price volatility and third-party risk. Staking does not guarantee returns.
Learn about validators →Updates
Product and security notes without hype
Product notice: unified download entry and language paths
Use on-site explanations to understand changes without invented dates, partnerships, rankings or user metrics.
Verify the full domain and request target before connecting
Use on-site explanations to understand changes without invented dates, partnerships, rankings or user metrics.
Transaction records emphasize hash-based verification
Use on-site explanations to understand changes without invented dates, partnerships, rankings or user metrics.
Check status before resubmitting during congestion
Use on-site explanations to understand changes without invented dates, partnerships, rankings or user metrics.
Staking guides include waiting periods and risk notes
Use on-site explanations to understand changes without invented dates, partnerships, rankings or user metrics.
FAQ
Frequently asked questions
A wallet manages keys and account information. An address is a public on-chain identifier that can receive assets. An address may be shared; a seed phrase or private key should not be.
It is safer not to. Screenshots can sync to cloud storage or be read by other software. Prefer an offline backup that you can protect physically.
You should not rely on any service to restore a private key. Seed phrases and private keys remain under the user’s control; requests to reveal them should be treated as high risk.
Networks maintain separate state and fee systems. The same-looking address can exist on multiple networks while holding entirely different assets and histories.
Gas is the network-fee concept used to pay for computation or transaction inclusion. It is usually paid in the network’s native asset and can change with network demand.
A transaction hash is a traceable identifier that can be used in the matching network’s block explorer to review status, block inclusion, sender, recipient and fees.
Check network conditions, fee settings, nonce and the existing transaction before submitting anything again. Repeated submissions without understanding the cause can create confusion or extra cost.
Get imtoken
All download actions use the dedicated download page. Review the network, address and security context before acting.