Never share a recovery phrase.
HOODBTC does not require you to send a seed phrase or private key to another person. Anyone asking for one should be treated as untrusted.
SECURITY CENTER
VERIFY / PROTECT / REPORT
Security starts with verification.
Use this page to confirm official HOODBTC destinations, understand wallet-safety boundaries, review website protections and report security issues responsibly.
OFFICIAL DOMAINSNO SEED PHRASESRESPONSIBLE DISCLOSURE
OFFICIAL DESTINATIONS
Check the full domain before connecting a wallet.
HOODBTC products and resources are published under the destinations below. Lookalike domains, copied logos and social profiles are not proof of authenticity.
ECOSYSTEM & DOCUMENTATIONhoodbtc.com
Official main siteDEX TRADINGtrade.hoodbtc.com
Official trading interfaceTOKEN CREATIONtokenfactory.hoodbtc.com
Official Token FactoryImportant: If a link does not match an official destination, do not connect a wallet, sign a message, approve a token permission or send funds.
WALLET SAFETY
Your wallet approval is a security boundary.
Onchain actions can be irreversible. Read every wallet prompt and independently verify the network, destination, token amounts and permissions before approval.
Read before you sign.
Confirm the exact action shown by your wallet. A familiar brand name in a message or browser tab does not replace checking the transaction itself.
Do not trust unsolicited support messages.
Impersonators can copy names, avatars and logos. Return to hoodbtc.com/community/ and use the published official links instead.
Assume onchain activity is visible.
Wallet addresses and transactions on public networks can be observable by third parties. Do not treat a public wallet address as private information.
WEBSITE PROTECTIONS
Defense in depth for the public HOODBTC website.
The main website deploys browser and transport protections intended to reduce common web risks. These controls improve resilience but cannot guarantee that any internet-connected system will never be compromised.
HTTPS enforcement
Strict Transport Security is configured to keep supported browsers on encrypted HTTPS connections.
Content Security Policy
A restrictive Content Security Policy limits where scripts, styles, fonts, images and connections may load from.
Frame blocking
Frame restrictions are configured to reduce clickjacking exposure on the main website.
Reduced unnecessary access
Camera, microphone, geolocation and payment permissions are disabled by default on the main website through policy headers.
RESPONSIBLE DISCLOSURE
Report security issues without putting users at risk.
If you believe you found a vulnerability affecting hoodbtc.com or an official HOODBTC destination, use the official contact route below and provide enough technical detail for the issue to be reproduced and assessed.
What to include
- The affected URL, product or component.
- Clear reproduction steps and expected versus observed behavior.
- The likely security impact and any safe proof of concept.
- Your preferred contact method for follow-up.
What not to do
- Do not access, copy or modify data that is not yours.
- Do not move user funds, attempt phishing or ask users for credentials.
- Do not disrupt availability, perform destructive testing or publish exploit details before there is time to investigate.
- Do not assume a reward is available. No bounty or payment is promised unless separate bounty terms are published.
SECURITY BOUNDARIES
Know what this page does — and does not — promise.
HOODBTC can publish verified destinations, safer-use guidance and security controls, but users remain responsible for securing their own devices, wallets, recovery material and approvals. Third-party wallets, blockchain networks, protocols and infrastructure may have separate security models, terms and risks.
Security information may change as products and infrastructure evolve. Material updates will be reflected on this page and in the published security.txt file.
Last updated: September 10, 2026Security policy version: 1.0