FAQ
Frequently Asked Questions
Use these answers as a starting point for understanding wallets, networks, transactions, Web3, security and proof of stake. For any action involving assets or permissions, verify the details shown in your own network context.
A wallet manages keys, accounts and transaction requests, while asset balances are recorded on blockchain networks. The interface presents that network state and helps the user prepare signed actions.
You should keep it under your own control. Prefer offline backup and never send it to support staff, websites, chat contacts, DApps or other people. imtoken personnel will not ask for it.
No. An address is used publicly to identify an account or receive assets. A private key authorizes actions for the account and must remain secret.
Balances and transaction history exist on a specific chain. Compatible networks may use similar addresses while having separate ledgers, gas assets and token contracts.
Verify the full destination address, intended network, asset, amount and gas. Confirm the recipient expects the same network, and consider a small test when appropriate.
Gas represents the network resources required to process a transaction or smart-contract call. It is usually paid with the network’s native asset and can vary with demand and execution complexity.
It is an identifier for a submitted transaction. Use it with a block explorer for the correct network to inspect whether the transaction is pending, confirmed or failed.
On-chain transactions generally cannot be reversed by a wallet alone after the network has accepted them. This is why destination, network and amount checks matter before submission.
A normal wallet connection should not reveal the private key. It can expose approved account information and create an interaction session, while later signatures and approvals still require separate review.
Message signatures and transaction signatures can have different effects. Confirm the requester, content, network and intended result, and stop when the request is unclear or unrelated to your action.
A token approval records permission for a specified contract or address to use tokens within a defined scope. It may persist on-chain until changed or revoked.
Usually not. Front-end connection state and on-chain approvals are separate, so permissions that are no longer needed should be reviewed independently.
It means a network supports an Ethereum-style smart-contract execution environment. Compatible networks can share account and contract patterns while still having separate chain state, gas and contracts.
Not necessarily. Layer 2 describes a scaling and settlement relationship with a base layer. Many Layer 2 systems are EVM-compatible, but the two terms describe different properties.
Stop the interaction. Do not share seed phrases, private keys or verification codes with anyone, including supposed support staff. Re-enter through a trusted source and review whether any transaction or approval was created.
They add avoidable exposure through shared devices, browser residue, network interception or malware. Sensitive recovery operations are better performed in an environment you control.
No. Rewards can change with protocol and network conditions. Validators can face penalties, exits can involve waiting, and smart-contract, third-party-service and digital-asset price risks can also apply.
A validator performs protocol-defined consensus duties such as block proposal or attestation. Status, performance, rewards, penalties and exit mechanics are governed by network rules.