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.
Practical answers

FAQ

Answers to common questions about wallets, seed phrases, networks, transfers, gas, DApps, approvals, EVM, Layer 2, Ethereum and validators.

A wallet manages blockchain accounts and signing authority. Whether you personally control the private keys depends on the product model, so understand custody, recovery and supported networks first.

It is not recommended. Screenshots can be synced to cloud services or exposed to other software. Keep recovery material offline and never send it through chat, email or cloud notes.

Treat the wallet as no longer having a reliable security boundary. Create a new wallet on a trusted device and, if possible, move assets you still control. Do not reuse exposed recovery material.

No. Several EVM networks can use similar address formats while maintaining completely separate state. Always verify both the network and the asset network before sending.

Gas is the fee concept used to account for computation and network resources when transactions or contract calls are processed. The cost can change with network conditions and transaction complexity.

A transaction hash is a public identifier that lets you inspect status, sender, recipient, fees and confirmations on the corresponding network’s block explorer.

Congestion, fee settings, transaction ordering or propagation can affect confirmation. Check the public status on the correct network before submitting duplicate transactions.

A connection alone is not the same as a transfer, but later signatures, approvals or contract transactions can have on-chain effects. Review every request separately.

Message signing can prove account control or acknowledge data, while transaction signing may change on-chain state. In both cases, review the origin and the exact request.

An approval can allow a contract to use tokens up to a certain allowance. Unused high allowances increase exposure, so review them periodically and consider revoking them.

No. Compatible address formats do not merge network state or balances. Moving assets across networks requires an explicit bridge or transfer path.

Layer 2 systems generally expand transaction capacity while relying on the base layer for parts of security or settlement, but the exact model differs by network. Check deposit, withdrawal and confirmation rules.

Check the exact domain, how you reached it, the signing request and approval target. Never enter recovery material because of a search ad, private message or impersonated support page.

Use extra caution in untrusted environments. Avoid handling recovery material or important signatures on public devices and networks, and keep your system and browser updated.

No. Rewards can change, exits can require waiting, validators may face penalties, and smart contracts or service providers introduce additional risks.

Validators are expected to follow protocol rules and remain available. Downtime, incorrect behavior or protocol violations can lead to different network penalties.

No. Never send a seed phrase, private key or verification code to anyone. Stop any interaction that requests them for support, recovery or security checks.

Once an on-chain transaction is confirmed, a wallet generally cannot reverse it unilaterally. Recovery depends on address control, network and asset circumstances and cannot be guaranteed.