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.
imtokenimtoken
中文Download

imtoken Knowledge Center

FAQ

Answers covering wallets, networks, Web3, security, Ethereum, PoS and validators.

Download imtokenRead the guide ↓
Safety principle

Never share your seed phrase, private key or verification code. Review the address, network and request details before you sign, approve or transfer.

Wallet and recovery

How to evaluate it

Wallet and recovery is a distinct part of understanding FAQ. Separate interface labels from on-chain facts: an address identifies an account, the selected network determines where the asset and transaction exist, and a signature or approval can change permissions or trigger execution. The goal is not to memorize button positions. A safer habit is to identify the request, the network, the permission being granted and the result you expect before you confirm anything.

Wallet and recovery is a distinct part of understanding FAQ. Separate interface labels from on-chain facts: an address identifies an account, the selected network determines where the asset and transaction exist, and a signature or approval can change permissions or trigger execution. Fees, confirmation speed and supported features vary across networks. A wallet interface is only one view of the activity; the corresponding blockchain record remains the stronger reference for transaction status.

Networks and transactions

Operational and risk points

Networks and transactions is a distinct part of understanding FAQ. Separate interface labels from on-chain facts: an address identifies an account, the selected network determines where the asset and transaction exist, and a signature or approval can change permissions or trigger execution. Fees, confirmation speed and supported features vary across networks. A wallet interface is only one view of the activity; the corresponding blockchain record remains the stronger reference for transaction status.

Networks and transactions is a distinct part of understanding FAQ. Separate interface labels from on-chain facts: an address identifies an account, the selected network determines where the asset and transaction exist, and a signature or approval can change permissions or trigger execution. Use a least-privilege mindset. Never share a seed phrase, private key or verification code, and do not lower your review standard because a request claims to be support, an airdrop, an upgrade or an urgent notice.

Web3 and approvals

How to evaluate it

Web3 and approvals is a distinct part of understanding FAQ. Separate interface labels from on-chain facts: an address identifies an account, the selected network determines where the asset and transaction exist, and a signature or approval can change permissions or trigger execution. Use a least-privilege mindset. Never share a seed phrase, private key or verification code, and do not lower your review standard because a request claims to be support, an airdrop, an upgrade or an urgent notice.

Web3 and approvals is a distinct part of understanding FAQ. Separate interface labels from on-chain facts: an address identifies an account, the selected network determines where the asset and transaction exist, and a signature or approval can change permissions or trigger execution. A repeatable sequence helps: verify the source, check the address and network, review the amount or permission, then keep the transaction hash and verify confirmation on-chain. Stop when details conflict.

Ethereum and validators

Operational and risk points

Ethereum and validators is a distinct part of understanding FAQ. Separate interface labels from on-chain facts: an address identifies an account, the selected network determines where the asset and transaction exist, and a signature or approval can change permissions or trigger execution. A repeatable sequence helps: verify the source, check the address and network, review the amount or permission, then keep the transaction hash and verify confirmation on-chain. Stop when details conflict.

Ethereum and validators is a distinct part of understanding FAQ. Separate interface labels from on-chain facts: an address identifies an account, the selected network determines where the asset and transaction exist, and a signature or approval can change permissions or trigger execution. The goal is not to memorize button positions. A safer habit is to identify the request, the network, the permission being granted and the result you expect before you confirm anything.

Related learning

Security→Academy→

Questions & Answers

Frequently asked questions

How are a wallet and an account related?

A wallet manages keys and constructs requests, while account state and assets are recorded on the relevant blockchain. Changing a device or interface does not automatically move those assets.

Should I store a seed phrase in a screenshot?

That is not recommended. Screenshots may sync to cloud storage or become readable by other software. Use an offline backup method instead.

Can I send a private key to support?

No. Stop any troubleshooting flow that asks you to send a private key, seed phrase or verification code.

Why can the same address appear on different networks?

Some networks use compatible address formats, but assets remain recorded separately on each network. Always verify the network.

What should I check before sending?

At minimum, review the recipient address, network, asset, amount and gas, then check them again on the confirmation screen.

Is gas a platform fee?

Gas is generally a network resource and execution fee. Its cost can vary with protocol rules and network demand.

What is a transaction hash for?

A transaction hash is a unique transaction identifier that can be used with a block explorer to inspect broadcast, execution and confirmation state.

Does connecting to a DApp automatically move assets?

A connection usually establishes account access, but later signatures, approvals or transactions can have different effects. Review each one separately.

Are message signatures and transaction signatures the same?

Not exactly. Message signatures may prove identity or authorize protocol actions, while transaction signatures usually request an on-chain state change. Both need review.

What is the risk of unlimited approval?

A large allowance can give a contract broader future spending permission. Understand the target and revoke permissions you no longer need.

Why do EVM networks look similar?

EVM networks can share account and contract patterns, while chain IDs, gas assets, balances and deployed contracts remain separate.

Are Layer 2 assets the same as mainnet assets?

The systems are related, but asset location, bridge state and settlement confirmation still need to be evaluated separately.

How can I reduce phishing risk?

Verify domains and sources, avoid wallet links from unsolicited messages, do not install unknown software and reject “support” requests for remote device control.

Does Ethereum staking guarantee returns?

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

Can PoS validators be penalized?

Yes, depending on protocol rules. Downtime, consensus violations or other validator conditions can affect outcomes.

What information is safe to use for troubleshooting?

Prefer non-sensitive public information such as the network name, transaction hash, public address and visible error message. Never send recovery secrets.