Create a Wallet
Understand wallets, addresses and recovery credentials before creating a new wallet environment.
View steps →imtoken · Multi-chain Wallet & Web3 Knowledge Hub
Manage Multi-chain Assets and Connect to Web3 with Clarity
A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken
From multi-chain asset views, network selection, sending and receiving to DApp connections, signatures and approvals, imtoken organizes wallet actions around details you can verify. The knowledge center also covers public chains, EVM, Layer 2, gas, transaction confirmations and wallet security so each decision is grounded in clear context.
Back Up a Wallet
Record the seed phrase offline and verify it independently without sending it through chat, email or cloud notes.
View steps →Receive Assets
Confirm the receiving address and network, and use a small test when the route or counterparty is unfamiliar.
View steps →Send Assets
Review the address, network, amount and gas, then track the transaction with its public hash.
View steps →Connect to a DApp
Verify the domain and account request before reviewing each signature or token approval separately.
View steps →Wallet capabilities built around verifiable actions
Asset display is only the starting point. The more important skill is understanding the network an asset belongs to, how a transaction confirms, and what signatures or approvals can change.
Multi-chain assets
The same address format may appear on different networks, while balances, fee assets and transaction status remain chain-specific. Confirm the network before relying on an address or token label.
imtoken App
The mobile experience brings together asset views, network management, transaction history and DApp connections. Every signature and approval should still be reviewed on its own.
Send & receive
For receiving, verify the network and address. For sending, add amount and gas checks, then use the transaction hash to inspect the on-chain state.
imtoken Web
Browser connections focus on account requests, network changes and approval review. Disconnect connections you no longer use and revisit persistent permissions.
Wallet security
Seed phrases and private keys remain under the user's control. Offline backups, device protection and approval hygiene work together as long-term safety practices.
Explore blockchain networks
A network label affects gas, block confirmations, contract addresses and the path an asset follows.
Multi-chain does not mean every network is identical
Each network has its own blocks, fee assets and transaction states. Even when address formats match, the selected chain still determines the actual asset state.
Public chains maintain state through distributed nodes
A transaction is broadcast, processed, included in a block and then followed by later confirmations. Block explorers expose these public records.
EVM links accounts, gas and smart contracts
EVM networks share many account and contract concepts, but chain IDs, gas conditions and contract addresses still need separate verification.
Layer 2 has a defined boundary with mainnet
Cross-layer movements may involve bridges, waiting periods and confirmations on both sides. A mainnet balance and a Layer 2 balance are not the same chain state.
Gas and confirmations describe different parts of a transaction
Gas represents network resource cost, while confirmations describe how later blocks continue to build on a recorded transaction. Waiting time can change with network conditions.
A complete path from setup to approval review
Each step pairs the next action with the details worth checking.
Get imtoken
Use the official download entry rather than an unknown installation link.
Create or import a wallet
Confirm the environment and understand how recovery credentials control the wallet.
Back up offline
Keep the seed phrase offline, avoid screenshots, and never hand it to a person claiming to be support.
Select and verify the network
Check the target network, its fee asset and address context instead of guessing from the token name.
Receive or send assets
Verify network details when receiving and review address, network, amount and fees before sending.
Review transactions and approvals
Use transaction hashes for on-chain verification and periodically review DApp approvals you no longer need.
Web3 & DApps
Treat every connection, signature and approval as a separate decision
Connecting a wallet establishes account communication; it does not mean every later request is appropriate. Signatures, transactions and token approvals can have different outcomes and should be reviewed one by one.
Open the Web3 guide →- Visit the DApp
- Verify the domain
- Start the connection
- Review the account request
- Check the signature or approval
- Complete the action
- Disconnect connections you no longer need
Connecting a wallet does not mean you should accept every signature request. Review each signature and approval independently.
Security
Separate recovery secrets, on-chain permissions and device risk
Wallet security is a set of habits rather than a single switch. Seed phrases and private keys control accounts and should remain under the user's custody with offline backups preferred. DApp connections, signatures and approvals are on-chain permissions that should be checked for target, scope and meaning. Before a transfer, review the address, network and amount; afterward, verify the public transaction hash. Public Wi-Fi, shared computers, remote-control tools and clipboard manipulation can change the operating environment, so important actions should be performed on trusted devices and networks. Official personnel will not ask for a seed phrase or private key, and no one should receive your recovery phrase or verification code. Third-party DApps and smart contracts can carry risk, and unused approvals should be reviewed for revocation.
Open Security Center →- Back up seed phrases offline
- Never disclose private keys
- Verify network and address
- Review signature requests
- Manage DApp approvals
Academy
Start with wallets and addresses, then move through networks, gas, DApps and approvals in the order users encounter them.
Featured beginner guide
What Should You Understand Before Using a Digital Wallet?
An address is public information for receiving assets, while seed phrases and private keys control account access. A network determines where a transaction is processed, gas represents network resource cost, and a transaction hash lets you inspect the result. DApps add message signatures, transaction signatures and token approvals, each with distinct permissions and consequences. Understanding these boundaries is a strong first step before using a wallet.
Read the full guide →
NetworksPublic Chains & ConfirmationsLearn how nodes, blocks and confirmations describe transaction state.Smart ContractsEVM & Smart ContractsUnderstand addresses, gas, tokens and approvals.ScalingLayer 2 BasicsSeparate mainnet, Layer 2 and cross-layer asset paths.Web3 SecurityDApp ApprovalsReview spenders, allowance scope and persistent permissions.SecurityWallet SecurityBuild backup, device and transfer-check habits.GlossaryBlockchain GlossaryLearn common wallet and on-chain terms.
Ethereum & PoS knowledge
Start with validators and reward sources, then account for exits, waiting periods, penalties and technical risk.
Ethereum Staking
Ethereum staking basics
Ethereum PoS uses validators to participate in block proposal and attestation. Rewards can vary with protocol rules and validator status, while exits and withdrawals may involve waiting. Staking should not be treated as a fixed-return product.
Learn staking basics →Product & security updates
No fabricated dates, partnerships or market claims—only guidance related to product use, network awareness and security education.
Wallet action checklist
View →A consolidated review of setup, backup, sending, receiving and transaction lookup steps.
Network selection and asset arrival
View →Why matching address formats do not imply assets are on the same network.
Review signatures and approvals individually
View →A DApp connection never replaces review of later signature or approval requests.
Multi-chain asset display
View →How displayed assets relate to token contracts and on-chain balances.
Frequently asked questions
Common questions covering wallets, networks, transactions, DApps, security and PoS.
Both relate to account control and should never be shared. A seed phrase often restores a set of accounts, while a private key controls a particular account.
Assets are processed by a specific network. A wrong network can place the result on a different chain from the one you expected.
Gas generally represents the blockchain network resources required to process an action, and the amount can change with network conditions and complexity.
It is a public identifier you can use in the relevant block explorer to inspect status, block inclusion and confirmations.
No. A connection usually establishes account communication. Token approvals and transaction signatures are separate requests.
Some approvals remain active. Review and revoke permissions that are no longer needed based on your current use.
No. They are separate chain states, and moving assets between them may involve bridging and waiting periods.
No. Rewards, validator status, exit timing, penalties, smart-contract risks and asset prices can all change.
imtoken
Start multi-chain asset management with a clear first step
The download entry always leads to the dedicated download page. Review backup and transaction-check guidance before using a wallet.