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

FAQ: Wallet, Networks, Web3 and Security

Answers about wallets, seed phrases, private keys, networks, transfers, gas, transaction hashes, DApps, approvals, EVM, Layer 2, Ethereum, PoS and validators.

Asset records live on the relevant blockchain. A wallet manages account access and signing capability. Changing devices does not move assets by itself; protecting and restoring access credentials is the critical part.

Prefer a private offline method that can survive long-term storage. Avoid chat, email, ordinary cloud drives and screenshots. Legitimate staff should not ask for your seed phrase.

Usually not. A password change does not invalidate a private key that has already been exposed. From a trusted environment, assess asset migration and approval revocation.

The same account can hold separate assets and history on multiple networks. Confirm the active network first, then verify the token contract and transaction records.

At minimum, verify the network, full destination address, asset, amount and fee. For a new destination or larger amount, consider a small test transfer first.

Gas is the fee paid for network computation and block space. It changes with congestion and transaction complexity. Paying more gas does not make an action absolutely safe.

A transaction hash lets you query status, block inclusion, sender, recipient, amount and fees in the relevant block explorer. It is a key troubleshooting reference.

A basic account connection usually does not move assets, but later signatures, approvals and transactions can have on-chain consequences. Review each request separately.

Some signatures are used for login, but structured signatures can also authorize orders or permissions. No gas fee does not mean no risk.

An approval lets a specific contract or address spend up to an allowed amount of a token. Verify the spender and allowance and consider revoking permissions you no longer need.

They share a broadly similar contract execution model and address format, but chain IDs, gas assets, contract deployments and risks remain different.

Some Layer 2 designs include challenge, settlement or protocol waiting periods. The timing depends on the specific system and is not necessarily a sign of failure.

Use trusted entry points, verify domains, never enter recovery secrets on unfamiliar pages and do not let a fake airdrop, countdown or support message rush you into signing.

No. Rewards vary with network conditions, validator performance and protocol rules. Waiting periods, penalties, technical issues and asset-price volatility can also affect outcomes.

Proof-of-stake networks use rewards and penalties to encourage correct participation. Downtime or protocol violations can reduce rewards or trigger stronger penalties.

You can share the network, public account address, asset type and transaction hash. Do not provide a seed phrase, private key, recovery phrase or verification code.

Security reminder

imtoken staff will not ask for your seed phrase, private key or verification code. Review the network, address, signing request and permission scope before acting.