Security Center
Transaction Checks
A practical imtoken guide to transaction checks, including core concepts, verification steps and risk-aware usage.
imtoken staff will never ask for your seed phrase, private key or verification code.
Core concepts
To understand Transaction Checks, treat address checks and network checks 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 address checks, first define its role in the current task, then check whether network checks and amount checks are consistent. When transaction hashes is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For irreversibility, 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: address checks
- Cross-check: network checks and amount checks
- Review carefully: transaction hashes
- Verify afterward: irreversibility
Checks before you act
network checks rarely appears in isolation. It often intersects with amount checks and transaction hashes. 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 network checks, first define its role in the current task, then check whether amount checks and transaction hashes are consistent. When irreversibility is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For address checks, 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: network checks
- Cross-check: amount checks and transaction hashes
- Review carefully: irreversibility
- Verify afterward: address checks
How to evaluate a live request
When using imtoken for Transaction Checks, 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 amount checks, first define its role in the current task, then check whether transaction hashes and irreversibility are consistent. When address checks is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For network checks, 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: amount checks
- Cross-check: transaction hashes and irreversibility
- Review carefully: address checks
- Verify afterward: network checks
Risks and boundaries
From a risk perspective, address checks and network checks 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 transaction hashes, first define its role in the current task, then check whether irreversibility and address checks are consistent. When network checks is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For amount checks, 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: transaction hashes
- Cross-check: irreversibility and address checks
- Review carefully: network checks
- Verify afterward: amount checks
How to verify the outcome
After a Transaction Checks task is completed, review amount checks and transaction hashes 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 irreversibility, first define its role in the current task, then check whether address checks and network checks are consistent. When amount checks is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For transaction hashes, 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: irreversibility
- Cross-check: address checks and network checks
- Review carefully: amount checks
- Verify afterward: transaction hashes
Security 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.