Balances come from on-chain state
A wallet interface reads blockchain data. Network selection, node synchronization and token detection can affect display without changing state that has already been recorded on-chain.
A repeatable order of checks is more reliable than memory. Review source, network, account, target and expected outcome each time so the same safety logic carries across wallets and DApps.
Token contracts identify assets
Tokens with the same name are not necessarily the same asset. Verify the network and contract address rather than relying only on name, icon or displayed decimals.
When a task involves a third-party contract, bridge, validator or web service, separate that external risk from the wallet itself. A wallet can display and sign a request, but it cannot guarantee the safety of outside code or services.
History needs network context
A transaction hash is meaningful in its own network context. Use the correct explorer and inspect status, confirmations and relevant contract events.
Put this concept back into the current network, account and request type before acting. Identify what the interface is asking for, then decide whether a signature, gas payment or ongoing permission is actually required.
A sequence for display issues
Check the selected network first, then the address and on-chain balance, followed by token contract details or local display state. Never submit a seed phrase to a website or support contact to “restore” a display.
Do not rely on a button label or a familiar-looking page as the reason to continue. Compare the request with the on-chain target, network state and expected result, and stop when those pieces do not line up.
Practical checklist
- Confirm that “Balances come from on-chain state” matches the task you intend to perform
- Confirm that “Token contracts identify assets” matches the task you intend to perform
- Confirm that “History needs network context” matches the task you intend to perform
- Confirm that “A sequence for display issues” matches the task you intend to perform
Risk reminder
Seed phrases and private keys remain under the user’s control. Legitimate support should not ask for a seed phrase, private key or verification code. Review address, network and amount before transferring; blockchain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps and smart contracts carry risk, so review spender and permission scope and consider revoking unused approvals.