Understand the boundary of asset display
User Support and Troubleshooting is easier to use correctly when asset display is treated as a verifiable part of an on-chain workflow rather than a label in the interface. Use self-verifiable steps to troubleshoot asset display, transaction status, network selection, DApp connections and security questions, while making clear that official staff will never ask for a seed phrase or private key. The key distinction is between what a wallet displays for convenience and what the target blockchain records as state. A balance, network name, contract reference or transaction status should therefore be checked in the context of the network where the action actually occurs.
Looking at asset display together with transaction status prevents many avoidable mistakes. Similar address formats can appear on different networks, familiar token names can refer to different contracts, and a request can look routine while asking for broader permissions than expected. Before acting on network selection, confirm the source of the request, the selected network, the destination or contract and the exact action being authorized.
A robust routine keeps enough information to review the action later. Save a transaction hash when relevant, use an appropriate block explorer to check on-chain status, read signature or approval details before confirming and stop when a request cannot be explained. Familiar names, icons or balances are not substitutes for verification, and confirmed on-chain actions are generally not reversible by a wallet on its own.
- Confirm that you are evaluating asset display, not a similar-looking concept.
- Tie transaction status to the intended network, address or contract.
- Keep at least one verifiable reference before proceeding with network selection.
How transaction status changes the workflow
User Support and Troubleshooting is easier to use correctly when transaction status is treated as a verifiable part of an on-chain workflow rather than a label in the interface. Use self-verifiable steps to troubleshoot asset display, transaction status, network selection, DApp connections and security questions, while making clear that official staff will never ask for a seed phrase or private key. The key distinction is between what a wallet displays for convenience and what the target blockchain records as state. A balance, network name, contract reference or transaction status should therefore be checked in the context of the network where the action actually occurs.
Looking at transaction status together with network selection prevents many avoidable mistakes. Similar address formats can appear on different networks, familiar token names can refer to different contracts, and a request can look routine while asking for broader permissions than expected. Before acting on DApp connections, confirm the source of the request, the selected network, the destination or contract and the exact action being authorized.
A robust routine keeps enough information to review the action later. Save a transaction hash when relevant, use an appropriate block explorer to check on-chain status, read signature or approval details before confirming and stop when a request cannot be explained. Familiar names, icons or balances are not substitutes for verification, and confirmed on-chain actions are generally not reversible by a wallet on its own.
- Confirm that you are evaluating transaction status, not a similar-looking concept.
- Tie network selection to the intended network, address or contract.
- Keep at least one verifiable reference before proceeding with DApp connections.
What to verify around network selection
User Support and Troubleshooting is easier to use correctly when network selection is treated as a verifiable part of an on-chain workflow rather than a label in the interface. Use self-verifiable steps to troubleshoot asset display, transaction status, network selection, DApp connections and security questions, while making clear that official staff will never ask for a seed phrase or private key. The key distinction is between what a wallet displays for convenience and what the target blockchain records as state. A balance, network name, contract reference or transaction status should therefore be checked in the context of the network where the action actually occurs.
Looking at network selection together with DApp connections prevents many avoidable mistakes. Similar address formats can appear on different networks, familiar token names can refer to different contracts, and a request can look routine while asking for broader permissions than expected. Before acting on security support, confirm the source of the request, the selected network, the destination or contract and the exact action being authorized.
A robust routine keeps enough information to review the action later. Save a transaction hash when relevant, use an appropriate block explorer to check on-chain status, read signature or approval details before confirming and stop when a request cannot be explained. Familiar names, icons or balances are not substitutes for verification, and confirmed on-chain actions are generally not reversible by a wallet on its own.
- Confirm that you are evaluating network selection, not a similar-looking concept.
- Tie DApp connections to the intended network, address or contract.
- Keep at least one verifiable reference before proceeding with security support.
How DApp connections relates to security support
User Support and Troubleshooting is easier to use correctly when DApp connections is treated as a verifiable part of an on-chain workflow rather than a label in the interface. Use self-verifiable steps to troubleshoot asset display, transaction status, network selection, DApp connections and security questions, while making clear that official staff will never ask for a seed phrase or private key. The key distinction is between what a wallet displays for convenience and what the target blockchain records as state. A balance, network name, contract reference or transaction status should therefore be checked in the context of the network where the action actually occurs.
Looking at DApp connections together with security support prevents many avoidable mistakes. Similar address formats can appear on different networks, familiar token names can refer to different contracts, and a request can look routine while asking for broader permissions than expected. Before acting on asset display, confirm the source of the request, the selected network, the destination or contract and the exact action being authorized.
A robust routine keeps enough information to review the action later. Save a transaction hash when relevant, use an appropriate block explorer to check on-chain status, read signature or approval details before confirming and stop when a request cannot be explained. Familiar names, icons or balances are not substitutes for verification, and confirmed on-chain actions are generally not reversible by a wallet on its own.
- Confirm that you are evaluating DApp connections, not a similar-looking concept.
- Tie security support to the intended network, address or contract.
- Keep at least one verifiable reference before proceeding with asset display.
Common mistakes and safer habits
User Support and Troubleshooting is easier to use correctly when security support is treated as a verifiable part of an on-chain workflow rather than a label in the interface. Use self-verifiable steps to troubleshoot asset display, transaction status, network selection, DApp connections and security questions, while making clear that official staff will never ask for a seed phrase or private key. The key distinction is between what a wallet displays for convenience and what the target blockchain records as state. A balance, network name, contract reference or transaction status should therefore be checked in the context of the network where the action actually occurs.
Looking at security support together with asset display prevents many avoidable mistakes. Similar address formats can appear on different networks, familiar token names can refer to different contracts, and a request can look routine while asking for broader permissions than expected. Before acting on transaction status, confirm the source of the request, the selected network, the destination or contract and the exact action being authorized.
A robust routine keeps enough information to review the action later. Save a transaction hash when relevant, use an appropriate block explorer to check on-chain status, read signature or approval details before confirming and stop when a request cannot be explained. Familiar names, icons or balances are not substitutes for verification, and confirmed on-chain actions are generally not reversible by a wallet on its own.
- Confirm that you are evaluating security support, not a similar-looking concept.
- Tie asset display to the intended network, address or contract.
- Keep at least one verifiable reference before proceeding with transaction status.
Use and decision points
A consistent sequence around asset display and transaction status reduces cognitive load when switching networks, sending transactions or handling permissions. Approve only what the current step requires and use security support or an on-chain record to verify the result afterwards.
Keep your seed phrase and private keys under your own control. imtoken staff will never ask for a seed phrase, private key or verification code. Do not send these secrets to anyone; verify the address, network and amount before a transfer. On-chain transactions generally cannot be reversed unilaterally by a wallet, and third-party DApps and smart contracts can carry risk.