Understand the relationship between issue triage and transaction checks
Many wallet mistakes are not caused by one button; they happen because the surrounding context is misunderstood. When reviewing issue triage, also check the active network, address, asset type and the request in front of you. transaction checks often depends on the step before or after it, so treating one field in isolation can hide important risk. imtoken focuses on explaining these relationships rather than replacing judgment with slogans.
For Support, a useful way to judge the situation is to compare the request with your intended outcome. If the screen asks for something broader than the task requires, stop and review the details. Issue triage should be understood together with transaction checks; the combination often explains why a fee changes, why a transaction is still pending, or why a permission deserves another look.
Practical checks
- Confirm the active network before working with issue triage.
- Review the destination or contract related to transaction checks.
- Do not share a seed phrase, private key or verification code.
- Keep the transaction hash when an on-chain action is submitted.
Check transaction checks before you act
Before an action involving transaction checks, answer three questions: which network is active, who or what is the destination, and what on-chain result will this request create? If network checks is also involved, review the fee asset, permission scope or confirmation state. Once a transaction is broadcast, the network rules usually determine what can happen next, which makes pre-confirmation checks especially valuable.
For Support, a useful way to judge the situation is to compare the request with your intended outcome. If the screen asks for something broader than the task requires, stop and review the details. Transaction checks should be understood together with network checks; the combination often explains why a fee changes, why a transaction is still pending, or why a permission deserves another look.
Practical checks
- Confirm the active network before working with transaction checks.
- Review the destination or contract related to network checks.
- Do not share a seed phrase, private key or verification code.
- Keep the transaction hash when an on-chain action is submitted.
Place network checks in the full on-chain workflow
Placing network checks inside the full workflow makes its purpose easier to understand. A typical path includes selecting a network, verifying an address or contract, reviewing request details, checking fees, broadcasting and waiting for confirmation. DApp issues may affect one or several of those stages. Knowing exactly where it matters helps you decide whether a prompt is expected and whether the result matches your intent.
For Support, a useful way to judge the situation is to compare the request with your intended outcome. If the screen asks for something broader than the task requires, stop and review the details. Network checks should be understood together with DApp issues; the combination often explains why a fee changes, why a transaction is still pending, or why a permission deserves another look.
Practical checks
- Confirm the active network before working with network checks.
- Review the destination or contract related to DApp issues.
- Do not share a seed phrase, private key or verification code.
- Keep the transaction hash when an on-chain action is submitted.
Common mistakes and risk signals
Warning signs include pressure to act immediately, a domain that does not match what you expected, an unexplained network switch, an unfamiliar approval target, an allowance much larger than necessary, a pasted address that changes, or anyone asking for a seed phrase or private key. For requests involving DApp issues or security incidents, return to your original purpose and verify the on-chain details rather than relying on verbal assurances.
For Support, a useful way to judge the situation is to compare the request with your intended outcome. If the screen asks for something broader than the task requires, stop and review the details. Dapp issues should be understood together with security incidents; the combination often explains why a fee changes, why a transaction is still pending, or why a permission deserves another look.
Practical checks
- Confirm the active network before working with DApp issues.
- Review the destination or contract related to security incidents.
- Do not share a seed phrase, private key or verification code.
- Keep the transaction hash when an on-chain action is submitted.
Build a repeatable review habit
A repeatable sequence reduces missed details: verify the entry point and domain, confirm the account and network, check the destination, amount or contract parameters, then review fees, signatures and approvals. Afterward, inspect the transaction hash and status, and remove connections or approvals you no longer use. The same sequence works for security incidents and helps place issue triage in a practical routine.
For Support, a useful way to judge the situation is to compare the request with your intended outcome. If the screen asks for something broader than the task requires, stop and review the details. Security incidents should be understood together with issue triage; the combination often explains why a fee changes, why a transaction is still pending, or why a permission deserves another look.
Practical checks
- Confirm the active network before working with security incidents.
- Review the destination or contract related to issue triage.
- Do not share a seed phrase, private key or verification code.
- Keep the transaction hash when an on-chain action is submitted.