Create a Wallet
Understand the relationship between a wallet and its keys before creating one.
Open guide →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
From multi-chain assets, network selection, sending and receiving to DApp connections, approvals and wallet security, imtoken brings product use and blockchain knowledge into one clear path. Start with essential tasks, then build a practical understanding of network differences, gas, confirmations and smart-contract risk.
Start with real tasks
Five common tasks are organized around practical dependencies and risk, without requiring every technical term up front.
Back Up a Wallet
Keep seed phrases and private keys offline and under your control.
Open guide →Receive Assets
Make sure the receiving address and sender use the same network.
Open guide →Send Assets
Review the address, network, amount and gas before submission.
Open guide →Connect to a DApp
Verify the domain, then review account, signature and approval requests.
Open guide →A wallet is more than an asset list
Assets, networks, transfers, mobile use, browser connections and security each solve a different problem and deserve different treatment.
Multi-chain assets
Keep network boundaries visible
One wallet can present assets from multiple networks, while gas, confirmation behavior, token contracts and risk environments remain network-specific.
Send & Receive
Four checks before sending
The transaction hash becomes an important verification reference after submission.
Learn transfer checks →imtoken APP
View networks, assets and transaction history on mobile
imtoken Web
Review every browser-based request
A connection only establishes a channel; approvals, signatures and transactions remain separate decisions.
Wallet security
Offline keys, limited approvals, verifiable requests
Explore blockchain networks
Use a network-first view to understand addresses, gas, confirmations and cross-layer movement.
Multi-chain
In a multi-chain environment, identify where the asset lives before choosing a network for transfers or DApp use.
Open network guide →Public Chains
Nodes propagate transactions, blocks record state and confirmations build confidence; block explorers help verify independently.
Open network guide →
EVM
EVM networks share account and contract concepts, but chain IDs, gas markets and asset environments still need separate checks.
Open network guide →
Layer 2
Layer 2 systems have explicit relationships with mainnet; bridging, arrival and exits can involve separate stages and waiting periods.
Open network guide →
Gas & Confirmations
Gas reflects computation cost; confirmations reflect how a transaction becomes established in blocks.
Open network guide →A wallet path you can verify at every step
01
Get imtoken
Use the site download entry to reach the existing download flow; content pages do not expose a final mobile target.
02
Create or import a wallet
When creating or importing a wallet, keep recovery information inside a trusted local environment.
03
Back up the wallet offline
Store seed phrases and private keys offline; do not screenshot, send or enter them into web verification forms.
04
Choose and verify the network
Similar address formats can appear on different networks, so verify the intended chain before sending.
05
Receive or send assets
Review address, network, amount and gas; a smaller test can help validate an unfamiliar route.
06
Review transactions and approvals
Use transaction hashes to verify on-chain status and periodically review approvals you no longer need.
Web3 & DApp
Treat every request as a separate decision
Connecting a wallet does not mean every signature or approval should be accepted. Review the domain, account, message, transaction and token approval separately.
A wallet connection does not mean every signature request should be accepted. Review each signature and approval on its own.
- Visit the DApp
- Verify the domain
- Start the connection
- Review the account request
- Check the signature or approval
- Complete the action
- Disconnect sessions you no longer need
Security
Security comes from repeatable checks
Seed phrases and private keys remain under the user’s control, and official staff will not ask for them. Verify the address, network and amount before transfers, and review domains, signatures and approval targets before DApp interactions. On-chain transactions can be difficult or impossible for a wallet provider to reverse, and third-party smart contracts may add risk.
Open Security Center →- Back up seed phrases offline
- Never disclose private keys
- Check network and address
- Review signature requests
- Manage DApp approvals
Academy
What Should You Understand Before Using a Digital Wallet?
Connect addresses, seed phrases, private keys, networks, gas, transaction hashes, DApps and approvals into one practical path
An address identifies an account for receiving assets, a private key signs actions, and a seed phrase can be used to recover keys. The network determines where a transaction happens, gas represents on-chain resource cost, and a transaction hash helps verify the result. In Web3, DApp connections, signatures and token approvals should be understood as different permissions.
Read Getting Started →Public chains and confirmations
Understand nodes, blocks and confirmations.
EVM and smart contracts
Learn gas, contract addresses and approvals.
Layer 2 basics
Mainnet relationships, bridges and waiting stages.
DApp approvals
Review target, allowance and purpose.
Wallet security and glossary
Turn terminology into practical checks.
Ethereum and PoS knowledge
Understand validator duties, reward sources, exits and withdrawals together with waiting, penalty, contract and market risks.
Ethereum Staking Basics
Ethereum PoS uses validators to participate in block proposal and validation. Rewards depend on network mechanics and validator state and are not fixed; exits and withdrawals may include waiting periods.
Learn about Ethereum staking →What to know before participating
Validators can face network penalties, smart contracts can fail, digital asset prices can move and third-party services add their own risk. Participation should match the user’s own circumstances.
Understand PoS and validators →Product and security updates
No invented dates, partnerships, funding, licenses or user metrics—only update categories that help users operate safely.
ProductWallet usage guidance continues to improve
→NetworkRe-check the network name and gas before on-chain actions
→SecurityBeware of pages asking for seed phrases or private keys
→ServiceStaking and validator state depend on network mechanics
→ProductReview Web3 connections and approvals periodically
→Frequently asked questions
Open full FAQ →No. Seed phrases and private keys should remain under your control, and official staff will not ask for them.
On-chain transactions normally cannot be unilaterally reversed by a wallet provider. Verify address, network and amount before sending.
The address format may be the same, while assets, gas and transaction state remain network-specific.
Connection, signatures, transactions and token approvals are different actions and should be reviewed separately.
Avoid blind retries. Check congestion, pending transactions and current fees before deciding what to do.
No. Rewards can change, exits can involve waiting, and validators can be subject to network penalties.
Start from the download entry and understand each on-chain action
All site download buttons lead to /download.html. Review transfer, signature and approval details before confirming.