Create a Wallet
Understand control and recovery material before creating a new wallet environment.
Start here →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 and network selection to sending, receiving, DApp connections and approvals, imtoken helps users understand what an action is asking before they confirm it. Network knowledge, transaction checks and wallet-security education put addresses, gas, transaction hashes, signatures and approvals into practical context.
Quick tasks
Back Up a Wallet
Keep the seed phrase offline and avoid screenshots, cloud sync and remote exposure.
Backup principles →Receive Assets
Confirm the receiving address, intended network and asset before sharing details.
Receiving checks →Send Assets
Review the address, network, amount and gas before submitting a transaction.
Transfer checklist →Connect to a DApp
Verify the domain and account request; review each signature and approval separately.
Connection guide →Wallet capabilities
Understand what a wallet does from asset display to security checks
A wallet is more than a balance screen. It connects addresses, networks, transactions and contracts with keys under the user’s control. Different actions need different checks.
Multi-chain assets
Identify the network before interpreting the asset
The same-looking address can appear on compatible networks while balances and histories remain separate. Use network context, token contracts and confirmations together.
Send & Receive
Review address, network, amount and gas together
For receiving, state the intended network. For sending, verify the address and asset, then use the transaction hash to check block status.
Transfer guide →imtoken Web
A connection does not approve every later request
After a browser connection, new signatures, transactions and token approvals still require individual review.
Web connections →imtoken App
Manage networks, assets and transaction records on mobile
Review asset state, initiate transactions and inspect history while keeping the device and link source in the security context.
Explore the App →Wallet security
Protect recovery material and manage permissions
Seed phrases and private keys remain under user control. Check approval targets and scope, and consider revoking permissions that are no longer needed.
Blockchain Networks
Know which network an asset belongs to before acting
Network selection determines which nodes process a transaction, which asset pays gas and where confirmations can be checked. Explore public chains, EVM, Layer 2 and gas within one reasoning framework.
Multi-chain
Multi-chain does not mean assets are automatically interchangeable
Networks maintain separate ledger states. Similar addresses do not replace network verification, and moving assets across networks normally requires an explicit bridge or transfer path.
Multi-chain guide →Public chain
Nodes, blocks and confirmations maintain a public ledger
A broadcast transaction must be processed and included in a block. Block height, status and confirmation count help explain progress.
Public-chain basics →
EVM
Similar address models still belong to separate networks
EVM networks share account and contract concepts, but network IDs, gas assets and deployments remain separate. Approvals also belong to a specific network context.
Understand EVM →
Layer 2
Understand how an expansion layer relates to the base layer
Layer 2 systems can use different execution and settlement designs. Bridging across layers requires attention to the destination network, arrival state and possible exit waits.
Learn Layer 2 →
Gas
Fees and confirmations reflect how a network processes a transaction
Gas relates to execution resources while final fees also depend on network rules and congestion. Pending, success and failure should be distinguished through on-chain status.
Gas & confirmations →Start safely
Build a sequence from obtaining the wallet to reviewing approvals
Keep one verifiable checkpoint at every stage: source, recovery material, network, address, transaction result and approval state. The same sequence remains useful on unfamiliar networks and DApps.
Get imtoken
Use a clear download entry point rather than unknown files sent through unfamiliar messages.
Create or import a wallet
Understand what recovery material controls and never enter a seed phrase or private key into a web page.
Back up offline
Keep the seed phrase offline and avoid screenshots, cloud sync and uncontrolled digital copies.
Select and verify the network
Confirm the network where the asset exists, the destination network and the appropriate gas asset.
Receive or send assets
Review address, network and amount, then retain the transaction hash for verification.
Review transactions and approvals
Read DApp requests before signing and periodically review permissions that are no longer needed.
Web3 & DApps
Break a DApp interaction into steps you can review
A wallet connection opens an interaction channel; it does not mean every later request should be accepted. Message signatures, transaction signatures and token approvals have different consequences.
Connecting a wallet does not mean every signature request should be approved. Review each signature and approval independently.
Visit the DApp
Verify the domain
Start the connection
Review account access
Check the signature or approval
Complete the action
Disconnect unused connections
Security
Security is a review habit, not an absolute promise
Seed phrases and private keys should remain under the user’s control, and official personnel will not request them. Wallet security also means checking addresses, networks, signing targets, token approvals, devices and unfamiliar links. Because on-chain transactions generally cannot be unilaterally reversed by a wallet, review before confirmation matters.
Third-party DApps and smart contracts can carry technical or malicious risks. Check approval targets and scope, consider revoking permissions no longer needed, and be cautious on public devices, public networks or remote-control environments.
Security Center- Back up the seed phrase offline
- Do not disclose private keys
- Verify the network and address
- Review signature requests
- Manage DApp approvals
Academy
Connect on-chain concepts into knowledge you can use
Begin with wallet control, then understand addresses, networks, gas, transaction hashes, DApps and approvals. A clear learning order makes unfamiliar networks and interactions easier to assess.
Featured starter
What Should You Understand Before Using a Digital Wallet?
Addresses identify accounts, seed phrases and private keys relate to control, networks determine where transactions occur, gas relates to execution cost, and a transaction hash helps trace activity. In DApps, connection, signatures and approvals should be understood as separate actions.
Read the starter guide →NetworksPublic Chains & ConfirmationsNodes, blocks, consensus and confirmation count.ContractsEVM & Smart ContractsAddresses, gas, contracts and tokens.ScalingLayer 2 BasicsBase-layer relationships, bridges and cross-layer checks.Web3DApp ApprovalsSpenders, allowances and revocation.SecurityWallet SecurityKeys, devices, phishing and review habits.GlossaryBlockchain GlossaryBuild connections between common terms.
Ethereum & PoS
Understand validators and protocol mechanics before considering staking
Staking information should begin with network mechanics, reward sources, exit processes and risk rather than presenting participation as fixed income.
Foundation
Ethereum Staking Basics
Ethereum uses PoS consensus. Validators perform protocol duties, reward conditions can change, and withdrawal or exit timing can depend on protocol rules and queue conditions.
- Ethereum PoS
- Validators and reward sources
- Network state, withdrawals and exits
Before participating
Risk and waiting mechanisms matter too
Staking does not guarantee returns. Rewards can change, exits may require waiting, validators can face penalties, and smart-contract, third-party and asset-price risks remain relevant.
- Network penalties and validator status
- Smart-contract and third-party service risk
- Waiting periods and digital-asset price volatility
Updates
Product, network and security information centered on impact and action
When a verified date is unavailable, the site does not manufacture one. Notices focus on what users need to know, which actions may be affected and what should be checked.
Recent UpdateWallet and network knowledge entry points organizedRead note →
Product NoticeDownload actions consistently enter download.htmlRead note →
NetworkVerify the destination network and gas asset before cross-network actionsNetwork guides →
Security NoticeNever send a seed phrase, private key or verification code to anyoneSecurity Center →
ServiceUnderstand changing rewards and exit waits before stakingLearn the mechanics →
FAQ
Common questions with checks you can perform yourself
For transaction, network or DApp issues, use public addresses, transaction hashes and network state for troubleshooting. Do not provide a seed phrase, private key or verification code.
No. Seed phrases and private keys should remain under the user’s control. Official personnel will not request them or verification codes.
Assets and transaction state belong to specific networks. A similar address format does not replace network verification.
Confirm the network and transaction hash, then inspect the corresponding block explorer for status, block height and confirmations. Pending does not automatically mean failed.
No. Connection, message signatures, transaction signatures and token approvals are separate requests that should be reviewed independently.
It generally allows a specified contract to use a token within an allowance. Review the spender, amount, network and contract address.
They should normally be understood as separate network states. Moving assets across layers may involve a bridge and different arrival or exit confirmation processes.
No. Rewards, network conditions and exit queues can change, and validator penalties, smart-contract risk, third-party risk and asset-price volatility remain relevant.
imtoken
Prepare your network, backup and security checks before you begin
All download actions enter the download page. After obtaining the wallet, complete recovery-material backup before working with assets or DApps.