Create a Wallet
Understand what a new wallet creates and which secrets must be protected before receiving assets.
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 imtoken to understand multi-chain asset management, network selection, sending and receiving, DApp connections, token approvals, blockchain concepts, and wallet security. Every action should be verified against the intended network, address, request origin, and permission scope.
Multi-chain assetsEVMLayer 2DAppApproval security
Start with the task you need
Move from setup to transfers and Web3 with clear checks at each step.
Back Up a Wallet
Build an offline backup habit and keep seed phrases away from screenshots, cloud notes and messages.
Read guide →Receive Assets
Verify the receiving address and network before another party sends assets to your wallet.
Read guide →Send Assets
Check destination, network, amount, gas and transaction details before confirming a transfer.
Read guide →Connect to a DApp
Verify the domain, account request, signature content and approval scope before continuing.
Read guide →Wallet capabilities built around real actions
Assets, networks, transactions, Web3 and security are related parts of one wallet workflow.
Multi-chain assets
Understand how assets are separated by network, why addresses must be checked in context, and how confirmations affect final transaction state.
imtoken APP
Review assets, manage networks, inspect transaction history and prepare DApp actions from a mobile wallet interface.
Send & receive
Check receiving addresses, network selection, amount, gas and transaction hash throughout the transfer lifecycle.
imtoken Web
Use browser connections carefully: verify the site, review permission requests and disconnect sessions that are no longer needed.
Wallet security
Keep seed phrases and private keys under your own control, prefer offline backups, and review signatures and token approvals before confirming.
Explore blockchain networks
Switch between network topics without hiding the underlying content when scripts are unavailable.
Multi-chain
Different networks maintain independent state. Verify the network before reading balances or moving assets.
Learn more →Public Chains
Nodes, blocks, consensus and explorers provide the foundation for checking transaction state.
Learn more →
EVM
EVM networks share familiar contract patterns while maintaining separate gas and asset state.
Learn more →
Layer 2
Layer 2 systems extend execution while cross-layer transfers may use bridges and waiting periods.
Learn more →
Gas & Confirmations
Fees, mempool conditions and block confirmation affect how a transaction progresses.
Learn more →A six-step wallet path
Each step adds a verification habit before the next action.
Get imtoken
Start from the official download entry and avoid installation packages from unknown sources.
Create or import a wallet
Understand the difference between creating and importing, and never submit a seed phrase or private key to a webpage.
Back up offline
Keep the seed phrase offline. Do not send it to anyone or rely only on screenshots or cloud notes.
Choose and verify the network
Before receiving or sending, check the network name, address context and the network supported by the other party.
Receive or send assets
Review the address, amount, network and gas before confirmation, using a low-risk check when appropriate.
Review transactions and approvals
Use the transaction hash to inspect on-chain state and periodically review DApp approvals that are no longer needed.
Web3
Review every DApp request on its own
Connecting a wallet does not mean every signature or approval should be accepted. Verify the domain, account, request purpose, contract target and permission scope before moving forward.
A wallet connection is not blanket permission. Treat each signature and approval as a separate decision.
- Visit the DApp
- Verify the domain
- Start connection
- Review account request
- Inspect signature or approval
- Complete the action
- Disconnect unused sessions
Security is a sequence of checks
Keep seed phrases and private keys under your own control. Do not send them, screenshots of them, or verification codes to anyone. Before a transfer, verify the address, network and amount. Before a DApp signature, verify the source and requested action. Third-party DApps and smart contracts can introduce technical or permission risks, so approvals should be limited to what is actually needed and reviewed again when no longer in use.
Visit Security Center →- Back up seed phrases offline
- Never disclose private keys
- Verify network and address
- Inspect signing requests
- Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases, private keys, networks, gas, transaction hashes, DApps and approvals. These concepts explain most of the information a wallet asks you to review.
Read the beginner guide →Public chains and transaction confirmation
See how blocks, nodes and confirmations shape transaction state.
EVM and smart contracts
Understand gas, contract execution and token approvals.
Layer 2 fundamentals
Learn how cross-layer transfers and settlement differ from a single-network transfer.
DApp approval safety
Review approval targets, allowance scope and revocation habits.
Blockchain glossary
Use concise definitions for common wallet and network terms.
Ethereum and proof of stake
Understand the mechanism and risks before evaluating any staking service.
Ethereum Staking basics
Ethereum proof of stake uses validators to participate in consensus. Reward sources, validator state, withdrawals and exits depend on protocol conditions and network queues.
Learn staking basics →Know the risks before participating
Staking does not guarantee returns. Rewards can change, exits can involve waiting, validators may face penalties, smart contracts can have technical risk, and digital asset prices can fluctuate.
Understand validators →Product and security updates
Notices are organized by purpose without invented publication dates.
Product
→Wallet task navigation refined for clearer learning paths.
Network
→Review network selection before moving assets between ecosystems.
Security
→Recheck active token approvals and disconnect unused DApp sessions.
Service
→Staking materials emphasize variable rewards, exits and validator risk.
Product
→Academy content links wallet actions to network and transaction concepts.
Frequently asked questions
Short answers to core wallet, network, Web3 and security questions.
A digital wallet manages the relationship between addresses, keys, and on-chain actions. The interface can display balances and history, while the authoritative asset state lives on the relevant blockchain network.
A seed phrase can often restore a set of wallet accounts, while a private key directly controls signing for a specific address. Both are highly sensitive and should remain under the user’s control.
Assets with similar names can exist on different networks. Before sending, make sure the sending network matches the network supported by the destination.
Gas measures the computational resources required for on-chain execution. The actual fee depends on network rules, congestion, and transaction complexity.
A transaction hash identifies a specific on-chain transaction and can be used with the relevant block explorer to inspect status, confirmations, and execution results.
No. Connecting usually establishes account access. Signatures and token approvals are separate requests and should be reviewed individually.
A signature may simply prove account control, or it may authorize a transaction or permission. Verify the origin, content, and expected outcome before signing.
Many token approvals on EVM networks can be changed or revoked through an on-chain transaction. This normally requires network fees and careful verification of the approval contract.
Continue with imtoken
Review the download information and proceed only when you choose to.