Check every character.
Compare the complete recipient address with a trusted source. Matching only the beginning and end is not enough.
Take a moment to understand the request, protect what is private and verify what matters.
Build your review habitsSix practical habits for reviewing requests and keeping private information private.
Match the request to your intention.
Compare the complete recipient address with a trusted source. Matching only the beginning and end is not enough.
Check the sending network and what the recipient accepts. A token name alone is not enough.
Review the quantity, network fee and any spending allowance as separate details.
Keep control of what you share and install.
Question unexpected requests. Stop if the action differs from what you intended.
Never share seed phrases, private keys or wallet files through websites or with someone offering help.
Review the software source and download guidance. Treat unsolicited download links with caution.
Your recovery information can give access to your wallet. Keep it out of chats, forms and screenshots.
The words used to recover a wallet.
Secret keys used to authorise wallet actions.
Files that can contain sensitive wallet data.
Asked to share them? Stop. Never send recovery information to someone offering help or paste it into this website.
Know what documentation establishes — and what it does not.
Understand the assetsUSDe, sUSDe and ENA have different roles and risks. Consider market prices, smart contracts, liquidity, hedging and counterparties. Discretionary rewards are not guaranteed, and digital assets can lose value.
Protocol backing can rely on offchain custody and settlement arrangements. These introduce operational and counterparty dependencies. They are separate from an individual user’s application and do not prove wallet insurance or custody design.
Protocol audits cover specified contracts and versions. They do not establish the security of this desktop application or promise an absence of vulnerabilities.
This interface overview does not establish the desktop application’s key storage, recovery, authentication or hardware support. Do not infer those capabilities from protocol documentation.
If something is unfamiliar, pause and review the details.