On this page
Core principlesCommon risk scenariosHow to identify problemsWhat to do nextSecurity checklist- Keep seed phrase backups offline
- Never send private keys or verification codes
- Verify domains, networks and addresses
- Review every signature and approval
- Review and revoke approvals you no longer need
Core principles
Device Security makes more sense when device lock, public Wi-Fi, shared computers, remote control, browser extensions are considered as parts of one on-chain workflow. Breaking an action into separate checks reduces mistakes caused by familiar-looking pages, similar links or urgent prompts.
During real use, confirm the active network and account first, then verify the object, scope and expected outcome related to device lock. Any action that changes assets, permissions or account state deserves a full review before confirmation.
Common risk scenarios
During real use, confirm the active network and account first, then verify the object, scope and expected outcome related to device lock. Any action that changes assets, permissions or account state deserves a full review before confirmation.
For public Wi-Fi, prefer information that can be independently checked: the wallet transaction summary, the relevant network explorer, an explicit contract address or an official product page. The same address format can appear across different network contexts, so appearance alone is not enough to confirm the correct destination.
How to identify problems
For public Wi-Fi, prefer information that can be independently checked: the wallet transaction summary, the relevant network explorer, an explicit contract address or an official product page. The same address format can appear across different network contexts, so appearance alone is not enough to confirm the correct destination.
When shared computers is involved, separate display data from on-chain facts. Names, icons and fiat estimates may come from external data sources, while balances, transaction state and approvals should be verified on the selected network.
What to do next
When shared computers is involved, separate display data from on-chain facts. Names, icons and fiat estimates may come from external data sources, while balances, transaction state and approvals should be verified on the selected network.
For remote control, retain the transaction hash or other useful reference when appropriate. On-chain transactions generally cannot be reversed unilaterally by a wallet, which makes pre-broadcast checks of the address, network, amount and permissions especially important.
Security checklist
For remote control, retain the transaction hash or other useful reference when appropriate. On-chain transactions generally cannot be reversed unilaterally by a wallet, which makes pre-broadcast checks of the address, network, amount and permissions especially important.
Finally, consider browser extensions. Third-party DApps, smart contracts and network services can introduce technical, operational and market risk. Unclear signatures, unnecessarily broad approvals, or any page asking for a seed phrase or private key are reasons to stop and re-check the request.