Recovery secrets must remain private
Seed phrases, private keys and recovery phrases represent wallet control and should never be sent to anyone or entered into pages claiming to verify, sync or unlock a wallet. This determines how interface state should be interpreted and where verification should begin. Do not rely on a button label alone; compare what the interface shows with the active account, network and available on-chain evidence.
Phishing often relies on urgency
Fake support, airdrops, lookalike domains and scare messages often use urgency to make people skip verification; a trustworthy workflow allows time to inspect the request. Before acting, define the intended input, output and prerequisites, then inspect the relevant address, network, permission or fee fields. If a field is unclear, understanding it first is safer than repeating clicks or copying someone else’s steps.
A practical way to verify
Pause before confirmation and explain the key fields in your own words. If the account, network, contract, amount, fee or permission does not match the intended task, return to the previous step rather than forcing the flow to continue.
The device environment is part of the security boundary
Operating systems, browsers, extensions, clipboards and remote-access tools can affect transaction information; important actions belong on a controlled, updated device. Separate interface status from on-chain facts and retain non-secret references such as transaction hashes or contract addresses for later verification. Networks, protocols and DApps can implement similar ideas differently, so one prior experience should not be treated as a universal rule.
Evaluate each wallet request separately
Connection, message signing, token approval and transfers are different permissions; a safe first step does not automatically make the next one safe, especially where contracts, amounts or allowances are involved. Common failures come from the wrong target, wrong network, excessive permission or misunderstood request details. Stop when a domain, contract, amount or authorization falls outside the intended action rather than allowing urgency to weaken verification.
Keep seed phrases and private keys under your own control. imtoken support will not ask for them or for verification codes. Review address, network and amount before sending; on-chain transactions are usually not reversible by a wallet provider.
Stop expanding risk after an anomaly
If you notice an unfamiliar transaction, approval or suspicious page, stop further actions, disconnect it, inspect on-chain records and permissions, and reassess from a trusted device. Over time, turn the important checks into a repeatable routine and periodically review transaction history, approvals and device conditions. This cannot remove every risk, but it makes important decisions easier to explain and verify.
Keep the principle reusable
Interfaces and network conditions change, so a durable workflow focuses on understanding the object, permission and on-chain consequence rather than memorizing a single screen.
Applying Security in a real workflow
Seed phrases, private keys and recovery phrases represent wallet control and should never be sent to anyone or entered into pages claiming to verify, sync or unlock a wallet. In practice, begin by naming the active account, intended target and operating context rather than searching for the fastest button. Then use the idea behind “Phishing often relies on urgency” to verify prerequisites and make sure the visible fields match the task you actually intend to complete. This approach remains useful even when an interface changes.
Operating systems, browsers, extensions, clipboards and remote-access tools can affect transaction information; important actions belong on a controlled, updated device. During the workflow, treat “Evaluate each wallet request separately” as a separate verification checkpoint. A web page, a wallet prompt and the final on-chain result are different layers of evidence. If the network changes unexpectedly, the contract is unfamiliar, the permission is broader than expected or an amount cannot be explained, stop and verify before continuing.
A complete check can follow this sequence
- Before starting, identify the object, network or control boundary behind “Recovery secrets must remain private”.
- During the action, verify the conditions described by “Phishing often relies on urgency” and “The device environment is part of the security boundary”.
- Before confirmation, review the target, permission or risk represented by “Evaluate each wallet request separately”.
- After completion, use “Stop expanding risk after an anomaly” to review public chain records, approvals or device state.
If you notice an unfamiliar transaction, approval or suspicious page, stop further actions, disconnect it, inspect on-chain records and permissions, and reassess from a trusted device. If a field still cannot be explained, learn what it means before proceeding or use a lower-value, lower-permission and independently verifiable test. Never give seed phrases, private keys or verification codes to another person. Third-party DApps, contracts, bridges and services can carry their own risks, so a repeatable verification process is more durable than speed.