imtoken will never ask for your seed phrase, private key or verification code. Always review the address, network and request details before transferring, signing or approving.
imtoken
Home / Gas & Confirmations
imtoken

Gas & Confirmations

A practical imtoken guide to network fees, gas limit, pending state and confirmations, with clear checks for network, permissions and security.

Download imtoken

Core concepts

Put each term back into its on-chain context: networks, accounts, transactions and contracts have different responsibilities. In the context of network fees, it also helps to connect gas limit with pending state rather than treating them as isolated features. When checking state, prefer verifiable evidence such as network, address, contract and transaction hash. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare network fees with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Practical workflow

When checking state, prefer verifiable evidence such as network, address, contract and transaction hash. In the context of gas limit, it also helps to connect pending state with confirmations rather than treating them as isolated features. Networks can share similar address formats while keeping independent balances, gas assets, block histories and confirmation rules. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare gas limit with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

network fees

Put each term back into its on-chain context: networks, accounts, transactions and contracts have different responsibilities.

gas limit

When checking state, prefer verifiable evidence such as network, address, contract and transaction hash.

pending state

Networks can share similar address formats while keeping independent balances, gas assets, block histories and confirmation rules.

confirmations

When third-party nodes, bridges or contracts are involved, evaluate their technical risk separately from the wallet interface.

Checks before confirmation

Networks can share similar address formats while keeping independent balances, gas assets, block histories and confirmation rules. In the context of pending state, it also helps to connect confirmations with network fees rather than treating them as isolated features. When third-party nodes, bridges or contracts are involved, evaluate their technical risk separately from the wallet interface. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare pending state with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Review checklist

  • Put each term back into its on-chain context: networks, accounts, transactions and contracts have different responsibilities.
  • When checking state, prefer verifiable evidence such as network, address, contract and transaction hash.
  • Networks can share similar address formats while keeping independent balances, gas assets, block histories and confirmation rules.
  • When third-party nodes, bridges or contracts are involved, evaluate their technical risk separately from the wallet interface.

Risks and follow-up

When third-party nodes, bridges or contracts are involved, evaluate their technical risk separately from the wallet interface. In the context of confirmations, it also helps to connect network fees with gas limit rather than treating them as isolated features. Put each term back into its on-chain context: networks, accounts, transactions and contracts have different responsibilities. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.

A useful review habit is to compare confirmations with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.

Key risks

  • Never share a seed phrase, private key or verification code.
  • Third-party DApps, networks and contracts can fail or behave maliciously.
  • Staking and digital assets do not offer guaranteed returns or protection from price volatility.