imtoken · FAQ
Frequently Asked Questions
Practical answers covering wallet control, blockchain networks, DApp permissions, security and Ethereum staking.
Use public information such as the network name, public address and transaction hash. Never send a seed phrase, private key or verification code to support.
A digital wallet manages keys, derives addresses and helps users interact with blockchain networks. Assets are recorded on the relevant chain rather than stored as files inside the wallet app.
No. Your seed phrase represents wallet control and remains under your custody. imtoken staff will never ask for a seed phrase, private key or verification code.
A seed phrase can derive one or more accounts, while a private key directly controls signing for a particular account. Both are sensitive recovery information.
Some EVM-compatible networks use similar address formats while maintaining independent state. Similar addresses do not make assets move automatically between networks.
Verify the full destination address, target network, asset and amount, then review gas and transaction details. Consider a small test for a high-value transfer when appropriate.
Gas is the network resource cost for processing a transaction or smart-contract call. It can change with congestion and transaction complexity and is not a fixed wallet fee.
A transaction hash identifies a specific on-chain transaction and can be used in a block explorer to check status, block inclusion and confirmations.
No. Connection usually establishes account visibility and a request channel. Message signatures, transactions and token approvals must still be reviewed separately.
Not necessarily. Message signatures are often used for login or proof of address control, but they can still have authorization meaning and should be read carefully.
A token approval lets a specific contract call assets within an allowance. Review the target, amount and purpose and consider revoking permissions you no longer need.
EVM-compatible networks can share address and contract patterns while using different chain IDs, gas assets, RPC endpoints, explorers and token contracts.
Layer 2 systems process activity outside the main chain and settle through defined mechanisms. Cross-layer transfers can involve bridges, waiting periods and multiple confirmation stages.
Use trusted entry points, verify domains and avoid starting important wallet actions from unknown direct messages or ads. Never enter a seed phrase or private key into an unfamiliar site.
Public networks add environmental risk. If use is unavoidable, avoid high-value actions, keep the device updated and take extra care with signing and copied addresses.
No. Rewards can change with network conditions, participation, validator performance and protocol rules, while digital-asset prices can also fluctuate.
Yes. Downtime can reduce rewards and serious protocol violations can lead to penalties. Exact rules depend on the network.
Some networks use activation, exit or withdrawal queues, so timing changes with network conditions. Third-party services can also add processing steps.
A network name, public address, transaction hash and visible error symptoms are usually enough for basic troubleshooting. Never provide recovery secrets or verification codes.
