Create a Wallet
Understand wallets, addresses and keys before creating a new wallet environment on a trusted device.
Learn the basics →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 asset awareness and network selection to sending, receiving, DApp connections, signatures, approvals and wallet security in one clear learning path. Understand addresses, networks and transaction confirmations before interacting with contracts, and treat key protection and request review as part of every action.
Back Up a Wallet
Keep your seed phrase offline. Avoid screenshots, cloud copies and sharing it with anyone.
Backup principles →Receive Assets
Check both the receiving address and the network instead of relying on the token name alone.
Receiving steps →Send Assets
Review address, network, amount and gas before signing; use the transaction hash afterward.
Sending checks →Connect to a DApp
A connection is not blanket consent. Review each signature and approval request separately.
Connection guide →Wallet capabilities
Keep assets, networks and security in one operational path
A multi-chain wallet can organize information across networks, but it does not merge those networks. Safer use comes from knowing where an action takes place, which address or contract it involves, and what a signature will change.
Multi-chain assets
Separate the network, asset and address context. Switching networks does not move assets across chains.
Understand multi-chain use →imtoken App
View assets, manage networks, review transaction history and inspect DApp requests from a mobile environment.
Explore the App →Send & Receive
Check addresses and networks when receiving; review amount, gas and transaction details when sending.
View the flow →imtoken Web
Understand browser connections, account requests, signatures, approvals and disconnecting sessions.
Web guide →
Wallet security
Seed phrases and private keys stay under the user’s control. Legitimate support should never ask for them.
Open Security →Blockchain networks
Check the network before judging fees or arrival
Different chains have independent nodes, blocks, gas and confirmation rules. A similar-looking address does not make assets directly interchangeable across networks.
Multi-chain networks
Identify where an asset is located and where the destination expects it. Switching networks changes context; it does not bridge an asset.
Learn more →Public chains
Nodes maintain shared state, transactions enter blocks and confirmations increase as the chain advances.
Public-chain basics →
EVM networks
Similar account and contract models do not make separate EVM networks interchangeable. Check both network and contract.
EVM guide →
Layer 2
Learn how Layer 2 relates to mainnet, how bridging works and why exits or confirmations can involve waiting.
Layer 2 basics →
Gas & confirmations
Gas varies with network conditions and execution complexity. Check the original transaction hash before resubmitting.
Fees and confirmations →Usage path
Build six repeatable habits
Each step prepares for the next: control the keys first, understand the network, then receive, send and interact with Web3.
01
Get imtoken
Use a trusted entry point and start the download yourself rather than relying on unsolicited links.
02
Create or import a wallet
Use a trusted device and avoid public computers, screen sharing or unknown remote-control sessions.
03
Back up offline
Store the seed phrase offline and never disclose private keys, recovery words or verification codes.
04
Select and verify the network
Confirm where the asset actually lives and which network the destination supports.
05
Receive or send assets
Review address, network, amount and gas. Use a small test when learning a new route.
06
Review transactions and approvals
Use transaction hashes for on-chain status, inspect DApp requests and remove permissions you no longer need.
Web3 & DApps
A connection is only the beginning
A site connection may expose an account for interaction, while later signatures, approvals and transactions can have very different consequences. Stop when a request is unclear.
Connecting a wallet does not mean every signature request should be accepted. Review every signature and approval on its own.
Visit the DApp
Use a trusted path.
Verify the domain
Check spelling and context.
Start the connection
See which account is requested.
Review account access
Expose only what is needed.
Inspect signature or approval
Check network, address, contract and permission.
Complete the action
Verify the result on-chain.
Disconnect when finished
Review stale approvals later.
Security
Make key protection and request review the default
Wallet security is a continuous practice across creation, backup, transfers and Web3 interactions. Keep seed phrases and private keys under your own control; legitimate support should never ask for them or for verification codes. Review the address, network and amount before transferring. Inspect the target and permission scope before signing or approving. Remove permissions that are no longer needed. Third-party DApps and smart contracts carry separate risk, while public devices, public networks and remote-control tools can increase exposure. On-chain transactions usually cannot be reversed by a wallet provider, so pre-transaction review matters more than promises of recovery.
Open SecurityBack up seed phrases offline
Never disclose private keys
Check network and address
Review signature requests
Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases, private keys and networks, then move to gas, transaction hashes, DApps and token approvals. With those concepts in place, questions about missing assets, confirmations and unfamiliar signature prompts become easier to diagnose.
Read the beginner path →Public Chains & Confirmations
Blocks, confirmations and explorers.
EVM & Smart Contracts
Gas, contracts and tokens.
Layer 2 Basics
Mainnet, bridging and waiting.
DApp Approvals
Targets, allowances and review.
Blockchain Glossary
Find essential terms quickly.
Ethereum & PoS
Understand the mechanism before deciding whether to participate
Staking content explains protocol mechanics, validators, exits, waiting and risk without presenting historical rewards as fixed returns.
Ethereum Staking Basics
Ethereum PoS uses validators in consensus. Reward sources and network conditions can change, while entry and exit can involve waiting.
Understand staking →Know Before Participating
Validators may face network penalties. Smart contracts can fail, digital-asset prices can move and third-party services add separate risks.
Understand validators →Updates
Product, network, security and service notices
When no verified date is available, notices use non-fabricated labels and never invent partnerships, licenses, user counts, trading volume or market rankings.
Wallet usage path
A clearer route across creation, backup, network selection, transfers and transaction review.
Confirmations and congestion
Check the transaction hash before repeating an action during periods of network congestion.
Signature and approval review
Every signature and approval should be evaluated separately after connecting to a DApp.
Self-service checks
Review network, transaction hash, contract and approvals without submitting sensitive credentials.
FAQ
Start with the questions users ask most often
The full FAQ covers wallets, networks, gas, DApps, security, Ethereum PoS and validators.
No. Seed phrases and private keys stay under the user’s control. Legitimate support should never ask for them.
Some networks use similar account formats, but assets remain separate on each network. Always verify the selected network.
Gas measures resources used by on-chain execution. Fees vary with network conditions and transaction complexity.
No. Connections, signatures, token approvals and transactions are separate actions.
Usually not by the wallet alone. Review address, network, amount and request details before signing.
No. Rewards can change and participation involves waiting, network penalties, contract risk and market volatility.
Get started
Download imtokenUse a trusted entry point for imtoken
Downloads are user initiated. Review backup, network and transaction-check principles before you begin.