Help Center
Frequently Asked Questions
Answers to common questions about wallets, networks, gas, DApps, security, Ethereum, PoS, and validators.
Answers organized around real wallet decisions
Questions cover wallet basics, networks, transactions, Web3 permissions, security, Ethereum PoS, and validators. The answers remain readable without JavaScript.
A digital wallet helps manage blockchain accounts controlled by private keys. The interface can show addresses, balances, and transactions, while the underlying state is recorded by the relevant blockchain network.
A seed phrase can commonly restore a set of wallet accounts, while a private key directly controls a particular account. Both are sensitive and should never be shared or entered into an untrusted site.
The same asset name can exist on multiple networks, and address formats may look similar. Verifying the intended network before sending helps reduce routing mistakes.
Gas refers to the computation cost associated with blockchain transactions or contract execution. The actual fee can change with network conditions and transaction complexity.
A transaction hash is an identifier used to locate an on-chain transaction in a block explorer and inspect broadcast, confirmation, or failure status.
No. Connection requests, message signatures, transaction signatures, and token approvals are separate actions and should be reviewed independently.
No. A signature may be a login message or may relate to more consequential permissions. Review the domain, request text, and context before signing.
A token approval allows a specified contract to act on a token within an allowance. Review the target and amount, and consider revoking approvals that are no longer needed.
EVM networks generally support the Ethereum Virtual Machine and related contract models, but fees, block times, bridges, and risk profiles can differ.
Layer 2 systems extend transaction processing while settling or anchoring in relation to a base chain. Moving assets between layers can involve bridges, waiting periods, and different confirmation rules.
Prefer offline backup. Avoid screenshots, plaintext cloud storage, messaging apps, and sharing it with another person.
Do not provide a seed phrase, private key, or verification code. Do not install unknown remote-control software or sign transactions you do not understand.
High-value actions are better avoided on public networks or shared devices. If use is unavoidable, reduce exposure and verify the device and network environment carefully.
Ethereum uses proof of stake, where validators participate in proposing and attesting to blocks. Users should understand rewards, exits, and penalty mechanisms before participating in related services.
No. Rewards may change, exits may involve waiting periods, validators can face network penalties, smart contracts can fail, and digital asset prices can fluctuate.
PoS protocols can penalize validators for prolonged downtime or behavior that violates network rules. The exact mechanism depends on the protocol.
Once confirmed, an on-chain transaction generally cannot be unilaterally reversed by a wallet. Check the address, network, amount, and request details before broadcasting.
No. imtoken will never ask for a seed phrase, private key, or verification code through a webpage form or support conversation.
