Create a Wallet
Understand what a wallet controls before creating a new one.
Learn more →imtoken
Manage Multi-chain Assets and Connect to Web3 with Clarity
A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken
Manage assets across multiple networks, understand network differences before a transfer, inspect addresses and fees, connect to DApps with explicit permission checks, and build habits for wallet security. imtoken brings product usage and network knowledge into one practical path.
Quick paths
Start from the task you need
Each task starts with the checks that matter before an on-chain action.
Back Up a Wallet
Keep seed phrases offline and verify your backup process.
Learn more →Receive Assets
Confirm the receiving address and network before sharing it.
Learn more →Send Assets
Review address, network, amount and gas before confirming.
Learn more →Connect to a DApp
Verify the domain and review every request independently.
Learn more →Wallet capabilities
Wallet functions in real network contexts
Multi-chain assets
Compare networks, check addresses and understand confirmations before moving assets.
imtoken APP
Use the mobile wallet to manage networks, view assets and inspect transaction history.
Send & Receive
Address, network, amount, gas and transaction hash form one complete verification chain.
Read the guide →imtoken Web
Browser connections should keep account requests, approvals and disconnecting clearly separated.
Learn about Web access →Wallet security
Keep seed phrases and private keys under your own control, and review approvals that are no longer needed.
Blockchain networks
Explore networks by the decision you need to make
Multi-chain is about context, not just more assets
The same wallet can interact with multiple networks. Always identify the active chain before interpreting balances, addresses or transaction state.
Explore multi-chain concepts →Nodes, blocks and confirmations
Public chains record transactions through network rules that can be inspected with block explorers.
EVM addresses, gas and contracts
EVM-compatible networks can look similar while remaining separate chains with different gas assets and state.
Layer 2 and mainnet relationships
Cross-layer transfers may involve bridges, waiting periods and different confirmation rules.
Fees are only one part of confirmation
Gas, congestion, block inclusion and contract execution all influence the final result.
Understand confirmations →Usage path
A repeatable six-step wallet path
01
Get imtoken
Use the unified download entry and keep the package source clear.
02
Create or import a wallet
Understand whether you are creating new control or restoring existing control.
03
Back up offline
Keep the seed phrase offline and never disclose the private key.
04
Choose and verify the network
Check the network before interpreting an address or balance.
05
Receive or send assets
Review destination, amount, gas and network before confirmation.
06
Review transactions and approvals
Keep the transaction hash and remove approvals you no longer need.
Web3 & DApp
Treat every request as a separate decision
Connecting a wallet does not mean you should accept every signature or approval that follows.
Check the domain, account, network, contract and permission scope before confirming.
Open the Web3 guide →Visit the DAppOpen the intended site.
Confirm the domainMake sure the domain matches the service you intended to use.
Connect the walletReview which account and network are requested.
Inspect the account requestDo not expose seed phrases or private keys.
Review signing or approvalRead the action, contract and permission scope.
Complete the actionCheck the resulting transaction state.
Disconnect when no longer neededRemove stale sessions and approvals where appropriate.
Security
Security starts before you click confirm
Seed phrases and private keys remain under the user’s control. Do not send them to anyone, and do not treat a familiar interface as proof that a request is safe. Review address, network and amount before transfers, inspect each signature, and manage token approvals that are no longer needed.
Open Security Center →Back up seed phrases offline
Never disclose private keys
Verify network and address
Inspect signature requests
Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
Before the first transfer, learn how addresses, seed phrases, private keys, networks, gas, transaction hashes, DApps and token approvals relate to one another. These concepts are connected: the network determines the transaction context, the address identifies an account or contract, gas pays for execution, and signatures express permission.
Start learning →Ethereum & PoS
Understand staking before participating
Ethereum Staking
Understand Ethereum PoS, validators, reward sources, withdrawals and exits before evaluating participation.
Read the staking guide →Before participating
Staking does not guarantee returns. Rewards can change; validators may face penalties; exits can involve waiting; smart contracts and third-party services introduce technical risk; and digital asset prices can move significantly.
Understand validators →Updates
Product, network and security information
Wallet usage guidance refined
Details →Navigation and learning paths continue to focus on practical wallet tasks and clearer network checks.
Review account and network before DApp use
Details →A connected wallet should still review each later request independently.
Do not share seed phrases or private keys
Details →Sensitive credentials remain under the user’s control and should never be submitted to websites or support chats.
Confirm the active chain before troubleshooting
Details →Transaction state, gas and balances should always be interpreted in the context of the correct network.
FAQ
Common questions before you act
A wallet manages addresses, signing and on-chain interactions. Asset records live on blockchains; the wallet helps users view state and initiate actions.
A seed phrase can usually restore control of the corresponding wallet. Keep it offline and do not screenshot, upload or share it.
No. Official personnel should never request a private key, seed phrase or verification code.
The same address format can appear on different networks, while balances and transactions belong to a specific chain.
At minimum, verify the destination address, network, amount, gas and intended recipient. For higher-value transfers, consider a small test first.
Gas is the fee mechanism used for transaction or contract execution. Its level depends on network rules and congestion.
A transaction hash identifies a public on-chain transaction and can be used in a block explorer to inspect status and confirmations.
Get imtoken from the unified download entry
The download action is always initiated by you.