Core concepts
Seed phrases and private keys remain under the user’s control. Official staff will not ask for them, and they should never be sent through chat, email or web forms. In the context of seed phrases, it also helps to connect private keys with address derivation rather than treating them as isolated features. Before transferring, signing or approving, review the domain, address, network, amount, target contract and permission scope. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.
A useful review habit is to compare seed phrases with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.
Practical workflow
Before transferring, signing or approving, review the domain, address, network, amount, target contract and permission scope. In the context of private keys, it also helps to connect address derivation with offline backup rather than treating them as isolated features. Public computers, remote-control sessions, unknown Wi-Fi and untrusted apps increase exposure around sensitive actions. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.
A useful review habit is to compare private keys with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.
Checks before confirmation
Public computers, remote-control sessions, unknown Wi-Fi and untrusted apps increase exposure around sensitive actions. In the context of address derivation, it also helps to connect offline backup with seed phrases rather than treating them as isolated features. After use, review DApp sessions and approvals and consider removing permissions that are no longer needed. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.
A useful review habit is to compare address derivation with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.
Review checklist
- Seed phrases and private keys remain under the user’s control. Official staff will not ask for them, and they should never be sent through chat, email or web forms.
- Before transferring, signing or approving, review the domain, address, network, amount, target contract and permission scope.
- Public computers, remote-control sessions, unknown Wi-Fi and untrusted apps increase exposure around sensitive actions.
- After use, review DApp sessions and approvals and consider removing permissions that are no longer needed.
Risks and follow-up
After use, review DApp sessions and approvals and consider removing permissions that are no longer needed. In the context of offline backup, it also helps to connect seed phrases with private keys rather than treating them as isolated features. Seed phrases and private keys remain under the user’s control. Official staff will not ask for them, and they should never be sent through chat, email or web forms. Keep the actual request details visible, and stop if the network, contract or permission cannot be explained clearly.
A useful review habit is to compare offline backup with the active network state and the exact request shown by the wallet. Third-party DApps and smart contracts may introduce their own risk, and confirmed on-chain transactions usually cannot be reversed by the wallet alone.
Key risks
- Never share a seed phrase, private key or verification code.
- Third-party DApps, networks and contracts can fail or behave maliciously.
- Staking and digital assets do not offer guaranteed returns or protection from price volatility.