imtoken · FAQ
FAQ
Common questions about wallets, blockchain networks, transfers, Web3, security and proof of stake, answered with clear mechanics and risk boundaries.
Asset state is recorded by the relevant blockchain. A wallet manages keys, addresses and transaction actions and reads network state for display.
A seed phrase can often restore an entire wallet. Anyone with the complete phrase may be able to control the associated accounts, so it should be kept private and offline where possible.
No. imtoken staff will not ask for a private key, seed phrase or verification code as part of normal support.
Assets exist on a specific chain. Similar address formats do not make networks interchangeable, so both sides should agree on the exact network.
Gas is the network resource fee required for a transaction or smart-contract operation. Cost varies with network conditions and transaction complexity.
A transaction hash uniquely identifies a submitted transaction and can be checked on the appropriate block explorer for pending, success or failure status.
A normal connection usually exposes a public account and starts a session. Asset changes require later signatures or transactions, which should each be reviewed.
No. Some signatures can represent login, permission or protocol intent. A request can matter even when it does not use gas.
Approval grants a designated spender contract permission to use a defined amount of a token. Review the spender, token, allowance and purpose.
No, but it increases potential exposure. Judge it based on the contract, intended use and your own risk tolerance.
Many EVM-compatible chains share an address format, while chain IDs, gas assets and state remain separate. The network still has to be selected correctly.
Layer 2 systems scale activity while remaining linked to a main chain. Deposits, withdrawals and exit timing vary by design.
Most confirmed on-chain transactions cannot be reversed by a wallet provider. Check the address, network, asset and amount before signing.
No. Rewards can change with network conditions, validator performance and protocol parameters, and exits may involve waiting.
Downtime or protocol violations can reduce rewards or cause penalties, alongside technical, service and market risks.
Stop signing or approving, do not disclose secrets, reopen the service from a trusted entry point and inspect any on-chain approvals you may have granted.