Create a Wallet
Create or import an account in a trusted environment, then confirm the active network.
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
Understand multi-chain assets, network selection, sending and receiving, DApp connections, approvals, network knowledge and wallet security in one clear learning path.
Start with the task in front of you
Five common actions, each with the verification point that matters most.
Back Up a Wallet
Write down recovery material offline and never send it through chat or cloud storage.
Read guide →Receive Assets
Confirm receiving network and address before sharing it.
Read guide →Send Assets
Verify destination, network, amount and fee before signing.
Read guide →Connect to a DApp
Check the domain, account request, signature and approval scope separately.
Read guide →Wallet capabilities organized by use
Asset management, mobile use, browser connections and security have different roles and deserve different emphasis.
Assets across networks
Compare networks, verify addresses and understand confirmations before moving assets.
imtoken APP
View assets, manage networks and review transaction history.
imtoken Web
Review account requests, approvals and session state in the browser.
Protect control, not just the screen
Keep recovery material offline, review signatures and manage persistent DApp permissions.
Explore blockchain networks
Compare what each concept changes in practice.
Multi-chain
Multi-chain
A multi-chain wallet can interact with several networks, but balances, histories and fees remain network-specific.
Learn more →
Public Chains
Public Chains
Public chains use distributed nodes, blocks and consensus rules to maintain a shared ledger.
Learn more →
EVM
EVM
EVM networks share a contract execution model, while balances and approvals remain network-specific.
Learn more →
Layer 2
Layer 2
Layer 2 processes more activity away from mainnet and can involve extra bridging and withdrawal stages.
Learn more →
Gas & Confirmations
Gas & Confirmations
Gas is a network resource cost; fees and confirmation time change with demand and transaction complexity.
Learn more →A six-step wallet path
Security checks stay inside the workflow rather than being added later.
01
Get imtoken
Use the official download entry and avoid unknown mirrors.
02
Create or import a wallet
Use a trusted environment and confirm the selected account.
03
Back up offline
Keep the seed phrase offline and never disclose private keys.
04
Choose and verify the network
Confirm the network before transfers or contract interactions.
05
Receive or send assets
Verify address, amount and network fee before signing.
06
Review transactions and approvals
Track by transaction hash and revoke permissions you no longer need.
Web3
Use DApps one request at a time
A connection is only the beginning; each signature and approval has its own purpose and risk.
Connecting a wallet does not mean every signature request should be accepted. Review each signature and approval independently.
Visit the DApp
Open the intended service from a trusted entry point.
Confirm the domain
Check spelling and context before connecting.
Start a connection
Review the account and network request.
Review account requests
Only expose what is needed.
Check the signature or approval
Read each request independently.
Complete the action
Confirm expected on-chain effect.
Disconnect when finished
Close unused sessions and review persistent approvals.
Security
Protect the wallet by protecting each decision
Wallet security comes from private recovery material, verified destinations, reviewed permissions and a controlled device and network. Confirmed transactions are normally not reversible by the wallet alone.
Open the security center →- Keep seed phrases offline
- Never disclose private keys
- Verify network and address
- Review signature requests
- Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
Learn addresses, seed phrases, private keys, networks, Gas, transaction hashes, DApps and approvals as one connected model.
Read the full guide →Public chains and confirmations
How nodes, blocks and confirmations describe transaction state.
EVM and smart contracts
Why Gas, contract methods and approvals matter.
Layer 2 basics
How Layer 2 relates to mainnet and bridges.
DApp approvals
Understand spenders, limits and revocation.
Wallet security
Protect recovery material and review every request.
Blockchain glossary
Plain-language explanations of common terms.
Ethereum and proof of stake
Learn mechanics, exits, penalties and technical risk before considering participation.
Ethereum staking basics
Rewards depend on protocol conditions and are not fixed or guaranteed.
Read basics →Before participating
Validator penalties, waiting time, smart-contract risk, third-party services and asset-price volatility can all affect outcomes.
Understand validators →Product and security updates
Content-first notices without invented dates, partnerships or market claims.
Product Notice
Wallet workflow
Review the network before asset actions.
Security Notice
Recovery material
Keep seed phrases and private keys offline.
Network
Confirmation status
Use the transaction hash to check on-chain status.
Service
Approval review
Revoke permissions you no longer need.
Frequently asked questions
Short answers for common wallet, network and security decisions.
A digital wallet manages addresses and keys, reads on-chain assets, and builds or signs transactions. The asset record lives on the blockchain rather than simply inside an app interface.
No. Seed phrases and private keys should remain under your control, and official support should not request them.
A private key controls a specific account, while a seed phrase commonly restores a set of derived keys. Both are highly sensitive.
Assets can exist on different networks. The network determines where a transaction is executed, so sender and receiver must agree on the intended network.
Gas represents computation and storage used by on-chain execution. Actual fees vary with network conditions and transaction complexity.
It is the main reference used to look up transaction status, fees and contract calls in a block explorer.
A connection only opens an interaction channel. Every later signature, approval and transaction should still be reviewed independently.
No. A message signature may authorize login or another off-chain flow, while a transaction signature normally submits an on-chain state change.
Ready to start with imtoken?
Use the single download entry, then complete wallet setup, backup and security checks before moving assets.