Guide
Verifying frontends
A short checklist for confirming you are on a real wallet or DEX frontend — bookmarks, TLS, hashes, and approvals — without trading advice.
7 min read
Why this matters
Most “DEX hacks” that hit ordinary users are UI phishing: a lookalike site that asks your wallet to approve a malicious spender. Verifying the frontend is cheaper than recovering keys.
Educational only. Not financial advice. Not an FSP/CASP. DYOR.
Checklist
- Type the URL yourself the first time, then bookmark it. Do not trust search ads or “support” DMs.
- Read the certificate / lock details — HTTPS is necessary, not sufficient. Confirm the domain spelling character by character.
- Cross-check announcements from the project’s known Nostr, GitHub, or documented status page — not a random Telegram forward.
- Prefer known hashes when a project publishes IPFS CIDs, release signatures, or reproducible frontend builds.
- Simulate before you sign if your wallet supports it. Read the approval target and amount.
- Revoke stale allowances with tools you independently verify — unlimited approvals are a long fuse.
- Separate play funds from savings — see the wallets pillar and sovereign starter kit.
What CryptoDecentral will not do
- Host a swap UI or route trades
- Tell you which asset to buy
- Recover a seed or “validate” a transaction for you
More context: DEX pillar.