imtoken Help Center
FAQ
These questions cover common topics across wallets, networks, transactions, DApps, security, Ethereum, PoS and validators.
No. Your seed phrase and private keys are yours to protect. Official personnel should never ask for, store or request them or your verification codes.
The same asset can exist on different networks. Choosing the wrong network can prevent a transfer from arriving as expected, so check the address, network and amount together.
Gas describes network fees required to execute on-chain actions. Costs can vary with network conditions and operation complexity, and fee models differ by network.
A transaction hash is a unique identifier that can be used in a block explorer to check whether a transaction was broadcast, confirmed or failed.
No. A connection, token approval, transaction signature and message signature are different requests and should be reviewed separately.
Old permissions can leave unnecessary access in place. Review what is still needed and consider revoking authorizations you no longer use.
Layer 2 systems usually rely on a base chain for security or settlement while improving throughput or cost. Bridging, confirmations and exits can follow different rules.
Many EVM-compatible networks use similar address formats, but their state, token contracts and Gas assets differ. An address alone does not identify the network.
Once confirmed, a blockchain transaction generally cannot be reversed by the wallet alone. Check the address, network and amount before submitting.
Do not provide it. Official personnel will not ask for your seed phrase, private key or verification code. Stop and verify through a trusted entry point.
Use caution. Shared networks and devices add environmental risk. Sensitive actions are better performed on a device and network you control and trust.
A message signature can prove that an address signed specific data. Malicious pages can still disguise risky requests, so read what you are signing.
An allowance defines how much a contract can spend for a token. Unlimited approval is not always necessary; match permissions to the actual task.
No. Rewards can change, exits may involve waiting, validators can face protocol penalties, and smart-contract and market-price risks remain.
In a PoS network, validators participate in proposing or attesting to blocks and help maintain consensus. Reward and penalty mechanics are defined by the protocol.
Do not rush to approve it. Check the domain, network, contract and request type. If the meaning is still unclear, reject it and consult trusted references.
Network confirmations, node synchronization, token recognition or the selected network can affect display. Check the transaction in a block explorer for the correct network.
It is not recommended. Screenshots may be synced to cloud storage or exposed to other apps. An offline record stored securely is safer.
Need a clearer learning path?
Start with the academy and follow the wallet, network, Web3 and security topics in order.
