Create a Wallet
Create a new wallet on a trusted device and understand the relationship between addresses, seed phrases, and private keys first.
View steps →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 and network selection to transfers, DApp connections, token approvals, network knowledge, and wallet safety, imtoken keeps critical actions in a clear and verifiable workflow. Every transaction, signature, and approval starts with checking the network, address, and request details.
Multi-networkVerify the network before transacting
Quick start
What do you want to do?
Start from a real task and keep a safety check at every step.
Back Up a Wallet
Keep recovery information offline, verify its order and completeness, and do not send it through chats, cloud drives, or unfamiliar sites.
View steps →Receive Assets
Confirm the receiving address and network, and make sure the sender uses that same network.
View steps →Send Assets
Verify the address, network, amount, and gas, then keep the transaction hash and follow confirmation status.
View steps →Connect to a DApp
Verify the domain and network first, then review connection, signature, approval, and transaction requests separately.
View steps →Wallet capabilities
One wallet interface across different on-chain tasks
Multi-chain Assets
Know the network before deciding where an asset lives
Assets, addresses, and confirmations belong to specific blockchains. Switching networks does not move assets automatically.
Learn multi-chain basics →
imtoken APP
Manage networks, assets, and history on mobile
From asset viewing to DApp use, every signature is an active user decision.
Send & Receive
Address, network, amount, gas, and transaction hash
Verify before sending, then use the transaction hash to inspect the on-chain result.
Read the transfer guide →A browser connection is not an approval
Treat account connection, message signing, transaction signing, token approvals, and disconnecting as separate actions.
Wallet Safety
Keep recovery credentials offline and private
Official personnel will not ask for seed phrases or private keys.
Multi-chain
One wallet can show many chains, while each chain keeps independent state
Confirm the current network, gas asset, and transaction destination; moving across chains requires an explicit transfer path.
Public Chains
Nodes propagate transactions and blocks build confirmations
Block height, transaction hashes, and explorers help users trace wallet displays back to public on-chain data.
EVM
Familiar addresses do not make networks interchangeable
Chain IDs, native gas assets, contract deployments, and balances remain network-specific.
Layer 2
Check the bridge path and timing before moving between layers
Cross-layer operations can involve multiple confirmation stages, bridge-contract risk, and third-party dependencies.
GAS
Gas
Fees are part of on-chain execution
Fees can change with network conditions, and a failed transaction may still consume gas because execution resources were used.
User journey
From getting the wallet to reviewing transactions and approvals
Practical safety comes from a sequence of good decisions, not a single safety button.
- 01
Get imtoken
Use the single download entry instead of looking for installers on unknown pages.
- 02
Create or import a wallet
Create or import only on a trusted device you control; never submit recovery phrases to a website or support agent.
- 03
Back up the wallet offline
Keep the seed phrase offline and verify the word order. Do not screenshot, send, or share it.
- 04
Choose and verify the network
Check the network name, gas asset, and application requirements. Similar addresses do not mean the networks are the same.
- 05
Receive or send assets
Verify address, network, and amount before sending; consider a small test where it makes sense.
- 06
Review transactions and approvals
Keep the transaction hash, inspect DApp requests before signing, and review permissions you no longer need.
Web3 & DApp
Connecting a wallet does not mean every signature should be approved
Review every signature and approval on its own. Confirm the domain, account, network, contract, and permission scope; cancel if the request is unclear.
Open the Web3 guide →- 01Visit the DApp
- 02Verify the domain
- 03Connect
- 04Review account requests
- 05Inspect signatures or approvals
- 06Complete the action
- 07Disconnect unused sessions
Security
Keep the most important secrets under your control
Seed phrases and private keys remain under the user's control. Do not share them through support chats, web forms, email, or remote-control tools. Verify address, network, and amount before sending, inspect DApp requests before signing, and remember that third-party contracts can carry technical and operational risk. On-chain transactions generally cannot be reversed by a wallet alone.
Open the Security Center →- Back up the seed phrase offline
- Never disclose private keys
- Verify network and address
- Review signature requests
- Manage DApp approvals
Featured guide
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases, private keys, networks, gas, and transaction hashes before moving into DApps and approvals. Learn the concepts that change real outcomes first.
Read the full guide →
NetworkPublic Chains and ConfirmationsNodes, blocks, explorers, and confirmation state
EVMEVM and Smart ContractsAddresses, gas, tokens, and approvals
Layer 2Layer 2 BasicsMainnet relationships, bridges, and settlement
Web3DApp ApprovalsSpenders, allowances, and permission management
SafetyWallet SecurityKeys, devices, phishing, and transaction checks
GlossaryBlockchain GlossaryPut common terms back into real user contexts
Ethereum Staking
Understand PoS, validators, reward sources, and exits
Ethereum staking does not guarantee returns. Rewards can change, exits may involve waiting, and validators can face network penalties.
Learn Ethereum staking →Product & Safety Updates
Useful information without invented metrics
Wallet and network guidance continues to follow real user workflows.
No one should ask you for a seed phrase, private key, or verification code.
Switching networks does not move assets; confirm both sides use the same network.
All download links go to the download page; content pages do not trigger downloads automatically.
FAQ
Start with the questions that affect real wallet use
From key protection and network checks to DApp signing and staking mechanics.
View all FAQs →A digital wallet helps you manage keys and interact with blockchain networks. Asset state is recorded on the relevant blockchain rather than simply stored inside a phone application.
A seed phrase is commonly used to recover a set of wallet accounts. It is highly sensitive and should stay offline rather than being sent to people or entered into unfamiliar websites.
No. A private key can control an address. Official personnel should never ask for your private key, seed phrase, or wallet verification code.
Assets exist on specific networks. Even when address formats match, using the wrong network can prevent a receiving service from recognizing or crediting a transfer.
Gas measures on-chain execution resources and contributes to network fees. Costs can change with congestion, transaction complexity, and protocol rules.
A transaction hash lets you locate a transaction on the correct block explorer and inspect public details such as sender, recipient, status, block, and fees.
Check the transaction hash first and review network congestion, fees, and any earlier transaction from the same account. Avoid repeatedly resubmitting without understanding the cause.
imtoken
Start with the safety principles in mind
Downloading, creating, backing up, transferring, and connecting to DApps all begin with active verification.