Create a Wallet
Understand creation versus import and prepare a safe backup environment.
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
Learn multi-chain assets, network selection, sending and receiving, DApp connections, token approvals and wallet security through a clear workflow. imtoken emphasizes what to verify before a signature, approval or transaction so users can make decisions with better context.
Start with a task
Five common wallet tasks
Back Up a Wallet
Keep the seed phrase offline and out of screenshots, chats and cloud documents.
Learn more →Receive Assets
Check the receiving address, target network and asset type together.
Learn more →Send Assets
Review the address, network, amount and gas, then verify the transaction hash.
Learn more →Connect to a DApp
Verify the domain, then review connection, signature and approval requests separately.
Learn more →
Wallet capability
Organize assets across networks without losing context
Treat every balance as belonging to a specific network. Check the network, destination and confirmation state before moving assets between accounts or services.
Send & receive
Review the address, network, amount, gas and transaction hash as one sequence.
Open guide →imtoken App
Mobile access for asset views, network management, transaction history and DApp requests.
imtoken Web
Understand browser connections, account requests, approvals and when to disconnect.
Web guidance →
Wallet security
Keep seed phrases and private keys offline. Review every approval independently.
Multi-chain does not mean interchangeable networks
A familiar address format or token name does not guarantee that two networks are compatible. Verify the intended chain and recipient support before sending.
Nodes, blocks and confirmation
Use block height and transaction status to understand where a broadcast transaction sits in the public ledger.
EVM compatibility still requires network checks
Gas assets, explorers, contracts and network parameters can differ even when networks share an EVM-compatible execution model.
Layer 2 adds a cross-layer workflow
Bridging or withdrawing may involve separate contracts, confirmation stages and waiting periods. Read the route before moving assets.
Gas reflects network execution conditions
Fees can change with network state and transaction complexity. Confirmation time should be evaluated together with the chosen fee and current network load.
Learn gas and confirmations →Wallet journey
A six-step path from setup to ongoing review
- 01
Get imtoken
Use the official download entry and review the environment before installation.
- 02
Create or import a wallet
Know whether you are generating new keys or restoring existing ones.
- 03
Back up offline
Keep seed phrases offline and never send private keys to anyone.
- 04
Choose and verify a network
Confirm the intended network, gas asset and recipient support.
- 05
Receive or send assets
Check the address, network and amount before broadcasting.
- 06
Review transactions and approvals
Verify transaction hashes and remove permissions you no longer need.
Web3 & DApp
Treat each request as a separate decision
Connecting a wallet does not mean you should accept every later signature or approval. Read each request in the context of the domain, account, network and permission scope.
Open Web3 guide →- Visit the DApp
- Confirm the domain
- Start a connection
- Review the account request
- Check the signature or approval
- Complete the intended action
- Disconnect unused sessions
Security
Build security around what you control
Seed phrases and private keys remain under the user’s control. imtoken personnel will never ask for them. Security also depends on the device, network, destination address, DApp domain, signing message and approval scope. On-chain transactions are generally not reversible by the wallet alone, so the strongest protection is a repeatable review process before acting.
Open Security Center →- Back up the seed phrase offline
- Never disclose a private key
- Check the network and address
- Read signing requests
- Manage DApp approvals
Academy
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases, private keys, networks, gas and transaction hashes. Then move on to DApps and approvals. This order helps you understand what a wallet request means before you authorize it.
Read the starter guide →NetworkPublic chains and confirmation
How nodes and blocks produce verifiable transaction state.
EVMEVM and smart contractsAddresses, gas, tokens and contract execution.
Layer2Layer 2 basicsBase networks, bridges and cross-layer movement.
DAppToken approvalsTargets, allowances and permission cleanup.
SecurityWallet securityKey protection, phishing and transaction checks.
GlossaryBlockchain glossaryA practical reference for recurring wallet terms.
Ethereum & PoS
Ethereum staking basics
Proof of stake uses validators to help secure the network. Rewards come from protocol activity and can change. Withdrawals and exits may involve queues, while validator performance and protocol rules can affect outcomes.
Learn Ethereum staking →Understand before participating
- Protocol penalties can affect validators
- Exit queues may create waiting periods
- Smart contracts may carry technical risk
- Digital asset prices can fluctuate
- Third-party services have independent risks
FAQ
Common questions before you act
A digital wallet typically manages keys and helps you view addresses, assets and on-chain transactions. The assets themselves are recorded on the relevant blockchain rather than stored as a balance inside a webpage.
A seed phrase can usually derive a set of wallet keys, while a private key directly controls a corresponding address. Both are highly sensitive and should never be sent through chat, forms or screenshots.
The same asset name may exist on multiple networks, and the recipient must support the network you choose. Checking the address without checking the network can still result in a serious transfer mistake.
Gas is the fee mechanism used to execute transactions or contract calls on a blockchain. The actual cost depends on network rules, transaction complexity and congestion.
A transaction hash is a unique identifier that lets you inspect status, block height, confirmation count and related addresses in a block explorer.
An account connection by itself usually does not transfer assets, but later signatures, approvals or transactions can create permissions or move value. Review every request separately.
imtoken
Start with a clear wallet workflow
Use the official download entry, then build your setup around offline backups, network checks and independent review of every signature or approval.