01
Understand the role of Self-service checks
In “Support,” Self-service checks is not an isolated idea. It works with Transaction issues and Knowledge resources to determine what the user sees and where an action actually takes place. Once those boundaries are clear, interface prompts become easier to evaluate.
Self-service troubleshooting should retain non-sensitive details such as a transaction hash, network name and public address, then distinguish display issues from confirmation or contract-interaction issues. Support should never request a seed phrase or private key. This section therefore focuses on reasoning through the relationship between Self-service checks, Transaction issues and the resulting on-chain state rather than memorizing interface locations.
A practical review habit
- Identify the active network and the object represented by Self-service checks, not only its display name.
- When Transaction issues is involved, confirm that both concepts share the intended network and permission context.
- Keep public verification details such as a transaction hash when troubleshooting, but never expose recovery secrets.
02
How Transaction issues works with Network issues
Start with the goal of the action, then identify the network, address, contract or permission context represented by Transaction issues. Similar names, icons or page layouts do not prove that two environments are equivalent; network and on-chain identifiers provide stronger context.
Self-service troubleshooting should retain non-sensitive details such as a transaction hash, network name and public address, then distinguish display issues from confirmation or contract-interaction issues. Support should never request a seed phrase or private key. This section therefore focuses on reasoning through the relationship between Transaction issues, Network issues and the resulting on-chain state rather than memorizing interface locations.
A practical review habit
- Identify the active network and the object represented by Transaction issues, not only its display name.
- When Network issues is involved, confirm that both concepts share the intended network and permission context.
- Keep public verification details such as a transaction hash when troubleshooting, but never expose recovery secrets.
03
Reviewing Network issues during an action
A repeatable review of Network issues can begin with the source and network, continue with the target and parameters, and end with the asset or permission change the action may create. Consistency is more useful than trying to confirm quickly.
Self-service troubleshooting should retain non-sensitive details such as a transaction hash, network name and public address, then distinguish display issues from confirmation or contract-interaction issues. Support should never request a seed phrase or private key. This section therefore focuses on reasoning through the relationship between Network issues, Security incidents and the resulting on-chain state rather than memorizing interface locations.
A practical review habit
- Identify the active network and the object represented by Network issues, not only its display name.
- When Security incidents is involved, confirm that both concepts share the intended network and permission context.
- Keep public verification details such as a transaction hash when troubleshooting, but never expose recovery secrets.
04
Common assumptions to avoid
A common mistake around Security incidents is treating display information as final on-chain truth, or assuming that a workflow that was safe once will be identical on another network, asset or DApp. Re-read the current request every time.
Self-service troubleshooting should retain non-sensitive details such as a transaction hash, network name and public address, then distinguish display issues from confirmation or contract-interaction issues. Support should never request a seed phrase or private key. This section therefore focuses on reasoning through the relationship between Security incidents, Knowledge resources and the resulting on-chain state rather than memorizing interface locations.
A practical review habit
- Identify the active network and the object represented by Security incidents, not only its display name.
- When Knowledge resources is involved, confirm that both concepts share the intended network and permission context.
- Keep public verification details such as a transaction hash when troubleshooting, but never expose recovery secrets.
05
Make Knowledge resources part of a routine
Making Knowledge resources part of a routine means adding checkpoints before, during and after an operation: verify the conditions, read the request, then confirm the result through the transaction hash, network state or approval record.
Self-service troubleshooting should retain non-sensitive details such as a transaction hash, network name and public address, then distinguish display issues from confirmation or contract-interaction issues. Support should never request a seed phrase or private key. This section therefore focuses on reasoning through the relationship between Knowledge resources, Self-service checks and the resulting on-chain state rather than memorizing interface locations.
A practical review habit
- Identify the active network and the object represented by Knowledge resources, not only its display name.
- When Self-service checks is involved, confirm that both concepts share the intended network and permission context.
- Keep public verification details such as a transaction hash when troubleshooting, but never expose recovery secrets.
Important security reminder
Seed phrases and private keys should remain under the user’s control, and official personnel will not request them or verification codes. Check the address, network and amount before a transfer; on-chain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps and smart contracts carry risk, so review the spender and permission scope and consider revoking unused approvals.
Before you continue
Use a repeatable review routine
- Verify the active network and target address or contract
- Read the amount, fee, signature or permission scope
- Never send a seed phrase, private key or verification code to anyone
- Verify the result through a transaction hash or approval record
- If a request is unclear, stop and verify the source before continuing