Help Center
Frequently Asked Questions
Clear answers to practical questions about wallets, networks, Web3, security, Ethereum proof of stake, and validators.
A wallet address is generally used to receive assets and can be shared when needed. Still, verify the network and account, and never confuse a public address with a seed phrase or private key.
A seed phrase can recover a set of wallet accounts, while a private key directly controls a specific account. Both are secret recovery or control material and should be kept offline and private.
No. imtoken will never ask for a seed phrase, private key, or verification code. Stop and verify the source of any request that asks for those secrets.
The same asset name can appear on different networks, and address formats can look similar. The selected network determines where the transaction is submitted, which gas asset is used, and which state records the result.
Verify the receiving address, destination network, and asset type. For contract tokens, confirm the token contract instead of relying only on a name or icon.
Review the recipient address, network, asset, amount, gas, and request details. For unfamiliar destinations or important transfers, a small test can be considered when appropriate.
Gas describes the network fee required to execute a transaction or smart-contract operation. The actual cost depends on network rules, transaction complexity, and current network conditions.
A transaction hash is a unique reference that can be used with the appropriate block explorer to inspect submission, execution, and confirmation status on the correct network.
Network congestion, fee settings, propagation, or the state of an earlier transaction can affect confirmation. Check the transaction hash on the matching network before deciding on a next action.
No. Connection, message signing, transaction signing, and token approval are separate requests. Review the domain, account, contract, amount, and permission scope each time.
A token approval gives a specified contract or address permission to use a token under defined conditions. Check the spender and allowance before approving, and consider revoking permissions that are no longer needed.
No. Signatures can be used for login, messages, or transactions, but malicious signing requests can still create risk. Understand what the signature authorizes before confirming it.
Many EVM-compatible networks share a similar account and contract model, so address formats can match. Assets, gas, contract state, and transaction history still belong to each specific network.
A Layer 2 system has a defined relationship with a base layer for data, settlement, or security. Moving assets across layers usually requires a supported bridge route and may involve additional confirmation or waiting periods.
Once a transaction is confirmed by the network, it generally cannot be reversed by a wallet provider alone. That is why checking the address, network, amount, and request details before sending is important.
No. Rewards can change with network conditions, validator performance, and protocol rules. Exit may involve waiting, validators can face penalties, and digital-asset prices can fluctuate.
Consider validator uptime, network penalties, exit queues, waiting periods, smart-contract risk, third-party service risk, and asset-price volatility before deciding whether participation fits your circumstances.