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.
Home / Security / Transaction Checks

imtoken · Security

Transaction Checks

The final seconds before submission are valuable. Address, network, amount, asset and fee should match the intended action, and the transaction hash should be saved so the result can be checked independently.

On this pageCore Security PrinciplesTypical Risk ScenariosHow to Recognize Suspicious RequestsWhat to Do When Something Looks WrongRoutine ChecklistSecurity Statement

Core Security Principles

To understand Transaction Checks, start by separating the wallet interface from the underlying chain state. The final seconds before submission are valuable. Address, network, amount, asset and fee should match the intended action, and the transaction hash should be saved so the result can be checked independently.

Address should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. Network should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. Amount should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. If the origin or meaning of a request cannot be verified, stopping and checking a trusted source is safer than approving something that is not understood.

Typical Risk Scenarios

In everyday use, network, amount and gas often appear in the same workflow. They should be evaluated together in the context of the user’s actual intent rather than as isolated interface labels.

Network should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. Amount should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. Gas is paid in the network’s required fee asset and reflects execution resources rather than a service charge from the wallet. If the origin or meaning of a request cannot be verified, stopping and checking a trusted source is safer than approving something that is not understood.

addressAddress should be verified in the context of the active network, the user’s intended action and the information shown by the wallet.
networkNetwork should be verified in the context of the active network, the user’s intended action and the information shown by the wallet.
amountAmount should be verified in the context of the active network, the user’s intended action and the information shown by the wallet.
gasGas is paid in the network’s required fee asset and reflects execution resources rather than a service charge from the wallet.

How to Recognize Suspicious Requests

A useful review model has three moments: confirm the intended context before acting, inspect the requested permission while signing, and verify the public result after submission. This keeps interface assumptions separate from on-chain facts.

Amount should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. Gas is paid in the network’s required fee asset and reflects execution resources rather than a service charge from the wallet. A transaction hash is the main reference for checking on-chain status. If the origin or meaning of a request cannot be verified, stopping and checking a trusted source is safer than approving something that is not understood.

What to Do When Something Looks Wrong

Many problems that appear complicated are really context mismatches: the wrong network, an unexpected contract, a stale permission or a transaction that is still pending. Breaking the problem into those parts makes independent verification easier.

Gas is paid in the network’s required fee asset and reflects execution resources rather than a service charge from the wallet. A transaction hash is the main reference for checking on-chain status. Address should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. If the origin or meaning of a request cannot be verified, stopping and checking a trusted source is safer than approving something that is not understood.

  • Never share a seed phrase, private key or verification code.
  • Verify the domain, network and contract before approving.
  • Reject unexpected signing requests.
  • Review and revoke permissions you no longer need.

Routine Checklist

A repeatable routine is more dependable than memory. Confirm the network first, then the destination or contract, then the amount, fee and request details, and finally keep the transaction hash or approval record for later checking.

A transaction hash is the main reference for checking on-chain status. Address should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. Network should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. If the origin or meaning of a request cannot be verified, stopping and checking a trusted source is safer than approving something that is not understood.

  • Confirm the active network
  • Verify the destination or contract
  • Review the amount and fee
  • Understand the signature or approval
  • Keep the transaction hash for verification

Security Statement

The next step is to connect this topic with transfer checks, wallet security and Web3 permissions. Good technical knowledge should help a user decide what to inspect when a request is unfamiliar, not merely define terminology.

Address should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. Network should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. Amount should be verified in the context of the active network, the user’s intended action and the information shown by the wallet. If the origin or meaning of a request cannot be verified, stopping and checking a trusted source is safer than approving something that is not understood.

Seed Phrases & Private Keys →Support →Security →