Create a Wallet
Understand account control and recovery responsibility before creating a new wallet.
Read guide →imtoken
Manage Multi-chain Assets and Connect to Web3 with Clarity
A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken
Use one clear learning path for multi-chain assets, network selection, sending and receiving, DApp connections, token approvals and wallet security. The goal is to understand what a request means before you sign or submit it—not to depend on a familiar-looking interface.
Back Up a Wallet
Keep the seed phrase offline and out of screenshots, cloud drives and messages.
Read guide →Receive Assets
Confirm the receiving network before sharing an address with the sender.
Read guide →Send Assets
Review the address, network, amount, gas and transaction details before signing.
Read guide →Connect to a DApp
Verify the domain and account scope, then treat each signature and approval separately.
Read guide →Wallet capabilities organized around real tasks
A wallet is more than an asset list. Network identity, addresses, transaction state, contract permissions and recovery information all affect what an action means on-chain.
Multi-chain Assets
Compare network identity, native gas and confirmation behavior before switching chains.
Send & Receive
Review address, network, amount, gas and transaction hash as one connected workflow.
imtoken App
View assets, manage networks, review transaction history and enter DApp workflows from mobile.
imtoken Web
Separate public account access from signatures, token approvals and disconnection. A prior connection is not permission to approve every later request.
Wallet Security
Keep recovery information offline, and review approvals, signatures and transfers as distinct decisions.
Explore blockchain networks
Public chains, EVM networks and Layer 2 systems can share address formats or asset names while keeping separate chain state, gas assets and confirmation paths.
Multi-chain Networks
Use network identity, native gas, address behavior and confirmations to identify the chain context.
Read topic →Public Chains
Nodes, blocks, transactions and consensus create publicly verifiable chain state.
Read topic →
EVM Networks
EVM-compatible chains share execution patterns while balances, gas assets and contracts remain network-specific.
Read topic →
Layer 2
Learn the base-layer relationship, bridge path, confirmation process and possible exit delay.
Read topic →
Gas & Confirmations
Interpret fees, broadcasts and confirmation state together with the target network and transaction hash.
Read topic →A six-step wallet path
Separate acquisition, account creation, backup, network verification, transfers and permission maintenance so every stage can be reviewed independently.
Get imtoken
Use the common download entry point rather than installation links from unknown messages.
Create or Import a Wallet
Know whether you are creating a new account or restoring an existing one.
Back Up Offline
Keep seed phrases and private keys offline and never send them to another person.
Select and Verify the Network
Confirm the destination chain, address context and native gas asset.
Receive or Send Assets
Review address, network, amount and fees, then retain the public transaction hash.
Review Transactions and Approvals
Verify transaction state and periodically remove permissions that are no longer needed.
Web3 & DApps
Treat every connection, signature and approval as a separate decision
Verify the DApp domain before connecting. A connection establishes account context, but later message signatures, transaction signatures and token approvals still need individual review.
Security note: Connecting a wallet does not mean every signature request should be accepted. Review each signature and approval independently.
Open the Web3 guide →Visit a DApp
Verify the domain
Start the connection
Review account access
Check the signature or approval
Complete the action
Disconnect unused sessions
Security
Security begins with controlling your keys and verifying every request
Seed phrases and private keys stay under user control, and official staff should never request them. Check address, network and amount before a transfer; check the domain, signature meaning and approval scope before a DApp action. On-chain transactions generally cannot be unilaterally reversed by a wallet, so pre-confirmation review matters more than recovery promises.
Open Security CenterBack up the seed phrase offline
Never disclose private keys
Verify network and address
Review signature requests
Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
An address identifies an on-chain account; seed phrases and private keys relate to account control; the network determines where assets and transactions exist; gas represents execution cost; a transaction hash provides public verification; and DApps extend wallet use through connections, signatures and approvals. Understanding those relationships makes unexpected requests easier to detect.
Read Getting Started →Ethereum and Proof of Stake
Validators participate in Ethereum PoS consensus. Rewards, withdrawals, exits, waiting periods and penalties are shaped by protocol rules and network conditions, so mechanism should be understood before return expectations.
Ethereum Staking Fundamentals
Learn validator responsibilities, reward sources, withdrawal mechanics, exit flow and possible waiting periods.
Learn more →Before Participating
Staking does not guarantee returns. Validator penalties, smart-contract risk, third-party service risk, exit delays and asset-price volatility all matter.
PoS & Validators →Product and security updates
Notices are organized by product, network, security and service. When there is no verified date, the site uses descriptive labels rather than inventing dates, partnerships, funding claims or market statistics.
Recent UpdateWallet and network content is organized around real tasks so users can move directly from a problem to the relevant guide.→NetworkRe-check network, address and gas before cross-network activity instead of inferring the chain from an asset name.→SecurityA connected wallet still requires a fresh review of each signature request.→ServiceStaking material separates protocol mechanics, exit flow and risks without fixed-return promises.→
Frequently asked questions
Find clear answers about account control, networks, transaction confirmation, DApp permissions and PoS risk.
A digital wallet manages on-chain accounts, addresses, key-controlled signing and transaction requests; the assets themselves are recorded on blockchain networks.
Prefer offline storage and avoid screenshots, cloud drives and chat messages. Never send it to another person.
The same asset name or address format can exist across different chains, while balances and transaction state remain network-specific.
Gas measures computational resources used by transactions or contract execution, with cost affected by network conditions and transaction complexity.
No. A connection can be followed by separate message signatures, transaction signatures and token approvals, each requiring its own review.
No. Rewards can change and participation can involve validator penalties, contract risk, exit delays and asset-price volatility.
imtoken
Continue with the product—or learn first
Use the common download entry point when ready, or start with wallet basics, network knowledge and security guidance.