Create a Wallet
Understand addresses, networks and backup responsibility before creating a new wallet.
Learn more →imtoken · Multi-chain Wallet
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 assets, choose the correct network, send and receive with deliberate checks, connect to DApps, review approvals, and build stronger wallet-security habits through practical network knowledge.
Start from the task you need to complete
A clear task path reduces the chance of skipping network, address, backup or approval checks.
Back Up a Wallet
Keep the seed phrase offline and separate from screenshots, cloud notes and chat tools.
Learn more →Receive Assets
Share the correct receiving address and make sure the sender uses the matching network.
Learn more →Send Assets
Check destination, network, amount, gas and transaction summary before signing.
Learn more →Connect to a DApp
Verify the domain and review each connection, signature and approval request separately.
Learn more →Wallet capabilities in real use
Multi-chain assets
Different networks can use similar addresses while keeping balances, fees and transaction state separate.
Send & receive
Review address, network, amount, gas and transaction hash as one flow.
imtoken App
Mobile access for network management, asset viewing, transaction history and DApp use.
imtoken Web
Review browser connection, approval and disconnect requests before confirmation.
Wallet security
Seed phrases and private keys stay under user custody. Offline backup and approval review are routine responsibilities.
Explore blockchain networks
Multi-chain does not mean one shared state
Balances, fee assets, confirmations and contract state depend on the selected network.
Blocks, nodes and confirmations
Public chains use distributed nodes and protocol rules to order transactions into blocks.
EVM-compatible networks share an execution model, not one ledger
Gas assets, contracts and token balances remain network-specific.
Layer 2 adds another settlement path to understand
Cross-layer transfers can involve bridges, confirmation windows and waiting periods.
A six-step wallet path
Get imtoken
Start from a trusted imtoken entry point and review the product information.
Create or import
Understand whether you are creating new keys or importing existing wallet credentials.
Back up offline
Keep the seed phrase offline and never share the private key with anyone.
Choose the network
Verify network, address format, fee asset and destination requirements.
Receive or send
Check address, network, amount and gas before signing.
Review transactions & approvals
Verify the transaction hash and review approvals that are no longer needed.
Review every request, not just the connection
Connecting a wallet does not mean every later signature or approval should be accepted.
Each signature and approval is a separate decision.
- Visit the DApp
- Verify the domain
- Start the connection
- Review the account request
- Inspect signature or approval
- Complete the action
- Disconnect when no longer needed
Security is a sequence of checks you can repeat
Keep seed phrases and private keys under your own custody, use offline backups, verify destination and network, inspect signatures and manage DApp approvals.
Open Security Center →✓ Back up the seed phrase offline
✓ Never disclose private keys
✓ Verify network and address
✓ Inspect signature requests
✓ Manage DApp approvals
What Should You Understand Before Using a Digital Wallet?
A wallet interface brings together addresses, seed phrases, private keys, networks, gas, transaction hashes, DApps and approvals.
Read the guide →Public chains and confirmations
Understand blocks, nodes, explorers and confirmation depth.
EVM and smart contracts
Learn how addresses, gas, contracts and token approvals relate.
Layer 2 basics
Understand mainnet relationships, bridges and cross-layer transfers.
DApp approvals
Review spenders, allowances and revocation.
Private keys and backups
Build safer habits around custody and recovery material.
Ethereum and Proof of Stake
Ethereum Staking Basics
Learn proof of stake, validators, reward sources, network state, withdrawals and exits.
Learn the basics →Understand risk before participating
Rewards are not guaranteed. Waiting periods, validator penalties, smart-contract risk, third-party service risk and price volatility can affect outcomes.
PoS & validator guide →Product and security updates
Review network details before transfers
Details →Verify destination network, fee asset and transaction summary.
Wallet backup learning path
Details →A practical learning sequence for creation, backup, receiving and sending.
Treat approvals as ongoing permissions
Details →Review spender, allowance and contract address before approving.
Self-service support flow
Details →Start with network, transaction hash and request origin when troubleshooting.
Frequently asked questions
What is the difference between a wallet address and a private key?
A wallet address can be shared for receiving assets. A private key controls assets and must remain under the user’s custody; it should never be sent to anyone.
Can official staff recover a lost seed phrase?
No. A seed phrase is used to restore wallet control and should be backed up offline. Official staff should never ask for it and cannot recover a user’s private key.
Why must I verify the network before sending assets?
The same asset may exist on multiple networks. A wrong network can prevent the transfer from arriving as intended, and on-chain transactions generally cannot be unilaterally reversed by a wallet.
What is gas?
Gas is the network fee mechanism used to execute transactions or contract calls. Cost depends on network demand, transaction complexity and protocol rules.
What is a transaction hash used for?
A transaction hash is a unique identifier that can be used in a block explorer to check broadcast, inclusion, confirmation, failure or other on-chain status.
What should I do if a transaction is pending?
Verify the network, transaction hash and block-explorer status before taking another action. The cause may be congestion, fee settings or another network condition.
Does connecting to a DApp mean I already approved something?
Not necessarily. A connection usually creates an interaction channel. Signatures, transactions and token approvals are separate requests that should each be reviewed independently.
Ready to continue?
Use the download entry and keep address, network, signature and approval checks part of every action.