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.
imtoken

Frequently Asked Questions

Practical answers about wallets, networks, transactions, Web3, security and PoS.

A wallet manages keys that control on-chain accounts and organizes network, asset and transaction information. Public-chain assets are not simply stored inside a local wallet file.

A seed phrase is commonly used to derive wallet keys and recover a wallet. Keep it offline and avoid unnecessary copies.

No. Legitimate support should never request a seed phrase or private key. Never send private keys, recovery phrases or verification codes to anyone.

Similar address formats can exist on multiple networks while assets, gas and contracts remain independent. A wrong network can create serious transfer risk.

Verify the receiving address, destination network and asset type, and make the expected network clear to the sender.

Review the address, network, amount, gas and final transaction details. Consider a small test before a larger transfer.

Gas is a mechanism for pricing execution resources on many networks. The actual fee depends on network rules and current conditions.

A transaction hash identifies an on-chain transaction and can be used with a block explorer to verify status.

A connection establishes a session, but later signature, transaction or approval requests still need separate review.

No. Message signatures may prove account control or authenticate, while transaction signatures can change on-chain state. Read both carefully.

An approval gives a smart contract permission to use a token within a defined scope. Review the spender, amount, network and purpose.

Many EVM networks share account and contract concepts, but chain IDs, gas assets and deployments remain separate.

Layer 2 refers to scaling networks with defined relationships to a base layer. Cross-layer transfers can have distinct confirmation and exit flows.

Verify domains and sources independently, never share recovery material through chat or remote-control sessions, and do not let urgency bypass your checks.

No. Rewards can change, exits can take time, and validator, technical and market risks remain.

A validator follows protocol rules to participate in attestations and block proposals while maintaining required operational responsibilities.

Offline behavior, double-signing or other protocol violations can trigger penalties according to network rules.

Stop repeated submissions, keep the transaction hash and verify public status on the correct network. Never provide a private key or seed phrase for troubleshooting.