Verify a decision
Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.
How verification works
- We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (
payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction. - We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
- You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is
AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.
Decision
publish · FEGex
- Sequence
- #1
- Score
- →
- Cluster
- mainnet-beta
- Slot
- 423086650
- Off-chain at
- 2026-05-30T04:48:02.052Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- G5inQDfBrJN9toSeLSa1KihaipWbdEWUchPJhauGgmvC
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (6992 chars)
{"actor":"system:backfill","investigation_id":"371a48cc-77ea-4fda-beae-4efc4fc12f75","kind":"publish","page_slug":"fegex","published_at":"2026-05-30T04:48:01.963Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"FEGex","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://ambcrypto.com/making-defi-mainstream-an-interview-with-fegex-marketing-manager-chris/","type":"other","url":""},{"credibility":3,"name":"https://feg.io/","type":"other","url":""},{"credibility":3,"name":"https://docs.feg.io/smartdefi-tm-platform/smartdefi-protocol","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://certik.com/resources/blog/w6AxRmf6l2ow4zL884gr8-feg-token-flashloan-exploit-analysis","type":"other","url":""},{"credibility":3,"name":"https://blocksecteam.medium.com/the-analysis-of-fegtoken-security-incident-devils-in-the-details-ea554f52bdcb","type":"other","url":""},{"credibility":3,"name":"https://medium.com/coinmonks/beosins-detailed-analysis-of-fegtoken-flashloan-attack-3-280-bnb-and-144-eth-lost-758d972ac65b","type":"other","url":""},{"credibility":3,"name":"https://x.com/FEGtoken/status/1527327080031330305","type":"other","url":""},{"credibility":3,"name":"https://certik.medium.com/20220516-feg-token-flashloan-exploit-analysis-4bfcd23bcfc9","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://protos.com/feg-token-holders-in-despair-after-third-hack-causes-99-dump/","type":"other","url":""},{"credibility":3,"name":"https://www.web3isgoinggreat.com/single/feed-every-gorilla-hack-2","type":"other","url":""},{"credibility":3,"name":"https://www.bsc.news/post/feg-token-rallies-after-recovery-of-funds-from-team-finance-exploit","type":"other","url":""},{"credibility":3,"name":"https://www.theblock.co/post/180369/hacker-uses-2700-to-drain-15-8-million-from-team-finance","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.certik.com/resources/blog/feg-bridge-exploit-technical-analysis","type":"other","url":""},{"credibility":3,"name":"https://www.halborn.com/blog/post/explained-the-feed-every-gorilla-feg-hack-december-2024","type":"other","url":""},{"credibility":3,"name":"https://protos.com/feg-token-holders-in-despair-after-third-hack-causes-99-dump/","type":"other","url":""},{"credibility":3,"name":"https://www.vibraniumaudits.com/post/feg-tokens-third-hack-in-december-2024-results-in-99-value-drop","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/academy/article/8c4f1c8b-b61c-4fae-9fc5-faa49e723d1b","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://docs.feg.io/welcome/security-audits","type":"other","url":""},{"credibility":3,"name":"https://certik.medium.com/feg-token-flashloan-exploit-analysis-5006070aca2d","type":"other","url":""},{"credibility":3,"name":"https://www.halborn.com/blog/post/explained-the-feed-every-gorilla-feg-hack-december-2024","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://docs.feg.io/recovery/old-fegex-sd-recovery","type":"other","url":""},{"credibility":3,"name":"https://www.bsc.news/post/feg-ready-for-migration-to-smart-defi-after-2nd-anniversary-launch-feb-22","type":"other","url":""},{"credibility":3,"name":"https://docs.feg.io/feg-smartdefi-tm/feg-upgrade","type":"other","url":""},{"credibility":3,"name":"https://protos.com/feg-token-holders-in-despair-after-third-hack-causes-99-dump/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://ambcrypto.com/making-defi-mainstream-an-interview-with-fegex-marketing-manager-chris/","type":"other","url":""},{"credibility":3,"name":"https://www.scam-detector.com/validator/fegtoken-com-review/","type":"other","url":""},{"credibility":3,"name":"https://www.quora.com/Is-the-FEG-crypto-token-a-scam","type":"other","url":""},{"credibility":3,"name":"https://fegrox.com/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://en.wikipedia.org/wiki/ZachXBT","type":"other","url":""},{"credibility":3,"name":"https://twitter.com/zachxbt","type":"other","url":""}]}],"sources_used":[],"summary":"FEGex is a decentralized exchange (DEX) and DeFi launchpad built around the FEG (Feed Every Gorilla) token ecosystem, operating on Ethereum and BNB Chain. The protocol has suffered three separate security exploits between 2022 and 2024, resulting in cumulative losses exceeding $3.6 million and a near-total collapse of token value following the most recent incident. The team operates anonymously and the protocol has demonstrated a repeated inability to prevent critical smart contract vulnerabilities despite multiple third-party audits.","timeline":[{"date":"2021-01-01","event":"FEG (Feed Every Gorilla) token launches on Ethereum and BNB Chain; FEGex DEX and FEGexPRO swap contracts deployed.","source":""},{"date":"2021-04-21","event":"Hotbit exchange lists FEG and FEGBSC tokens, broadening retail access.","source":""},{"date":"2022-05-15","event":"FEGexPRO contracts on Ethereum and BNB Chain exploited via flash loan attack targeting swapToSwap() input validation vulnerability; approximately $1.3 million (3,280 BNB + 144 ETH) stolen. Funds laundered via Tornado Cash.","source":""},{"date":"2022-05-16","event":"CertiK and BlockSec publish independent technical postmortems on the May 15 exploit.","source":""},{"date":"2022-10-01","event":"Team Finance, a liquidity lock platform used by FEG's SmartDeFi ecosystem, is exploited for $14.5 million total; FEG-associated losses estimated at approximately $950,000–$2 million.","source":""},{"date":"2022-10-30","event":"Team Finance exploiter returns approximately $1.9 million to affected projects; FEG recovers approximately 548 ETH. FEG token price rallies ~11%.","source":""},{"date":"2023-02-22","event":"FEG token migrates to new SmartDeFi-based contract at a 1,000,000:1 ratio, consolidating FEGeth, FEGbsc, and ROX tokens. Protocol restructuring announced.","source":""},{"date":"2023-03-13","event":"FEG team secures a 200 ETH liquidity loan to replenish FEGbsc liquidity pool post-migration.","source":""},{"date":"2024-12-29","event":"FEG SmartBridge cross-chain contract exploited via Wormhole relay message spoofing vulnerability; approximately $1.3 million (96.3 ETH on ETH, 73.3 ETH on Base, 712 BNB on BSC) stolen. FEG token price collapses approximately 99%. Funds laundered via Tornado Cash.","source":""},{"date":"2024-12-30","event":"CertiK and Halborn publish technical analyses confirming the bridge exploit was caused by flawed access control in FEG's own relay contract, not in the Wormhole protocol itself.","source":""}]},"v":1}