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.

Frequently Asked Questions

Clear answers to common wallet, network, Web3, security and validator questions.

An address can be shared for receiving assets. A private key controls signing authority and must remain secret.

It is safer to avoid screenshots because cloud sync, malware or device backups can increase exposure. Prefer an offline backup.

No. Private keys remain under user control. imtoken will never ask you to send a private key for recovery.

The same asset can exist on multiple networks and address formats may look similar. A network mismatch can lead to an unintended result.

Gas depends on network demand, block space and execution complexity, so it is not a fixed service charge.

It is a unique reference that can be used with a block explorer to check status, block inclusion and confirmations.

Check the corresponding network explorer first. Do not repeat the transfer merely because an interface appears delayed.

Connection alone is not the same as a transfer, but later signatures, transactions or approvals can grant additional capabilities and must be reviewed.

No. A message signature can prove control or express consent, while a transaction signature authorizes an on-chain state change.

It allows a specified spender or contract to use tokens within an allowance. Review both the spender and the amount.

Use a trusted approval-management method on the correct network, submit the revocation or allowance change, and verify the resulting transaction.

Many EVM-compatible networks use the same address format, but their state is separate. The network still needs to be verified.

Layer 2 systems expand transaction processing while keeping a settlement or data relationship with a base network. Cross-layer transfers can add steps.

Check the domain, source and exact request. Any page asking for a seed phrase, private key or verification code should be treated as unsafe.

No. Rewards can change, validators can be penalized, exits can involve waiting and asset prices can fluctuate.

Validators that remain offline or violate protocol rules can face reduced rewards or network penalties.

Use caution. Public networks and shared devices can increase the risk of monitoring, interception or credential exposure.

Generally not by the wallet alone. This is why the address, network and amount should be checked before signing.