Frequently Asked Questions

A digital wallet helps manage blockchain accounts and signing actions. Asset records live on blockchain networks; the wallet helps you control the keys and requests used to access those accounts.

A seed phrase commonly restores a group of wallet accounts, while a private key controls a specific account. Both are highly sensitive and should never be sent to another person or entered into a third-party website.

Offline storage can reduce exposure to cloud leaks, screenshot syncing, malware, and accidental sharing. Keep the backup complete, readable, and under your own control.

Some EVM-compatible networks use the same address format, but assets and transaction records remain separate by network. Always confirm the destination network before sending.

Check the destination address, network, asset, amount, and expected gas. For an important transfer, a smaller test transfer can help verify the setup.

Gas is the network fee mechanism used to execute transactions or smart-contract actions. Cost can vary with protocol rules, transaction complexity, and congestion.

A transaction hash is a public identifier for an on-chain transaction. Use it with the correct block explorer to review status, block inclusion, and confirmations.

First verify the transaction and address on the correct block explorer. Then confirm the selected network and token contract; wallet indexing or RPC data can sometimes update later than the chain itself.

A basic connection generally creates an account session, but later signatures, approvals, or transaction requests can carry risk. Review each request independently.

No. Transaction signatures typically authorize on-chain state changes, while message signatures may be used for login or proof of account control. Malicious messages can still be abused, so read the exact request.

An approval gives a smart contract permission to use a token within a defined scope. Review the target and amount, and consider revoking permissions you no longer need.

The EVM is an execution environment and rule set for smart contracts. Many networks are EVM-compatible, which is why addresses, gas concepts, and contract interactions can look similar.

Layer 2 systems process activity away from mainnet while maintaining a defined relationship with it. Moving assets between layers may involve bridges and waiting periods.

Check the full domain, source, page request, and wallet prompt. Do not trust a page only because it appears in an ad, a private message, or uses a familiar logo.

No. imtoken staff will not ask for your seed phrase, private key, or verification code. Treat any such request as high risk.

No. Rewards can change with network and protocol conditions, and participation can involve exit delays, validator penalties, technical risks, and asset-price volatility.

Validators participate in network consensus and block validation while following protocol rules. Duties, rewards, and penalties depend on the specific network.

Stop further signing or transfers. Check the transaction hash, contract address, approval target, and active network. Never provide a seed phrase, private key, or verification code during troubleshooting.