01
Make an offline backup
Record words in the exact order and check each one. Avoid screenshots, chat messages, and cloud syncing; use a secure offline storage plan.
Detailed stepsSECURITY EXPLAINER
Avoid Phishing
Identify impersonation websites, fraudulent signature requests, and fake support messages. Verify URLs, examine what you are authorizing, and never share a r.
Educational illustrationKEY CONTEXT
Understand the context before acting
Avoid Phishing
Identify impersonation websites, fraudulent signature requests, and fake support messages. Verify URLs, examine what you are authorizing, and never share a r.
This guide helps you build a careful review sequence. Any wallet screen, balance, or security state shown here is illustrative; follow verified instructions on your trusted device.
Safety boundary
Never upload keys, recovery phrases, or passwords to this website or a third party.
Concept previewACTION PLAN
Use four practical checkpoints
02
Check the asset network
Verify the active chain, token identity, and any applicable contract address. Assets with the same ticker on different networks are not necessarily interchangeable.
Detailed steps03
Review before approval
Check the destination network, recipient address, amount, and network fee. For a new destination, consider a small test transaction before sending more.
Detailed steps04
Verify the source
Do not rely on sponsored search links, forwarded messages, or unexpected archives. Check the full domain, certificate, and installer provenance; stop if the destination changes.
Detailed stepsRISKS & NEXT STEPS
When uncertain, pause and verify
01
Recognize unusual prompts
Independently verify requests for recovery credentials or urgent signatures.
02
Double-check the source
Avoid installers from unknown links, imitation domains, and private messages.
03
Maintain a recovery plan
Confirm offline backups are complete, legible, and securely stored.