Core Security Principles
The final review before an on-chain submission matters: address, network, asset, amount, fee and action type should all match the intended transaction. The practical way to understand Transaction Checks is to place it inside a real user journey rather than memorize isolated terms. 在链上提交前逐项核对地址、网络、金额和费用 should be checked before an action, during confirmation and again after completion. Verify the entry point and network first, read addresses, permissions, fees and request details at confirmation, then use on-chain records to validate the outcome.
Many mistakes around Transaction Checks begin with information that looks familiar: similar network names, address formats, token symbols or interface layouts. Prefer details that can be independently checked, such as the full domain, network name, contract address, transaction hash and a matching block-explorer record, instead of relying on icons, nicknames or screenshots. For Transaction Checks, break the task into small points that can be verified rather than continuing while the network, address, permission or transaction state is still unclear.
Pre-action check
Confirm that the page and network match the task, then review public addresses, assets, fees or permission details. A familiar interface is not a reason to skip the request details of a third-party DApp or smart contract.
Common Risk Scenarios
Do not verify only the first few address characters. Where possible, compare the full address or multiple segments and confirm the source you copied it from. Many mistakes around Transaction Checks begin with information that looks familiar: similar network names, address formats, token symbols or interface layouts. Prefer details that can be independently checked, such as the full domain, network name, contract address, transaction hash and a matching block-explorer record, instead of relying on icons, nicknames or screenshots.
imtoken treats user review as the final decision point for Transaction Checks. This site never asks for seed phrases, private keys or verification codes, and it does not promise that confirmed on-chain transactions can be reversed by the wallet. DApps, smart contracts, networks and third-party services each introduce their own risk boundaries. For Transaction Checks, break the task into small points that can be verified rather than continuing while the network, address, permission or transaction state is still unclear.
Confirmation check
Confirm that the page and network match the task, then review public addresses, assets, fees or permission details. A familiar interface is not a reason to skip the request details of a third-party DApp or smart contract.
How to Identify Suspicious Requests
After broadcast, a transaction generally cannot be cancelled by the wallet alone, so the confirmation step should never be treated as disposable. imtoken treats user review as the final decision point for Transaction Checks. This site never asks for seed phrases, private keys or verification codes, and it does not promise that confirmed on-chain transactions can be reversed by the wallet. DApps, smart contracts, networks and third-party services each introduce their own risk boundaries.
If the result differs from what you expected, preserve non-secret details such as the transaction hash, network and public address, then begin troubleshooting from on-chain state. Never send recovery information to someone claiming to provide support, and do not sign an unfamiliar request simply because it is presented as a fix. For Transaction Checks, break the task into small points that can be verified rather than continuing while the network, address, permission or transaction state is still unclear.
Post-action check
Confirm that the page and network match the task, then review public addresses, assets, fees or permission details. A familiar interface is not a reason to skip the request details of a third-party DApp or smart contract.
What to Do When Something Looks Wrong
The final review before an on-chain submission matters: address, network, asset, amount, fee and action type should all match the intended transaction. If the result differs from what you expected, preserve non-secret details such as the transaction hash, network and public address, then begin troubleshooting from on-chain state. Never send recovery information to someone claiming to provide support, and do not sign an unfamiliar request simply because it is presented as a fix.
The practical way to understand Transaction Checks is to place it inside a real user journey rather than memorize isolated terms. 在链上提交前逐项核对地址、网络、金额和费用 should be checked before an action, during confirmation and again after completion. Verify the entry point and network first, read addresses, permissions, fees and request details at confirmation, then use on-chain records to validate the outcome. For Transaction Checks, break the task into small points that can be verified rather than continuing while the network, address, permission or transaction state is still unclear.
Pre-action check
Confirm that the page and network match the task, then review public addresses, assets, fees or permission details. A familiar interface is not a reason to skip the request details of a third-party DApp or smart contract.
Everyday Security Checklist
Do not verify only the first few address characters. Where possible, compare the full address or multiple segments and confirm the source you copied it from. The practical way to understand Transaction Checks is to place it inside a real user journey rather than memorize isolated terms. 在链上提交前逐项核对地址、网络、金额和费用 should be checked before an action, during confirmation and again after completion. Verify the entry point and network first, read addresses, permissions, fees and request details at confirmation, then use on-chain records to validate the outcome.
Many mistakes around Transaction Checks begin with information that looks familiar: similar network names, address formats, token symbols or interface layouts. Prefer details that can be independently checked, such as the full domain, network name, contract address, transaction hash and a matching block-explorer record, instead of relying on icons, nicknames or screenshots. For Transaction Checks, break the task into small points that can be verified rather than continuing while the network, address, permission or transaction state is still unclear.
Confirmation check
Confirm that the page and network match the task, then review public addresses, assets, fees or permission details. A familiar interface is not a reason to skip the request details of a third-party DApp or smart contract.
You are responsible for keeping seed phrases and private keys private. imtoken personnel will never ask for them. Verify address, network and amount before sending; confirmed on-chain transactions generally cannot be reversed by the wallet.