On this page
Core concepts
gas fees rarely appears in isolation. It often intersects with gas limits and block inclusion. A useful pattern is to separate each action into four checks: identify the object, verify the network, review permissions, and confirm the result. If one of those checks cannot be completed, stop and verify rather than relying on an unfamiliar site or remote instructions.
For gas fees, first define its role in the current task, then check whether gas limits and block inclusion are consistent. When confirmation counts is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For failed transactions, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: gas fees
- Cross-check: gas limits and block inclusion
- Review carefully: confirmation counts
- Verify afterward: failed transactions
Checks before you act
When using imtoken for Gas & Confirmations, prioritize information that can be independently verified, such as addresses, network names, contract addresses, transaction hashes and block-explorer records. Visual design, urgency messages or claims from an unknown support account are not substitutes for verifiable on-chain details.
For gas limits, first define its role in the current task, then check whether block inclusion and confirmation counts are consistent. When failed transactions is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For gas fees, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: gas limits
- Cross-check: block inclusion and confirmation counts
- Review carefully: failed transactions
- Verify afterward: gas fees
How to evaluate a live request
From a risk perspective, failed transactions and gas fees deserve an independent review. Once a transaction is confirmed on-chain, a wallet normally cannot reverse it unilaterally. DApps and smart contracts can also introduce permission and contract risks, so every signature, approval and transfer should be understood before it is accepted.
For block inclusion, first define its role in the current task, then check whether confirmation counts and failed transactions are consistent. When gas fees is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For gas limits, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: block inclusion
- Cross-check: confirmation counts and failed transactions
- Review carefully: gas fees
- Verify afterward: gas limits
Risks and boundaries
After a Gas & Confirmations task is completed, review gas limits and block inclusion to make sure the outcome matches the intent. Long-lived approvals and persistent connections should be revisited periodically. Good wallet hygiene is a repeated process of checking critical details and retaining traceable on-chain information, not a one-time setting.
For confirmation counts, first define its role in the current task, then check whether failed transactions and gas fees are consistent. When gas limits is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For block inclusion, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: confirmation counts
- Cross-check: failed transactions and gas fees
- Review carefully: gas limits
- Verify afterward: block inclusion
How to verify the outcome
To understand Gas & Confirmations, treat failed transactions and gas fees as parts of the same on-chain workflow. The interface is only the entry point; the selected network, current chain state and permission scope determine what actually happens. Confirm the destination, source and network before continuing so the meaning of the request stays clear.
For failed transactions, first define its role in the current task, then check whether gas fees and gas limits are consistent. When block inclusion is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For confirmation counts, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: failed transactions
- Cross-check: gas fees and gas limits
- Review carefully: block inclusion
- Verify afterward: confirmation counts
Practical checklist
- Never share your seed phrase, private key or verification code.
- Verify the address, network and amount before sending.
- Review each DApp signature and token approval independently.
- Use transaction hashes and block explorers to verify on-chain status.
- Revoke approvals and disconnect sessions that are no longer needed.