imtoken · FAQ
FAQ
Frequently asked questions cover wallets, keys, networks, transfers, gas, transaction hashes, DApps, signatures, approvals, EVM, Layer 2, security, Ethereum, PoS and validators.
Answers focus on practical wallet, network and security decisions.
Wallets & Keys
Asset records live on the relevant blockchain network. A wallet manages keys and helps read and sign on-chain actions.
A seed phrase typically restores a set of accounts, while a private key directly controls a specific account. Both must remain under the user’s control.
No. Legitimate support should not request seed phrases, private keys or verification codes through chat, email or web forms.
Similar address formats can exist across different networks even though balances and contracts are separate. A network mismatch can prevent the expected arrival.
Networks & Transactions
Gas is the network resource-fee mechanism for executing transactions and smart contracts. Rates vary by network conditions and demand.
A transaction hash is the index used to look up public on-chain status, including pending, success, failure and block information.
Congestion, fee settings, nonce conflicts or node synchronization can be involved. Check the correct network’s on-chain state before taking another action.
Generally not by the wallet alone, so verify address, network, amount and asset before submitting.
Web3 & Approvals
Connection usually does not move assets by itself, but later signatures, transactions and approvals must be reviewed separately.
Not necessarily. A message signature can authenticate, authorize or prove account control. Read the message, domain, expiry and purpose.
A token approval lets a specified contract act within an allowance. Review the spender, amount and ongoing necessity.
No. Disconnecting ends the session, while an on-chain allowance can remain active until changed or revoked.
Many EVM-compatible networks use the same account address format, but chain ID, gas, balances, contracts and history remain separate.
Layer 2 adds execution or data-scaling architecture around mainnet, often retaining a settlement or security relationship and introducing cross-layer waits.
Security, Ethereum & PoS
Verify the full domain and request details, and be cautious of fake support, airdrops, urgency and any page asking for a seed phrase.
No. Rewards can change, exits can involve waits, and validator, smart-contract and market risks remain.
Validators perform consensus duties such as proposing blocks or attesting to state. Performance, network conditions and protocol rules affect outcomes.
Stop signing or transferring, disconnect suspicious pages and review transactions, approvals and network state from a trusted device.
Security reminder
Seed phrases and private keys remain under the user’s control. Legitimate support should not ask for a seed phrase, private key or verification code. Review address, network and amount before transferring; blockchain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps and smart contracts carry risk, so review spender and permission scope and consider revoking unused approvals.