Protect the device
Use a strong device lock, keep the operating system current, review installed software, and avoid wallet actions on a device you do not control.
Wallet security
Security is a practice, not a promise.
A self-custody wallet gives you direct control over access and approvals. That control is strongest when device protection, recovery planning, and transaction review become part of the same routine.
Before confirmation
Review the complete action
Asset and amount are expected
Network matches the destination
Address has been independently checked
Permissions and result are understood
A clear review reduces avoidable mistakes, but no interface can guarantee that a destination, token, or external protocol is safe.
Shared responsibility
The wallet protects a system. You protect access.
Product safeguards can make important details visible, limit accidental actions, and help recovery work as designed. They cannot verify every person, website, token, address, or protocol you encounter outside the wallet.
Your device lock, recovery information, transaction approvals, and choice of destination remain part of the security boundary. Treat unexpected urgency, secret requests, and unfamiliar approvals as reasons to stop.
Support should never need your secrets
Never send a seed phrase, private key, password, one-time code, or full recovery credential through email, chat, a form, or screen sharing.
Core safeguards
Protect the moments that carry the most risk.
Wallet security is not one setting. It is a chain of decisions across the device, recovery method, network, destination, and final approval.
Plan recovery before you need it
Understand the recovery method during setup. Store the required information privately and make sure no single message, screenshot, or cloud note exposes it.
Read before approving
Confirm the asset, amount, destination, fee, and requested permissions. Reject any action whose result or urgency you cannot explain.
Match the network
The same asset name may exist on different networks. Confirm compatibility on both sides before sending and use a small test when appropriate.
A safer routine
Four checks worth repeating.
Consistent habits are more useful than a warning seen once. Use this short sequence whenever a new device, address, network, or application is involved.
- 01
Verify the source
Download the wallet from the official domain and check the filename, publisher information, and available checksum before installation.
- 02
Start small
When using a new destination or network, consider a small test transaction before moving a larger balance.
- 03
Review independently
Compare critical addresses through a second trusted channel. Do not rely only on copied text or a link supplied by an unknown person.
- 04
Keep the setup current
Install trusted system and wallet updates, remove unused access, and revisit recovery arrangements when a device or circumstance changes.
If something looks wrong
Stop first. Investigate second.
Speed helps attackers when it creates panic. Preserve information, avoid additional approvals, and use a trusted device and official channel for the next step.
Pause new actions
Do not approve more transactions, signatures, recovery prompts, or software installations until you understand what happened.
Separate the risk
Close suspicious pages and disconnect unfamiliar sessions or applications when the available wallet controls allow it.
Record non-secret details
Save timestamps, transaction hashes, public addresses, screenshots, and message headers without recording or sharing private credentials.
Use the official channel
Open the FAQ or contact support from this domain. Be suspicious of direct messages claiming they can reverse a blockchain transaction.
Need help checking the next step?
Use the official FAQ for recovery, account access, suspicious messages, and common wallet questions. Keep all private credentials to yourself.
Open security FAQ