Crypto support has a strange failure mode: the user who most needs help is often the easiest person to trick.
Someone is missing a deposit, stuck on a bridge, confused by a token approval, or worried about an account lock. They are stressed, searching fast, and ready to paste anything that looks useful into a support chat. That is exactly when fake admins, fake support bots, and wallet-draining sites become dangerous.
The safest support request is not the one with the most information. It is the one with the right information.
This is a practical checklist for users, moderators, and small Web3 teams.
What You Should Never Share
Do not send any of these to support, even if the person asking has a logo, admin badge, or urgent tone:
Seed phrase or recovery phrase.
Private key.
Password.
2FA code.
API key.
Remote desktop access.
Full ID documents in public chat.
Screenshots that reveal balances, email addresses, internal IDs, recovery phrases, or full account details.
A si
Discussion
Take the lead—comment now
Lead the way—your insights can inspire others.