Create a Wallet
Understand the difference between creating a new wallet and importing an existing one, then establish backup before moving important assets.
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
Organize multi-chain assets with clear network selection, receiving and sending workflows, transaction records and DApp guidance. Learn how approvals, signatures, network fees and wallet security fit together before you act.
Back Up a Wallet
Keep recovery material offline and private, with a backup you can read and verify without sharing it with anyone.
Open guide →Receive Assets
Confirm both the receiving address and the network; a correct-looking address does not prove the network is correct.
Open guide →Send Assets
Review the destination, network, amount and fee before signing because on-chain transfers are often not reversible by the wallet.
Open guide →Connect to a DApp
Verify the domain and account request, then review each later signature or approval as a separate decision.
Open guide →Wallet capabilities
One wallet workflow, several kinds of decisions
Multi-chain assets
Separate networks, confirm addresses and understand confirmation status before treating a balance as fully settled.
Send & receive
Review the receiving address, active network, amount, gas and transaction hash as parts of one lifecycle.
imtoken APP
Use mobile wallet views to manage networks, inspect balances and review history while keeping device risk in mind.
imtoken Web · DApps · Security
Browser connection, approval review and safe disconnection are separate steps. Keep seed phrases and private keys offline and private.
Understand browser connections → Open security center →Blockchain networks
Read the network before you read the balance
Multi-chain Networks
Separate assets by network, confirm fee assets and use on-chain records to validate the final state.
Read more →Public Chains
Understand nodes, blocks, broadcast status and confirmations instead of treating a wallet display as the only source of truth.
Read more →
EVM Networks
Review chain ID, gas asset, contract address and token approval scope across compatible networks.
Read more →
Layer 2
Know whether you are on the base chain or Layer 2, and understand bridge paths and waiting periods before moving assets.
Read more →
Gas & Confirmations
Fees, pending status and confirmation counts describe different parts of the transaction lifecycle.
Read more →Wallet path
Six checkpoints from setup to ongoing review
Get imtoken
Use the official download entry and avoid unknown redistribution links.
Create or import
Know whether you are creating a new key set or importing one you already control.
Back up offline
Keep recovery material private and readable without screenshots or chat transfers.
Choose the network
Confirm the network, fee asset and destination before moving funds.
Receive or send
Review address, amount and network before signing a transaction.
Review transactions and approvals
Use transaction hashes and approval checks to verify what remains active.
Web3 & DApp
Treat every request as a new decision
A connection does not justify every later signature. Read the domain, account request, signature text, approval scope and expected on-chain result separately.
Security reminder
Connecting a wallet does not mean every signature request should be approved. Review each signature and approval independently.
- Visit the DApp
- Confirm the domain
- Start the connection
- Review account requests
- Check the signature or approval
- Complete the intended action
- Disconnect unused connections
Security
Build security from repeatable checks, not absolute promises
Seed phrases and private keys are controlled by the user and should never be sent to anyone. Review addresses, networks, signatures and approvals before confirming, and treat third-party DApps and smart contracts as potential risk sources.
Open security center →
- Back up seed phrases offline
- Never disclose private keys
- Verify network and address
- Review signature requests
- Manage DApp approvals
Academy
What Should You Understand Before Using a Digital Wallet?
Start with the durable ideas behind the interface: addresses identify destinations, seed phrases and private keys control access, networks define where transactions live, gas pays for execution, transaction hashes reveal on-chain status, and DApp approvals can outlive a browsing session.
Read the beginner guide →Ethereum · PoS
Ethereum Staking Basics
Ethereum PoS uses validators to participate in consensus. Reward sources, validator status, withdrawals and exits are governed by network rules and can change over time.
Learn the mechanism →Before participating
Risk belongs in the same conversation as mechanism
Rewards are not guaranteed. Exits may involve waiting periods, validators can face penalties, smart contracts can fail, third-party services can add operational risk, and digital asset prices can fluctuate.
Understand PoS & validators →Updates
Updates organized by what users need to understand
Wallet workflow guidance refined
Clarifies network checks, backup and transaction review as a continuous workflow.
Review the active network before sending
Similar address formats do not make different networks interchangeable.
Treat every signature as a separate decision
A prior connection should not be treated as approval for a later signature.
Use the support path without sharing recovery secrets
Support guidance never requires seed phrases, private keys or verification codes.
FAQ
Common questions before you act
A wallet manages keys and presents on-chain information. Assets remain recorded on their respective blockchain networks.
The same address format can appear across different networks, while balances and transaction states remain network-specific.
Gas is the fee mechanism used to pay for transaction execution on a network; it is separate from the transferred amount.
A transaction hash is an identifier you can use to look up on-chain status, block inclusion and confirmations.
No. A connection is not blanket approval. Review every signature, approval and transaction independently.
No. Seed phrases, private keys and verification codes should never be sent to anyone.
It is permission granted to a spender contract to use tokens within a defined scope or amount.
No. Rewards can change, exits may involve waiting, and validator, contract and market risks exist.
Use imtoken with a clear network and security checklist
Keep recovery secrets private, verify the network and destination, and review signatures or approvals before confirming.