Frequently Asked Questions

Asset state is recorded on the relevant blockchain. A wallet helps manage keys, addresses, networks and transaction requests rather than moving public-chain assets into the application.

No. imtoken will never ask for a seed phrase, private key or verification code. A request for any of these should be treated as a high-risk signal.

Many EVM networks use the same account-address format, but chain IDs, balances, token contracts and transaction state remain separate. Always verify the active network.

On-chain transactions generally cannot be reversed by a wallet alone. Keep the transaction hash, identify the actual network and then evaluate the receiver or protocol context.

Gas measures the computational resources required for a transaction or contract operation. Final cost depends on network conditions, operation complexity and fee parameters.

A transaction hash is a public identifier that lets you locate a transaction on the correct block explorer and review its status, block and related addresses.

No. Wallet connection, message signing, transaction signing and token approvals are different actions. Review each request independently.

Do not assume that. Some signatures are used for authentication or later protocol permissions. If the meaning is unclear, do not sign it just because a site creates urgency.

It lets a specified contract use a token within an approved scope. Check the spender, amount and need for the permission, and consider revoking permissions you no longer use.

Layer 2 systems process activity with scaling mechanisms tied to mainnet settlement or data. Cross-layer movement can use dedicated deposit, bridge or withdrawal flows and waiting periods.

Check the domain source and spelling. Be cautious with search ads, impersonated support, fake airdrops, unexpected downloads, remote-control requests and any page asking for recovery material.

Avoid it. Shared devices may contain keyloggers, remote-control software, malicious extensions or other unknown risks. Prefer a device you control and keep updated.

No. Rewards can change with network conditions and are not guaranteed. Exiting can also involve queues or waiting periods.

Yes. Long periods offline, incorrect duties or serious protocol violations can lead to different forms of network penalties.

Not necessarily. Exit and withdrawal are separate stages, and network queues or protocol state can introduce waiting time.

Stop repeating the action, preserve the transaction hash and relevant details, verify the network, addresses and contracts, and review permissions that may no longer be needed.