Build a repeatable security routine
Pre-transaction Check Guide is best approached as a sequence of checks rather than a promise that any wallet can remove all risk. Identify who is asking you to act, what permission is being requested, which network or contract is involved, and what will change if you approve; in Pre-transaction Check Guide, read this specifically alongside “Build a repeatable security routine” and recipient addresses. imtoken staff will not ask for a seed phrase, private key, or verification code; in Pre-transaction Check Guide, read this specifically alongside “Build a repeatable security routine” and recipient addresses. Those credentials remain under the user’s control and should never be uploaded, pasted into chat, or shown through remote-access software; in Pre-transaction Check Guide, read this specifically alongside “Build a repeatable security routine” and recipient addresses. This part of Pre-transaction Check Guide should be read together with the surrounding workflow: recipient addresses affects how you interpret networks, while amounts helps confirm the state after the action.
Recognize risks around recipient addresses
Problems involving recipient addresses often begin with a misleading page, an urgent message, or a request that does not match the task you intended to perform. Re-check the domain, the connected account, and the reason for the request; in Pre-transaction Check Guide, read this specifically alongside “Recognize risks around recipient addresses” and networks. Promises of rewards, account “verification,” urgent upgrades, or support assistance should never be used as a reason to skip basic checks; in Pre-transaction Check Guide, read this specifically alongside “Recognize risks around recipient addresses” and networks. For Pre-transaction Check Guide, connect networks with amounts and gas; the important part is the relationship between those concepts and the on-chain evidence you can verify afterward.
Review networks and amounts before acting
When reviewing networks and amounts, separate the object, the scope, and the consequence. The object may be an address, contract, device, or account; the scope may be a single transaction or a continuing approval; the consequence is what can happen after confirmation; in Pre-transaction Check Guide, read this specifically alongside “Review networks and amounts before acting” and amounts. If the interface does not give enough context, stop and verify the address, transaction, or contract through the correct blockchain explorer; in Pre-transaction Check Guide, read this specifically alongside “Review networks and amounts before acting” and amounts. When working through “Review networks and amounts before acting,” check the source, network, request details and resulting state in that order, with extra attention to amounts and gas.
- A request asks for recovery credentials or a verification code.
- The domain, account or permission does not match your task.
- Urgency or rewards are used to pressure you into approving.
What to do when something looks wrong
If activity appears suspicious, avoid repeated clicks in the same session; in Pre-transaction Check Guide, read this specifically alongside “What to do when something looks wrong” and gas. Disconnect unnecessary DApps, review recent transactions and token approvals, and move to a trusted device if the current environment may be compromised; in Pre-transaction Check Guide, read this specifically alongside “What to do when something looks wrong” and gas. Blockchain transactions are generally not something a wallet provider can unilaterally reverse, so the useful goal is to limit further exposure rather than trust anyone promising a guaranteed recovery; in Pre-transaction Check Guide, read this specifically alongside “What to do when something looks wrong” and gas. Do not treat an interface success message as the final answer for Pre-transaction Check Guide. Use gas, token contracts and transaction irreversibility to confirm that the expected change occurred on the intended network.
A practical security checklist
A consistent routine can cover gas, token contracts, and most other Web3 interactions: use a trusted device, confirm the site, verify the network and destination, read each signature or approval, check the amount and fee, then review the transaction hash afterwards. Remove permissions that are no longer needed and keep recovery credentials offline; in Pre-transaction Check Guide, read this specifically alongside “A practical security checklist” and token contracts. If “A practical security checklist” is unclear, stop before approving and return to the basics of token contracts and transaction irreversibility, then verify the result with a transaction hash, contract address or block record where applicable.
The boundaries that should not change
The durable rules are simple: never share a seed phrase or private key, treat third-party DApps and smart contracts as independent risk sources, verify the address/network/amount before a transfer, and review approval scope before granting access; in Pre-transaction Check Guide, read this specifically alongside “The boundaries that should not change” and transaction irreversibility. imtoken provides wallet tools and educational material; it does not guarantee the security of third-party contracts, network availability, or asset prices; in Pre-transaction Check Guide, read this specifically alongside “The boundaries that should not change” and transaction irreversibility. A durable routine for Pre-transaction Check Guide is to make transaction irreversibility a first-pass check, use recipient addresses as a second check, and rely on verifiable information related to networks rather than interface assumptions.
Security and risk reminder
Seed phrases and private keys are controlled by the user. imtoken will never ask for them. Blockchain transactions are generally irreversible by a wallet provider, and third-party DApps, smart contracts, network conditions and digital-asset prices can introduce additional risk.