Create a Wallet
Understand what a new wallet creates and which information represents control.
Start here →imtoken
A multi-chain wallet, blockchain network and Web3 knowledge hub from imtoken
Manage Multi-chain Assets and Connect to Web3 with Clarity
Use imtoken to learn how multi-chain assets, network selection, receiving, sending, DApp connections, signatures, approvals and wallet security fit together before you take action on chain.
Multi-chain assetsNetwork selectionSend & receiveDApps & approvalsWallet security
Back Up a Wallet
Keep the seed phrase offline rather than in screenshots, cloud sync or messages.
Backup principles →Receive Assets
Verify the receiving address and intended network rather than relying on the token name.
Receiving guide →Send Assets
Review address, network, amount and gas before deliberately submitting.
Transfer checks →Connect to a DApp
Verify the domain, then review the account, signature and approval scope.
DApp guide →Wallet & Assets
Wallet capabilities make more sense when they are tied to real on-chain tasks
Balance viewing, transfers, browser connections and backups touch different parts of the wallet and carry different verification requirements.
Multi-chain assets
A single wallet can display several networks while each chain keeps its own state, gas asset and confirmation model. Similar address formats do not make networks interchangeable.
- Network differences and asset location
- Address and network verification
- Transaction status and confirmations
Send & Receive
Confirm the address and network before receiving; review the amount, gas, token and transaction hash when sending.
See the transfer flow →imtoken App
Mobile network management, balance viewing and transaction history with device security and offline backup still under the user’s control.
imtoken Web
Browser connectivity supports Web3 access. Connections, signatures, approvals and actual transactions should be judged separately.
Learn browser connections →Wallet security
Never send a seed phrase or private key to anyone. Backups, approval management, device control and transaction checks work together.
Networks
Explore multi-chain networks
Learn where assets live, how network fees work and how confirmations can be independently checked. Even if interactive controls are unavailable, the complete text remains readable.
Multi-chain is not one chain with several labels
Different networks maintain separate ledgers. A wallet can aggregate the view while assets still belong to a specific network.
Explore multi-chain →Public chains are maintained through nodes, blocks and consensus
Transactions are broadcast, included in blocks and confirmed. Block explorers expose public evidence such as hashes and block height.
Learn public chains →
EVM compatibility does not make networks identical
Chain IDs, gas assets, deployed contracts and state remain independent even when address formats look similar.
Understand EVM →
Layer 2 has a settlement relationship with a base network
Cross-layer transfers can involve bridges, waiting periods and exit mechanisms that differ from same-network transfers.
Learn Layer 2 →
Gas and confirmation answer different questions
Gas is about execution cost; confirmations describe the transaction’s continuing on-chain status after inclusion.
Learn gas & confirmations →Start safely
A practical wallet path
Get imtoken
Use the site’s download entry rather than installation links sent by strangers.
Create or import a wallet
Understand the difference and use only a trusted device and application environment.
Back up offline
Keep the seed phrase offline, do not screenshot it, and never disclose a private key.
Select and verify the network
Identify the network, its gas asset and the intended destination.
Receive or send assets
Review the address, network and amount before confirming.
Review transactions and approvals
Read DApp requests, keep transaction hashes and periodically remove permissions you no longer need.
Web3 & DApps
A connection is only the beginning; every signature and approval deserves a separate review
Web3 flows often contain several actions in sequence. Reading each step separately keeps a successful connection from becoming automatic consent to everything that follows.
Connecting a wallet does not mean every signature request should be approved. Review each signature and approval independently.
Visit the DApp
Use a trusted route.
Verify the domain
Check spelling, HTTPS and source.
Start the connection
Confirm the requested account and network.
Review account access
Understand what public information is being requested.
Inspect the signature or approval
Focus on contracts, spenders, allowances and permissions.
Complete the action
Verify that the on-chain result matches your intent.
Disconnect unused sessions
Also review any approval that may remain.
Security
Wallet security is a repeatable verification process, not a promise
Users keep their own seed phrases and private keys, and official staff will never ask for them. Before transferring, signing or approving, verify the address, network, amount, contract and permission scope. On-chain transactions usually cannot be reversed by a wallet provider, while third-party DApps and smart contracts can carry independent risk.
Public computers, unknown extensions, remote-access tools and untrusted networks can increase exposure. Consider removing approvals that are no longer needed and keep both devices and backups under your control.
Open Security CenterBack up the seed phrase offlineNever disclose private keysVerify networks and addressesRead signature requestsManage DApp approvals
What Should You Understand Before Using a Digital Wallet?
Start with addresses, seed phrases and private keys, then learn how networks, gas and transaction hashes provide verifiable context before moving into DApps, signatures and approvals.
An address is normally public and can receive assets, while seed phrases and private keys can represent control and must remain private. Networks define where transactions execute, gas pays for network work, and transaction hashes make results inspectable in a block explorer.
Start the learning path →Public chains and confirmations
Understand nodes, blocks and transaction evidence.
EVM and smart contracts
Learn gas, contract addresses and approvals.
Layer 2 basics
Base-network relationships, bridging and settlement.
DApp approvals
Review spenders, allowances and revocation.
Wallet security
Backups, devices, scams and transaction checks.
Blockchain glossary
Keep common terms connected to their purpose.
Ethereum & PoS
Understand staking mechanics together with their limits and risks
Ethereum Staking Basics
Ethereum PoS uses validators in consensus. Reward sources, network state, withdrawals and exits affect participation, and rewards are not fixed.
Learn Ethereum staking →What to understand first
Validators can face penalties, exits can require waiting, smart contracts carry technical risk, asset prices fluctuate and third-party services add separate risk.
Understand PoS & validators →Updates
Product and security updates
Multi-chain network guidance continues to expand
Additional material covers confirmations, address checks and cross-layer transfers.
Support never requires a seed phrase or private key
Stop if someone requests secrets, remote control or a “recovery verification” process.
DApp connections and token approvals are separate actions
Connecting an account is not the same as granting asset permissions.
Staking education emphasizes exit and waiting risks
Ethereum PoS rewards can change and validators are subject to network conditions and penalties.
FAQ
Frequently asked questions
Digital assets are recorded on their blockchains. A wallet controls addresses with keys and reads on-chain balances; the app itself is not the ledger.
A seed phrase can derive wallet keys, while a private key is specific secret key material. Both should be kept offline and private.
No. imtoken will never ask for a seed phrase, private key or verification code.
Assets with similar names can exist on different networks and address formats can look alike, so both sides must confirm the intended network.
Gas is the fee mechanism for executing transactions or contract calls and can vary with network rules, complexity and congestion.
A transaction hash can be used in a block explorer to inspect status, block inclusion, sender, recipient and execution result.
Usually a connection establishes a session only. Later signatures, transactions and token approvals must be reviewed separately.
Ready to begin with imtoken?
Before downloading, make sure you understand seed backups, network selection and transaction checks.