Understand the mechanism before rewards
Answers to common questions about wallets, networks, transfers, DApps, security, Ethereum and validators. In real use, wallet, network and gas often intersect. A wallet screen is only one layer of information, so start by identifying the account, the active network and the task you intend to complete. Then verify the result against on-chain data instead of treating one button or balance as proof that everything is correct.
It helps to separate interface display from blockchain state. Information related to network can depend on the selected network, node data, a block explorer or a token contract, while gas may need a transaction hash and confirmation status. If something looks wrong, inspect the network and address first, then the contract or transaction, rather than repeatedly retrying the same action.
How network state can change outcomes
It helps to separate interface display from blockchain state. Information related to network can depend on the selected network, node data, a block explorer or a token contract, while gas may need a transaction hash and confirmation status. If something looks wrong, inspect the network and address first, then the contract or transaction, rather than repeatedly retrying the same action.
Before an action involving DApp, break the decision into smaller questions: who is the target, which network is involved, what permission is being requested, what fee can be incurred and whether the outcome is reversible. For security, read the confirmation details carefully. If you cannot explain the target or consequence, exit the flow and verify the source before continuing.
- Review network and gas before submitting.
- Keep verifiable references such as a transaction hash, contract address or network name.
- Stop if a request is unclear and verify the source and permission scope again.
- Confirm how the active network relates to wallet.
Exits, waiting periods and technical risk
Before an action involving DApp, break the decision into smaller questions: who is the target, which network is involved, what permission is being requested, what fee can be incurred and whether the outcome is reversible. For security, read the confirmation details carefully. If you cannot explain the target or consequence, exit the flow and verify the source before continuing.
A reliable routine is “check before, record after, verify when uncertain.” Before submitting, confirm the address, network and amount. After submitting, keep the transaction hash. During a delay, use an appropriate block explorer to check confirmations. This gives you verifiable evidence when a balance is slow to refresh or a third-party page behaves unexpectedly.
Evaluate third-party services separately
A reliable routine is “check before, record after, verify when uncertain.” Before submitting, confirm the address, network and amount. After submitting, keep the transaction hash. During a delay, use an appropriate block explorer to check confirmations. This gives you verifiable evidence when a balance is slow to refresh or a third-party page behaves unexpectedly.
Security is not a separate final step; it should run through the entire Frequently Asked Questions workflow. Keep seed phrases and private keys under your own control, and never send them in chat or to someone claiming to be support. Treat every DApp connection, signature and approval as a separate decision, and periodically review permissions you no longer need.
- Review network and gas before submitting.
- Keep verifiable references such as a transaction hash, contract address or network name.
- Stop if a request is unclear and verify the source and permission scope again.
- Confirm how the active network relates to wallet.
Checks to complete before participating
Security is not a separate final step; it should run through the entire Frequently Asked Questions workflow. Keep seed phrases and private keys under your own control, and never send them in chat or to someone claiming to be support. Treat every DApp connection, signature and approval as a separate decision, and periodically review permissions you no longer need.
Answers to common questions about wallets, networks, transfers, DApps, security, Ethereum and validators. In real use, wallet, network and gas often intersect. A wallet screen is only one layer of information, so start by identifying the account, the active network and the task you intend to complete. Then verify the result against on-chain data instead of treating one button or balance as proof that everything is correct.
Common questions
What is the difference between an address and a private key?
An address can be shared for receiving assets. A private key controls assets and must remain secret.
Can I send my seed phrase to support?
No. imtoken staff will never ask for a seed phrase or private key.
What are the three most important transfer checks?
Verify the address, network and amount, then review fees and the requested action.
Why is a submitted transaction still pending?
Transactions must be included and confirmed by the network; congestion and fee conditions can affect timing.
Is gas paid to the wallet?
Gas is part of the network execution and fee mechanism, not simply a wallet service fee.
Why keep a transaction hash?
It is the main reference for checking on-chain status in a block explorer.
Does connecting to a DApp automatically let it move assets?
No. Connection, signatures and token approvals are separate actions that should be reviewed independently.
Does a message signature create a transaction?
Not necessarily, but a signed message can still carry permission or identity risk.
What is a token approval?
It grants a specific spender permission to use a token within an allowance.
Why are unlimited approvals risky?
A broad allowance can increase exposure if the spender is compromised; review and revoke permissions you no longer need.
Why do EVM networks often use similar address formats?
Many EVM-compatible networks use similar address formats, but assets still belong to separate networks.
Is Layer 2 the same chain as the base layer?
A Layer 2 is related to its base layer but has its own execution environment and asset transfer paths.
Should I use a wallet on public Wi-Fi?
Treat public networks cautiously and avoid sensitive activity when the environment or certificate trust is uncertain.
Does Ethereum staking guarantee returns?
No. Rewards vary and there can be waiting periods, validator penalties, smart-contract risk and market volatility.
Why can validators be penalized?
Prolonged downtime or protocol violations can result in network-level penalties.
Can a wallet reverse a confirmed on-chain transaction?
Usually not. This is why address, network and amount checks matter before submission.
Security reminder
imtoken staff will never ask for your seed phrase or private key. Do not send seed phrases, private keys or verification codes to anyone. Before transferring, signing or approving, verify the address, network, target and scope. Third-party DApps and smart contracts may introduce independent risks.