Create a Wallet
Understand control and backup responsibility before creating a new wallet.
Open guide →imtoken · Multi-chain Digital Wallet
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 assets, network selection, sending and receiving to DApp connections, token approvals, network concepts and wallet security, imtoken brings practical checks and essential knowledge into one clear path.
Start with the task in front of you
Wallet learning does not have to start with a glossary. Begin with the task you need to complete, then add the network, signature and security context around it.
Back Up a Wallet
Keep the seed phrase offline; avoid screenshots, cloud sync or sharing.
Open guide →Receive Assets
Check the address and network, and make sure the sender uses the same network.
Open guide →Send Assets
Review address, network, amount and gas before sending, then keep the transaction hash.
Open guide →Connect to a DApp
Verify the domain first, then review every signature and approval separately.
Open guide →Wallet capabilities organised around real use
A single wallet action often spans account control, network choice and an on-chain result. These topics are grouped by how they are used, not by interface buttons.
Multi-chain Assets
Understand separate network state, address checks and confirmation so similar addresses are not mistaken for identical networks.
Understand multi-chain use →imtoken App
View assets, switch networks and review activity on mobile while keeping device security separate from offline backup.
Explore the app →Send & Receive
Receiving addresses, networks, amounts, gas and transaction hashes together describe a complete on-chain transfer.
Review transfer checks →imtoken Web
A browser connection does not approve every later request. Review each signature, approval and contract interaction separately.
Learn about web connections →Wallet Security
Keep seed phrases and private keys offline, review DApp approvals and reject any request for sensitive credentials.
Open Security Center →Explore blockchain networks
Network choice determines where a transaction executes and affects gas, confirmation, asset display and contract addresses.
One wallet can face separate network states
In a multi-chain environment, network name, chain ID, native gas asset and token contracts all need separate checks. A similar-looking address is not a substitute for selecting the correct network.
Public chains maintain state through participating nodes
Transactions are received, included and confirmed by the network. Block height and transaction hashes are useful public references for verification.
EVM networks share execution concepts but maintain separate state
Gas, contract execution and token approvals are common across EVM ecosystems, while contract deployments and asset state remain network-specific.
Layer 2
Cross-layer transfers may involve bridges, message confirmation or exit waits, so submission and destination availability are not always the same moment.
Gas and confirmations
Fees can vary with network demand and transaction complexity. A public transaction hash can be used to inspect pending, successful or failed status.
A practical wallet path
From obtaining the wallet to reviewing transactions and approvals, each step includes a repeatable safety action.
Get imtoken
Use the download entry on the official site and verify the source.
Create or Import
Understand creation versus import; do not enter seed phrases into web pages.
Back Up Offline
Keep the seed phrase offline and never disclose private keys.
Select and Verify a Network
Check the network, chain ID and required gas asset.
Receive or Send Assets
Review address, network and amount before transferring.
Review Transactions & Approvals
Keep transaction hashes, review DApp signatures and remove approvals you no longer need.
Web3 & DApp
Treat every request as a separate decision
Connecting a wallet only establishes an account-access relationship. It does not mean later signatures, token approvals or contract calls should be accepted.
Connecting a wallet does not mean every signature request should be approved. Review each signature and approval on its own.
Open the Web3 guide →01 Open the DApp
02 Verify the domain
03 Start the connection
04 Review the account request
05 Inspect the signature or approval
06 Complete the action
07 Disconnect when no longer needed
Security
Review control, requests and device environment together
Wallet security does not come from an absolute promise. It comes from repeatable actions: keep sensitive keys offline, reject anyone asking for a seed phrase, verify networks and addresses before transfers, inspect DApp requests individually, and remove permissions you no longer need. Public computers, public Wi-Fi, screen sharing and remote-control sessions increase exposure, so sensitive actions are better performed on trusted devices and networks. Because confirmed on-chain transactions generally cannot be reversed by a wallet, the final pre-submit review matters more than after-the-fact recovery claims.
Open Security Center →Security checklist
- Back up the seed phrase offline
- Never disclose private keys
- Check the network and address
- Review signature requests
- Manage DApp approvals
Academy
Move from concepts to actions through an editorial path that connects wallets, networks, transactions and Web3.
What Should You Understand Before Using a Digital Wallet?
Addresses identify accounts and receiving destinations; seed phrases and private keys relate to control; networks determine state and gas; transaction hashes support public verification; and DApp connections, signatures and approvals are different levels of request. Understanding them together helps prevent interface similarity from being mistaken for identical on-chain actions.
Read the guide →Ethereum & PoS
Treat staking as protocol knowledge and risk assessment, not as a return-promotion message.
Ethereum Staking Basics
Ethereum proof of stake relies on validators. Reward sources depend on protocol and network conditions, participation and validator performance, while exits and withdrawals can involve waiting.
Learn the staking mechanics →What to understand first
Validators can face protocol penalties, smart contracts can have technical risk, digital asset prices fluctuate, and third-party services can add operational or custody risk. Staking does not guarantee returns.
Understand validators →Product and Security Updates
No fabricated dates, user counts or partnership claims—only content-focused notices by category.
Recent Update
Multi-chain verification notes
Before using a network, verify its chain ID, gas asset and contract context.
Product Notice
Reading transaction history
Use transaction hashes and an explorer to confirm on-chain results.
Security Notice
Never share a seed phrase
Impersonated support, fake airdrops and remote assistance are never a reason to disclose keys.
Network Notice
Layer 2 transfer waits
Destination availability depends on the network and bridge design, so verify the destination state.
Frequently Asked Questions
Common questions across wallets, networks, transactions, DApps, security and Ethereum PoS.
Seed phrases and private keys should remain under your own control. Never send them to another person or enter them into an unfamiliar page, chat or remote-control session.
Both relate to account control. A wallet may derive multiple private keys from a seed phrase, so exposure of either sensitive form can place assets at risk.
Networks maintain separate state even when address formats look similar. Check the network, chain ID, token contract and appropriate explorer.
Review the destination address, selected network, asset, amount and gas. For a new destination or a large transfer, a small test can reduce avoidable mistakes.
Gas is generally a network fee required to execute and process an on-chain transaction. It is not the same thing as a fixed wallet-brand fee.
A transaction hash is a public identifier that can be used in a block explorer to verify status, block inclusion, addresses and execution results.
Not necessarily. Connection, message signatures, transaction signatures and token approvals are separate requests and should be reviewed separately.
No. A signature may be used for authentication or may have asset-related consequences. Reject requests you do not understand and verify the domain first.
Ready to start with imtoken?
All download actions use the same download page. Verify the current domain and request details before continuing.