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.

FAQ

FAQ

Understand FAQ through wallet and backup, networks and transfers and ethereum and pos, with clear checks for networks, addresses, transactions, signatures, approvals and risk.

Control is associated with the private key or seed phrase, not with a public profile or customer-service account.

The same address format or asset symbol can appear on multiple networks. Verify the sender and receiver network before transferring.

Gas is the network execution fee. Its level changes with network conditions and the operation being submitted.

No. Connection, message signing, transaction signing and token approvals are separate requests.

A wallet generally cannot unilaterally reverse a transaction after the network confirms it.

No. Do not send a seed phrase, private key or verification code to anyone.

It identifies a transaction and can be used with the correct network explorer to check status and details.

No. Rewards can change, exits can involve waiting periods, validators can face penalties, and asset prices can fluctuate.

EVM is an execution environment used by Ethereum and compatible networks for smart contracts. Similar compatibility does not make separate networks the same chain.

Layer 2 refers to scaling systems related to a base chain. Cross-layer transfers may involve bridges, different confirmation stages and waiting periods.

A token approval grants a contract or spender permission to use a token up to an allowance. Review the contract and allowance before confirming.

Permissions that are no longer needed can remain active. Reviewing and revoking unnecessary approvals can reduce the permissions exposed to third-party contracts.

Proof of Stake is a consensus approach in which validators participate under protocol rules and can earn rewards or face penalties.

Yes. Rewards depend on network and protocol conditions and are not fixed or guaranteed.

Yes. Exit and withdrawal timing can depend on protocol queues and network conditions.

Yes. Bugs, malicious logic or unexpected interactions can affect outcomes, so contract addresses and requests should be reviewed carefully.