On this page
Before troubleshootingAssets not displayedTransaction not receivedDApp interaction issuesSecurity concernsBefore troubleshooting
When reviewing Before troubleshooting, separate 不分享助记词, 不分享私钥, and 不提供验证码. They may appear in the same workflow, but they represent different layers of the action. On this Support & Self-service Troubleshooting page, the goal is to build a verifiable mental model rather than depend on a single interface cue. Before approving anything, identify the network, the object being changed, and whether the request matches the task you intended to perform.
A useful routine is to review items in a fixed order: confirm 不分享私钥, verify 不提供验证码, inspect 保存交易哈希, and keep 确认域名 for later reference. If a page unexpectedly asks for 不分享助记词, stop and verify the source instead of continuing simply because the workflow looks familiar.
From a security perspective, Before troubleshooting should be considered together with 不提供验证码, 保存交易哈希, and 确认域名. A legitimate review flow does not require you to reveal a seed phrase, private key, or verification code. Requests involving 不分享助记词 or 不分享私钥 can change permissions or asset state, so review them individually and reject anything you do not understand.
Assets not displayed
In practice, network often tells you whether you are in the right context, token contract affects the resulting state, and balance helps with independent verification afterward. Do not rely only on a success message in the interface. Where on-chain state is involved, compare it with indexing and refresh so you can distinguish presentation from the actual network result.
Assets not displayed also has failure modes. Congestion, incorrect parameters, insufficient balances, contract conditions, or third-party service changes can produce unexpected results. Start with the objective state of token contract, balance, and indexing before retrying. Repeated submissions without understanding the cause can add fees or duplicate actions.
When reviewing Assets not displayed, separate balance, indexing, and refresh. They may appear in the same workflow, but they represent different layers of the action. On this Support & Self-service Troubleshooting page, the goal is to build a verifiable mental model rather than depend on a single interface cue. Before approving anything, identify the network, the object being changed, and whether the request matches the task you intended to perform.
- network
- token contract
- balance
- indexing
- refresh
Transaction not received
A useful routine is to review items in a fixed order: confirm transaction hash, verify state, inspect confirmation, and keep target network for later reference. If a page unexpectedly asks for recipient address, stop and verify the source instead of continuing simply because the workflow looks familiar.
From a security perspective, Transaction not received should be considered together with state, confirmation, and target network. A legitimate review flow does not require you to reveal a seed phrase, private key, or verification code. Requests involving recipient address or transaction hash can change permissions or asset state, so review them individually and reject anything you do not understand.
In practice, confirmation often tells you whether you are in the right context, target network affects the resulting state, and recipient address helps with independent verification afterward. Do not rely only on a success message in the interface. Where on-chain state is involved, compare it with transaction hash and state so you can distinguish presentation from the actual network result.
| Item | Why it matters | Suggested action |
|---|---|---|
| transaction hash | Helps verify that the network state or permission scope matches your intent. | Review before and after submission and keep a traceable reference. |
| state | Helps verify that the network state or permission scope matches your intent. | Review before and after submission and keep a traceable reference. |
| confirmation | Helps verify that the network state or permission scope matches your intent. | Review before and after submission and keep a traceable reference. |
DApp interaction issues
DApp interaction issues also has failure modes. Congestion, incorrect parameters, insufficient balances, contract conditions, or third-party service changes can produce unexpected results. Start with the objective state of network, 连接, and signing before retrying. Repeated submissions without understanding the cause can add fees or duplicate actions.
When reviewing DApp interaction issues, separate 连接, signing, and approval. They may appear in the same workflow, but they represent different layers of the action. On this Support & Self-service Troubleshooting page, the goal is to build a verifiable mental model rather than depend on a single interface cue. Before approving anything, identify the network, the object being changed, and whether the request matches the task you intended to perform.
A useful routine is to review items in a fixed order: confirm signing, verify approval, inspect browser session, and keep network for later reference. If a page unexpectedly asks for 连接, stop and verify the source instead of continuing simply because the workflow looks familiar.
Security concerns
From a security perspective, Security concerns should be considered together with suspicious signature, approval, and 设备. A legitimate review flow does not require you to reveal a seed phrase, private key, or verification code. Requests involving 钓鱼 or new wallet can change permissions or asset state, so review them individually and reject anything you do not understand.
In practice, approval often tells you whether you are in the right context, 设备 affects the resulting state, and 钓鱼 helps with independent verification afterward. Do not rely only on a success message in the interface. Where on-chain state is involved, compare it with new wallet and suspicious signature so you can distinguish presentation from the actual network result.
Security concerns also has failure modes. Congestion, incorrect parameters, insufficient balances, contract conditions, or third-party service changes can produce unexpected results. Start with the objective state of 设备, 钓鱼, and new wallet before retrying. Repeated submissions without understanding the cause can add fees or duplicate actions.