imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.
imtoken FAQ

Frequently Asked Questions

Answers to common questions about wallets, networks, transfers, gas, DApps, approvals, security, Ethereum staking, PoS and validators.

Security reminder

Never share a seed phrase, private key or verification code.

A digital wallet manages on-chain accounts and signing authority. Assets are recorded on blockchain networks, while the wallet helps users manage keys, addresses, networks and transaction actions.

A seed phrase can usually derive one or more account keys, while a private key directly controls a specific account. Both are highly sensitive and should be stored offline rather than in screenshots, cloud drives or chat messages.

No. Users are responsible for their seed phrase and private keys. imtoken staff will not ask for them and cannot recover a private key on the user’s behalf.

Many EVM-compatible networks use the same address format, but balances, gas assets and chain state are independent. Always verify the destination network.

Gas is the pricing mechanism for the computation needed to execute transactions or smart-contract operations. Actual cost depends on network conditions, transaction complexity and fee parameters.

A transaction hash is a public identifier that can be checked in a block explorer to review status, confirmations and execution results.

The transaction may still be pending, or you may be viewing a different network or token contract. Check the transaction hash, network and confirmation state first.

A connection alone usually does not move assets, but later signatures, approvals or transactions can have real effects. Review every request separately.

No. A message signature may prove identity or accept a statement, while a transaction signature can submit an on-chain state change. Both require checking the domain, content and purpose.

A token approval allows a contract to use a token within a specified allowance. Verify the spender and scope, and consider revoking approvals you no longer need.

If a contract with a very large allowance is compromised or malicious, the potential scope of loss can be larger. Use approval scope that fits the actual task.

The EVM is an execution environment for smart contracts. Multiple networks use compatible designs, so addresses and contract interaction patterns can look similar even though chain state is separate.

Layer 2 systems generally improve scalability while using mainnet for part of their security or settlement. Cross-layer transfers can involve bridge mechanisms, confirmation steps and waiting periods.

Verify domains, avoid sensitive links from unsolicited messages, never share a seed phrase or private key, and review signatures and contract details before approval.

No. Rewards can change, exits may involve waiting, validators can be penalized, asset prices can fluctuate and smart contracts can contain technical risk.

A validator participates in block proposals and consensus under network rules. Uptime, penalties and exit mechanics can affect participation outcomes.

Shared devices may contain malware, browser residue or remote-control software. Key and signature operations are safer on devices you control.

Reject or close it first, then verify the domain, network, contract and request details. Do not continue when information is incomplete, and never send a seed phrase, private key or verification code to anyone.