Create a Wallet
Create or import in a trusted device environment and understand the difference between a new wallet, an import and a recovery workflow.
View 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
Move from multi-chain assets, network selection and transfers into DApp connections, signatures, approvals and wallet security with a workflow built around verification. The knowledge center also covers public chains, EVM networks, Layer 2, gas, Ethereum PoS and validators.
Quick tasks
Start with the action you need to complete
Creating, backing up, receiving, sending and connecting to a DApp require different checks. Identify the task first, then review the network, address, request and permissions that belong to it.
Back Up a Wallet
Keep recovery material offline and avoid screenshots, public cloud storage and sending it through chats.
Backup security →Receive Assets
Confirm the network and asset with the sender before sharing the receiving address.
Receiving checks →Send Assets
Review the recipient, network, asset, amount and gas before signing, then keep the transaction hash.
Transaction checks →Connect to a DApp
Verify the domain first, then review connections, signatures, transactions and token approvals separately.
Connection guide →Wallet capabilities
Keep assets, networks, transactions and security in one context
Different tasks need different information hierarchies rather than one repeated interaction pattern.
Multi-chain Assets
View assets across several networks while keeping network, address and transaction state distinct.
Understand multi-chain networks →
imtoken App
Review assets, manage networks, read transaction history and initiate on-chain actions from mobile.
Explore the app →Send & Receive
Use a repeatable sequence for addresses, networks, amounts, gas and transaction hashes.
Transfers →imtoken Web
Understand browser connections, account visibility, signatures and approvals as separate actions.
Web connections →Wallet Security
Keep recovery material offline and review every signature, transfer and approval independently.
Security center →
Network explorer
Identify the chain before interpreting an asset or transaction
Each network topic remains directly readable, while the tabs provide a focused way to move between subjects.
Multi-chain
One wallet can present several networks while balances, transactions, fees and contract state remain independent. Confirm the active network before acting on an asset.
Multi-chain guide →
Public Chains
Nodes propagate transactions, blocks record state and consensus produces confirmations. Explorers verify public records but do not replace network and address checks.
Public-chain basics →
EVM
EVM networks share concepts such as addresses, gas and contracts while chain state and deployments remain separate. Similar address formats do not prove that the network is correct.
EVM networks →
Layer 2
Layer 2 systems extend the base layer. Moving assets across layers can involve bridges, waiting periods and several confirmation stages.
Layer 2 basics →Gas & Confirmations
Gas reflects execution cost while transaction hashes and block confirmations help distinguish submitted, included, failed and confirmed states.
Gas & confirmations →Wallet path
From getting imtoken to reviewing transactions and approvals
01
Get imtoken
Use the single download entry and verify the source before continuing.
02
Create or import a wallet
Handle recovery material only in a trusted environment.
03
Back up offline
Keep the seed phrase offline and never disclose private keys or verification codes.
04
Select and verify the network
Confirm the network, asset and native fee asset rather than relying on address format alone.
05
Receive or send assets
Review the address, amount, network and gas, then read the full signing prompt again.
06
Review transactions and approvals
Keep the transaction hash, verify confirmation status and review DApp approvals that are no longer needed.
Web3 & DApps
A connection is only the beginning; review every request independently
Connecting a wallet does not mean every later signature or approval should be accepted. Treat each request as a separate decision.
Open the Web3 guide →Visit the DApp
Verify the domain
Start the connection
Review account access
Inspect the signature or approval
Complete the action
Disconnect sessions you no longer need
Check the domain first, then the request type, network, contract target and permission scope. A previous safe action does not make the next request safe automatically.
Security
Protect recovery material and every on-chain decision
Your seed phrase and private keys remain under your control, and imtoken will never ask for your seed phrase, private key or verification code. Keep recovery material offline and avoid screenshots, public cloud storage, chat forwarding and remote-control tools. Before transfers, review the address, network, asset and amount. In DApps, treat message signatures, transaction signatures and token approvals as separate requests. On-chain transactions generally cannot be reversed by a wallet alone, and third-party DApps and smart contracts can involve risk.
Open the security center →- Back up the seed phrase offline
- Never disclose private keys
- Verify the network and address
- Review signature requests
- Manage DApp approvals
Academy
Build wallet knowledge in the order you actually use it
What Should You Understand Before Using a Digital Wallet?
Learn addresses, seed phrases, private keys, networks, gas, transaction hashes, DApps and approvals in the context of real wallet actions.
Read the beginner guide →Networks
Public chains and confirmations
Understand nodes, blocks, consensus and confirmation state.
EVM
EVM and smart contracts
Understand gas, contract calls and token approvals.
Layer 2
Moving assets across layers
Understand base-layer relationships, bridges, waiting and arrival confirmation.
Web3
DApp approvals
Understand spenders, allowances and revocation.
Security
Wallet security
Recovery material, phishing, devices and transaction checks.
Glossary
Blockchain glossary
Understand key terms through practical scenarios.
Ethereum · PoS
Understand the mechanism and risks before deciding whether to participate
Ethereum Staking Basics
Learn about Ethereum PoS, validator duties, reward sources, network conditions, withdrawals and exits. Staking does not guarantee returns and rewards can change.
Ethereum Staking →What to understand first
Exits can involve waiting periods, validators can face protocol penalties, smart contracts can have technical risk and asset prices can fluctuate.
PoS & Validators →Updates
Product, network, security and service notices
Recent UpdateView →
Reconfirm the active network before sending
Similar address formats do not replace destination-network verification.
Product NoticeView →
Keep the transaction hash after submitting
Verify the public record on the explorer for the matching network.
Security NoticeView →
Review DApp approvals regularly
Permissions that are no longer needed should be considered for revocation.
Service NoticeView →
Understand exits and risk before staking
Rewards, waiting periods and validator conditions can all change.
FAQ
Common questions answered with practical checks
No. imtoken will not ask you to send a seed phrase, private key or verification code.
Match the sender, recipient, asset and DApp network rather than relying on address format alone.
Check the recipient, network, asset, amount and gas, then read the signing request again.
It identifies the public transaction record on the relevant network and helps verify status.
No. Connections, signatures, transactions and approvals are separate actions.
No. Rewards can change and staking also involves validator, network, contract and market risks.
imtoken
Download imtoken