Create a Wallet
Understand creation and import before generating new credentials.
Open guide →imtoken · Web3 Knowledge & Wallet Security
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 organization, network selection, receiving and sending, transaction history, DApp connections and approvals. The surrounding knowledge center explains how networks, gas, signatures, smart contracts and wallet security fit together so every action can be reviewed before it is approved.
Multi-chainEVMLayer 2DAppPoS
Back Up a Wallet
Keep seed phrases offline and never send them to another person.
Open guide →Receive Assets
Match the receiving address with the network and asset.
Open guide →Send Assets
Review the address, network, amount and gas before signing.
Open guide →Connect to a DApp
Verify the domain and inspect every signature or approval independently.
Open guide →Wallet capabilities
Move between assets, networks and Web3 with a clear mental model
A wallet is not only a balance screen. It is where you choose networks, review addresses, inspect transaction details and decide whether a DApp request should be signed or approved.
Multi-chain assets
Separate assets by network, confirm native gas assets and read confirmation state.
Send & Receive
Review receiving addresses, networks, amounts, gas and transaction hashes.
imtoken App
Mobile access to network management, asset views, transaction history and DApp use.
imtoken Web
Browser connections require the same care with domains, approvals and disconnection.
Wallet security
Keep seed phrases and private keys under your own control; review every approval.
Blockchain networks
Explore networks by how they affect real wallet actions
Network choice changes where the transaction is sent, which native asset pays gas, how confirmations are observed and how a bridge or Layer 2 transfer should be interpreted.
Multi-chain
Different chains can use similar address formats while maintaining separate transaction histories and gas assets. Always confirm the active network before sending.
Read the guide →Public Chains
Different chains can use similar address formats while maintaining separate transaction histories and gas assets. Always confirm the active network before sending.
Read the guide →
EVM
Different chains can use similar address formats while maintaining separate transaction histories and gas assets. Always confirm the active network before sending.
Read the guide →
Layer 2
Different chains can use similar address formats while maintaining separate transaction histories and gas assets. Always confirm the active network before sending.
Read the guide →
Gas & Confirmations
Different chains can use similar address formats while maintaining separate transaction histories and gas assets. Always confirm the active network before sending.
Read the guide →Usage path
Six steps from setup to ongoing review
The path emphasizes offline backup, network and address checks, reading DApp requests, and periodic approval review.
01
Get imtoken
In real use, get imtoken often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
02
Create or import a wallet
If the result does not match your expectation, avoid repeating the same action immediately. Save the transaction hash and inspect it on a block explorer for the correct network to see whether it was broadcast, succeeded and reached confirmation. On-chain transactions are usually not something a wallet can unilaterally reverse, so checks before action matter more than recovery promises after the fact.
03
Back up offline
For Usage path, it is useful to distinguish the wallet, the blockchain network and any third-party DApp. A contract can introduce code, permission and operational risks. imtoken staff will never ask for a seed phrase or private key and should not be treated as an entity that can recover those credentials for the user.
04
Choose and verify the network
Long-term habits are more useful than memorizing a button. For choose and verify the network, consistently review the address, network, amount or requested permission, and check whether old connections or approvals are still needed. Shared computers, remote-control sessions and untrusted network environments deserve extra caution.
05
Receive or send assets
The purpose of this material is not to promise returns or absolute safety. It is to make each on-chain action easier to reason about. Signing, approving, bridging or using validator-related services can involve network conditions, contract risk, waiting periods and market volatility, so participation should always be an independent decision.
06
Review transactions and approvals
When thinking about review transactions and approvals, separate the network, address, signature and transaction state. A wallet interface helps organize information, but the authoritative asset state is recorded by the relevant blockchain. Before acting, confirm that the selected network matches the asset and destination, and do not rely on names or icons alone to identify a token.
Web3 & DApp
Connection is only the beginning of the review
Connecting a wallet does not mean every later request should be accepted. Treat each signature and approval as a separate decision.
Open Web3 guide →Visit the DApp
In real use, visit the dapp often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Verify the domain
In real use, verify the domain often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Start connection
In real use, start connection often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Review account request
In real use, review account request often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Inspect signature or approval
In real use, inspect signature or approval often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Complete the action
In real use, complete the action often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Disconnect when no longer needed
In real use, disconnect when no longer needed often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Security
Self-custody starts with clear boundaries
Seed phrases and private keys are controlled by the user. imtoken staff will not ask for them. Avoid cloud screenshots, fake support, suspicious airdrops, remote-control requests and unreviewed approvals. Before a transfer, verify the address, network and amount. Remember that blockchain transactions are usually not reversible by the wallet provider, and third-party DApps and smart contracts can introduce additional risk.
Open Security Center →Back up the seed phrase offline
Never disclose private keys
Check network and address
Inspect signature requests
Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
Before the first transfer, learn what an address represents, why the seed phrase and private key matter, how networks and gas affect transactions, what a transaction hash can prove, and why DApp signatures and approvals need their own checks.
Start the guide →Ethereum · PoS
Understand the mechanism before considering participation
Staking content focuses on PoS, validators, reward sources, network state, withdrawals, exits, waiting periods, penalties and smart-contract risk without presenting fixed returns.
Ethereum Staking Basics
Validator rewards depend on protocol conditions and participation; they can change. Exit and withdrawal can involve waiting, and validators can be penalized by the network.
Read basics →Understand before participating
Smart-contract risk, third-party service risk and digital-asset price volatility remain relevant. Staking does not guarantee returns.
Learn about validators →Updates
View all updates →Product, network, security and service notices
Recent Update · ProductClarifying network and asset checks across wallet views.Details →
Recent Update · NetworkA reminder to verify the destination network before transfers.Details →
Recent Update · SecurityReview old DApp approvals and revoke what is no longer needed.Details →
Recent Update · ServiceStaking and validator materials now emphasize waiting and penalty risk.Details →
FAQ
Full FAQ →Common questions before you act
No. imtoken staff will not ask for your seed phrase, private key or verification code. Keep them under your own control.
Networks are separate ledgers. A matching-looking address does not mean the destination or asset route is correct.
Gas is the execution fee mechanism used by many networks. It is usually paid in the network’s native asset and can vary with demand.
It identifies a transaction on a specific network and can be used to inspect broadcast, execution and confirmation status on a block explorer.
No. Every signature and token approval should be reviewed separately.
No. Rewards can change, exits can involve waiting, validators can face penalties, and market and contract risks remain.
imtoken
Start with understanding, then act
Use the download entry only when you are ready, and keep your credentials under your own control.
Download imtoken