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.

FAQ

Frequently Asked Questions

Practical answers focused on checks you can perform yourself. imtoken will never ask for a seed phrase, private key or verification code.

A wallet manages addresses, keys and on-chain requests. It is not simply a server account that stores blockchain assets; the relevant network records asset state.

Keep it offline, private and readable for the long term. Do not send it to another person or enter it into an unfamiliar website.

No. A wallet provider generally cannot remotely reset or recover a private key. If it is exposed, assess the assets and permissions linked to it.

The network determines balances, gas assets, contracts and transaction history. Similar address formats do not make networks interchangeable.

Confirm the receiving address, destination network and asset, and make sure the sender is using the same intended network.

Verify the address, network, asset, amount and gas, then keep the transaction hash after submission.

Gas is the network fee mechanism for executing transactions or smart-contract operations. Pricing changes with network conditions.

It identifies a transaction and can be used to look up its status and confirmations on the relevant block explorer.

A connection is different from a transfer, but later signatures, approvals or transactions can have on-chain effects and should be reviewed separately.

No. A message signature proves approval of data, while a transaction signature commonly authorizes an on-chain state change. Both deserve review.

It gives a specified smart contract permission to use tokens within an allowance. Review the spender and amount.

EVM networks share a compatible account model, so address formats can look alike. Chain IDs, gas assets and contract state remain network-specific.

Layer 2 systems expand capacity while remaining connected to a base layer. Moving across layers can involve bridges and waiting periods.

Verify domains, reject requests for secret keys, do not let urgency or fake airdrops bypass your checks, and avoid remote-control requests from strangers.

Sensitive actions are better performed on trusted devices and networks. Public environments add observation, interception and misclick risks.

No. Rewards can change, and participation may involve exit waiting, validator penalties, contract risk and digital-asset price volatility.

Validators participate in consensus duties such as attestations and block proposals to help the network maintain shared state.

Consider revoking permissions that are no longer needed to reduce long-lived contract access.