Create a Wallet
Create or import only in a trusted environment.
Open guide →Manage assets across multiple networks, understand sending and receiving, verify network selection, connect to DApps, review approvals and build stronger wallet security habits.

Creation, backup, transfers and DApp use have different checks and different risk boundaries.
Create or import only in a trusted environment.
Open guide →Keep recovery material offline and verify the backup.
Open guide →Confirm the network, receiving address and token.
Open guide →Check address, network, amount and gas before signing.
Open guide →Verify the domain and review each request independently.
Open guide →Keep the differences between assets, networks, transfers and approvals visible.
Review balances together with the active network, account and confirmation status.
Explore multi-chain →Mobile access for network management, asset review and transaction history.

Check address, network, amount, gas and transaction hash.
Browser connections with explicit approval review.
Network choice affects balances, fees, confirmations and contract availability.
Multiple networks can appear in one wallet while balances remain on separate chains.
Always verify the active network before moving assets or calling a contract.
Nodes, blocks and consensus record transactions and confirmations.
Always verify the active network before moving assets or calling a contract.
Compatible networks share execution concepts but keep separate state and gas markets.
Always verify the active network before moving assets or calling a contract.
Layer 2 systems scale mainnet and often use dedicated bridge or withdrawal flows.
Always verify the active network before moving assets or calling a contract.
Fees and confirmations help explain cost, inclusion and finality.
Always verify the active network before moving assets or calling a contract.
Use the official download entry and verify the product.
Keep recovery material away from websites and chat tools.
Store the seed phrase offline and never share private keys.
Confirm the active network before every transfer or contract action.
Check address, amount, network and fee asset.
Keep transaction hashes and review approvals you no longer need.
Connecting a wallet does not mean every later signature or approval should be accepted.
Open the Web3 guide →Your seed phrase and private keys are under your control. imtoken will not ask you to send them. Review address, network, amount and permission scope before transferring, signing or approving.
Open security center →Addresses, seed phrases, private keys, networks, gas, transaction hashes, DApps and approvals form one practical learning path.
Read the guide →Nodes, blocks and confirmation state.
Execution, gas and contract calls.
Mainnet relationships and bridging.
Approval scope and lifecycle.
Recovery material and phishing.
Plain-language definitions.
Learn about PoS, validators, reward sources, network state, withdrawals and exits.
Learn more →Rewards can change, exits may involve waiting periods, validators can be penalized, smart contracts can fail and asset prices can fluctuate.
PoS & validators →Address format alone does not prove the correct network.
No. imtoken will not ask you to send a seed phrase, private key or verification code.
Match the network used by the sender, recipient, token or DApp; do not rely on address format alone.
Check recipient, network, asset, amount and gas, then review the request again before signing.
It is a public identifier used to look up a transaction on the correct network explorer.
No. Connection, signing, transactions and approvals are different actions.
No. Rewards can change and staking involves network, validator, contract and market risk.