Identify the network before the asset
The same asset name can appear on different networks, and similar EVM addresses do not mean identical chain state. Check the network, token contract and gas asset.
Understand multi-chain →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
Move from asset views and network selection to sending, receiving and DApp access with a clear understanding of what each action does. imtoken also explains approvals, network mechanics and wallet security so important decisions happen only after the address, chain, amount and permission have been reviewed.
01Create a Wallet
Understand how addresses and keys are created and initialize a wallet in a trusted environment.
Start here →02Back Up a Wallet
Keep the seed phrase offline, preserve the exact order and avoid chats, cloud notes and screenshots.
Backup principles →03Receive Assets
Confirm the network before sharing an address so both sides use the same chain.
Receive guide →04Send Assets
Review the address, network, amount and gas, then keep the transaction hash for verification.
Send checklist →05Connect to a DApp
Verify the domain, account and network and make a fresh decision for every signature and approval.
Connection guide →Wallet capabilitiesMulti-chain assets
Keep every step understandable, from assets to Web3
A wallet is more than a balance screen. Addresses, networks, gas, transaction hashes, contracts and approvals shape the full on-chain workflow.
Send & Receive
Confirm the network before receiving and add address, amount and fee checks before sending. Use the transaction hash afterward.
Transfer guide →imtoken App
Review assets, manage networks and inspect transaction history on mobile while treating each DApp request as a separate decision.
Explore the App →imtoken Web and security principles
Browser connectivity supports DApp access without asking for a seed phrase or private key. Connections, signatures and approvals are different actions and should be reviewed independently.
Web access → Security center →Blockchain networks
Understand the network, not just the address format
Public chains, EVM networks and Layer 2 systems have their own fees, confirmations and state. All text remains available even without scripts.
Multi-chain
A multi-chain wallet organizes several networks, but every asset still belongs to a specific chain. Confirm the active network before transfers, token additions or DApp use.
Read more →Public Chains
Nodes, blocks, transactions and confirmations maintain a public ledger, while block explorers help verify public state.
Public chain basics →EVM Networks
EVM-compatible chains can share account and contract models while keeping chain IDs, gas assets and state separate.
Understand EVM →Layer 2
Layer 2 systems scale activity alongside a main chain; moving assets across layers can involve bridges, waiting and extra confirmations.
Explore Layer 2 →Gas & Confirmations
Gas pays for on-chain resources, while confirmation follows the network’s block and consensus rules. A higher fee cannot guarantee an exact completion time.
Gas guide →Wallet path
Build a repeatable wallet routine in six steps
01
Get imtoken
Use a trusted entry point and avoid unknown installers from direct messages or ads.
02
Create or import
Create or import only in trusted wallet software and never submit a seed phrase to a web form.
03
Back up offline
Keep the recovery phrase offline and never disclose a private key to another person.
04
Select the network
Identify where the asset lives, the destination network and the native gas asset.
05
Receive or send
Check address, network and amount; consider a small test for a new route.
06
Review transactions and approvals
Inspect DApp requests before signing, verify transaction hashes afterward and remove permissions you no longer need.
Web3 & DApps
Treat connection, signing and approval as separate decisions
Connecting a wallet does not mean every later request should be accepted. Review each signature and approval on its own.
Verify the domain, requested account, network, signature details, spender and allowance. Reject requests you cannot explain.
- Open the DApp
- Verify the domain
- Request connection
- Review account access
- Inspect signature or approval
- Complete the action
- Disconnect unused sessions
Security
What matters most is the check before every critical action
Wallet security combines key custody, device hygiene, network selection and deliberate decision-making. Seed phrases and private keys stay with the user, and imtoken staff will not ask for them. Review the destination, network and amount before sending, and review each DApp signature and approval independently. Most confirmed blockchain transactions cannot be reversed by a wallet provider, and third-party contracts may carry their own risks.
Open Security Center
- Back up the seed phrase offline
- Never disclose private keys
- Check the network and address
- Review signing requests
- Manage DApp approvals
AcademyFeatured beginner guide Network Contracts Scaling Security
Learn digital wallets in the order people actually use them
What Should You Understand Before Using a Digital Wallet?
Addresses identify accounts; seed phrases and private keys determine control; networks determine where assets actually exist; gas pays for on-chain actions; transaction hashes let you inspect status; and DApps use connections, signatures and approvals to interact with wallets. These foundations make later topics such as EVM, Layer 2 and smart contracts easier to judge in context.
Start learning →Public chains and confirmations
How nodes, block height and confirmations shape transaction status.
EVM and smart contracts
The relationship between addresses, gas, tokens and approvals.
Layer 2 basics
Main chains, bridges, cross-layer movement and waiting periods.
DApp approvals and wallet safety
Understand spenders, allowances and revocation.
Ethereum & PoS
Understand validators before thinking about staking
Ethereum Staking Basics
Ethereum proof of stake uses validators for block proposals and attestations. Rewards, network status, exits and withdrawals follow protocol rules rather than a fixed return.
Ethereum staking →Know the risks first
Validators can face network penalties; exits can involve queues; smart contracts, third-party services and asset-price volatility add additional risks.
PoS & validators →Product & security updates
Focus on information that changes how you operate
Recent Update
Multi-chain network guidance
View →Understand network checks, chain IDs, gas and block explorers.
Security Notice
Beware of fake support asking for seed phrases
View →A legitimate support flow does not require wallet secrets.
Product Notice
Review DApp connections and approvals separately
View →Connection, signing and approval are distinct actions.
Network
Layer 2 transfers can add confirmation steps
View →Bridging, exits and arrival time depend on the network design.
FAQ
Common questions
Asset state is recorded on the blockchain; a wallet manages keys, addresses and on-chain actions.
No. imtoken staff will not ask for a seed phrase, private key or verification code.
Similar address formats do not make networks interchangeable. Sender and receiver should use the same intended chain.
Use its transaction hash on the block explorer for the relevant network.
No. Connection, signing and token approval are separate actions.
No. Rewards can change with network conditions, validator performance and protocol rules.
Get started
Download imtoken