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
Seed Phrase & Private Keys makes more sense when seed phrase custody, private key custody, offline backup, screenshot risk, cloud backup risk are considered as parts of one on-chain workflow. The same address format can appear across different network contexts, so appearance alone is not enough to confirm the correct destination.
During real use, confirm the active network and account first, then verify the object, scope and expected outcome related to seed phrase custody. 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 custody. Any action that changes assets, permissions or account state deserves a full review before confirmation.
For private key custody, prefer information that can be independently checked: the wallet transaction summary, the relevant network explorer, an explicit contract address or an official product page. A wallet interface is only the entry point; the important checks concern the network, address, contract and on-chain state.
How to identify problems
For private key custody, prefer information that can be independently checked: the wallet transaction summary, the relevant network explorer, an explicit contract address or an official product page. A wallet interface is only the entry point; the important checks concern the network, address, contract and on-chain state.
When offline backup 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 offline backup 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 screenshot risk, 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 screenshot risk, 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 cloud backup risk. 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.