FAQ
Answers about wallets, seed phrases, networks, gas, DApps, approvals, EVM, Layer 2, security, Ethereum, PoS and validators.
A wallet manages on-chain accounts and signing authority. Asset records live on the relevant blockchain network rather than inside a website.
A seed phrase can usually restore control of a wallet. Keep it offline and never send it to a website, support agent or third party.
No. imtoken will not ask for your private key and cannot recreate a lost private key on your behalf.
Check the asset network, recipient requirements, address format and block-explorer information instead of relying only on a token name.
At minimum, verify the address, network, amount, gas requirement and the actual transaction request.
Gas is the network accounting mechanism used to price transaction execution or contract calls. Fees change with network conditions.
It uniquely identifies an on-chain transaction and can be used in a block explorer to review status, block height and confirmations.
A connection usually establishes account access only, but later signatures, transactions and approvals must still be reviewed separately.
No. A signature can represent authorization, a login proof or transaction intent. Review the source and exact request before deciding.
An approval gives a specific contract permission to use tokens within the granted scope. Excessive allowances or untrusted contracts increase exposure.
An EVM network uses an execution environment compatible with the Ethereum Virtual Machine. Address formats may look similar, but assets and gas are network-specific.
Layer 2 systems relate to a base chain but remain distinct network environments. Cross-layer transfers can involve bridges, waiting times and different fees.
Use trusted entry points, verify domains and request details, and never submit sensitive secrets through unfamiliar links.
No. Rewards can change with network conditions and participation rules, while waiting times, technical risk and market volatility can also matter.
Yes. Depending on protocol rules, validator faults or extended downtime may lead to network penalties.
Stop further signatures or approvals, keep the transaction hash and verify it through a block explorer. If approval risk is involved, review and consider revoking permissions you no longer need.