FAQ

Asset state is recorded on the relevant blockchain. The wallet manages addresses, keys and signatures and reads balances and history from the chain.

A private key signs for an address, while a seed phrase commonly restores a related set of keys. Both are sensitive and should not be shared.

No. imtoken personnel will not ask for seed phrases, private keys or verification codes.

The same key can produce the same-looking address on several EVM-compatible networks while balances, gas and histories remain separate.

Review the recipient, network, asset or token contract, amount and gas. A small test can be useful for valuable transfers.

Gas depends on network demand, transaction complexity and the fee model; it is not a fixed wallet charge.

Use it on the correct explorer to inspect broadcast, confirmations, failures and gas use.

Generally no. A wallet normally cannot unilaterally reverse a confirmed on-chain transaction.

A normal connection does not require recovery words or private keys. A webpage asking for them is high risk.

Not necessarily, but it can still support identity or authorization flows, so the source and content matter.

It lets a specified contract spend a token up to an authorized amount. Review both spender and allowance.

No. Cross-chain movement normally requires a bridge and separate verification.

Some designs include message finality, challenge periods or queues, so timing varies.

Verify domains independently, avoid unsolicited asset links and reject requests for wallet secrets or unclear permissions.

No fixed return is guaranteed. Rewards can change and the digital asset price can fluctuate.

Risks can include downtime, protocol penalties, exit queues, configuration errors and third-party or contract exposure.

No. Browser sessions and on-chain token approvals are separate states.

Use caution. High-value and key-sensitive actions are better handled on trusted devices and networks.