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
Security makes more sense when seed phrase, private keys, approvals, phishing, transaction checks are considered as parts of one on-chain workflow. When a request is unclear, stop before signing or transferring and verify the network and on-chain record from a trusted path.
During real use, confirm the active network and account first, then verify the object, scope and expected outcome related to seed phrase. 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 seed phrase. Any action that changes assets, permissions or account state deserves a full review before confirmation.
For private keys, 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 goal is not to memorize more terminology, but to make each action explainable, verifiable and reviewable.
How to identify problems
For private keys, 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 goal is not to memorize more terminology, but to make each action explainable, verifiable and reviewable.
When approvals 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 approvals 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 phishing, 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 phishing, 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 transaction checks. 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.