← GeniusAI5 decisions on this page
Audit log
Every state-changing event for GeniusAI: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.
- #1publishby system:backfill2026-05-27 02:44:54ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 422,413,735
- sig
4J6X17L4Ap9Q…1cqC2hbPexplorer ↗- hash
J6uf9EgxkVEd…P2bmChWBsha256 → base58
verifying row…full verify ↗canonical bytes (5718 B) ▸
{"actor":"system:backfill","investigation_id":"9caf0d23-f3a5-4cfd-8cc2-13b8afe83513","kind":"publish","page_slug":"geniusai","published_at":"2026-05-27T02:44:54.814Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"GeniusAI","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coingecko.com/en/coins/genius-ai","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/genius-token-nft-collections/","type":"other","url":""},{"credibility":3,"name":"https://iq.wiki/wiki/gnus-ai","type":"other","url":""},{"credibility":3,"name":"https://theorg.com/org/genius-ventures/org-chart/kenneth-hurley","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.ccn.com/news/crypto/discord-hacked-million-stolen-gnus-ai-exploit/","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/news/feed/f3d12-gnus-ai-network-suffers-1-27m-exploit","type":"other","url":""},{"credibility":3,"name":"https://coincodecap.com/gnus-ai-discord-server-hack-results-in-1-27m-losses","type":"other","url":""},{"credibility":3,"name":"https://coinpaper.com/4140/gnus-ai-announces-new-token-launch-after-1-27-million-exploit","type":"other","url":""},{"credibility":3,"name":"https://www.web3isgoinggreat.com/?id=gnusai-exploi","type":"other","url":""},{"credibility":3,"name":"https://www.cryptometer.io/news/1-27-million-lost-in-gnus-ai-discord-hack-and-token-exploit/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://coinpaper.com/4140/gnus-ai-announces-new-token-launch-after-1-27-million-exploit","type":"other","url":""},{"credibility":3,"name":"https://coincodecap.com/gnus-ai-discord-server-hack-results-in-1-27m-losses","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/news/feed/f3d12-gnus-ai-network-suffers-1-27m-exploit","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coingecko.com/en/coins/genius-ai","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/genius-token-nft-collections/","type":"other","url":""},{"credibility":3,"name":"https://coincodex.com/crypto/gnus-token/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://coincodecap.com/gnus-ai-discord-server-hack-results-in-1-27m-losses","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/news/feed/f3d12-gnus-ai-network-suffers-1-27m-exploit","type":"other","url":""},{"credibility":3,"name":"https://www.web3isgoinggreat.com/?id=gnusai-exploi","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://en.wikipedia.org/wiki/ZachXBT","type":"other","url":""},{"credibility":3,"name":"https://t.me/s/investigations","type":"other","url":""},{"credibility":3,"name":"https://www.ccn.com/education/crypto/zachxbt-crypto-detective-uncovering-blockchain-scams/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.web3isgoinggreat.com/?id=gnusai-exploi","type":"other","url":""},{"credibility":3,"name":"https://coincodecap.com/gnus-ai-discord-server-hack-results-in-1-27m-losses","type":"other","url":""}]}],"sources_used":[],"summary":"GNUS.AI (Genius Ventures, Inc.) is a decentralized AI computing platform that issues the GNUS token across Ethereum, Polygon, and Fantom networks. On May 5, 2024, the project suffered a $1.27 million exploit in which an attacker leveraged a Discord breach to steal private key material, mint 100 million counterfeit GNUS tokens, and sell them into live liquidity pools — causing the token price to collapse. The token has traded 98-99% below its all-time high and ZachXBT has flagged the entity as a concern in the crypto community.","timeline":[{"date":"2016-06-01","event":"Kenneth Hurley and Brent Arias co-found Genius Ventures, Inc., the parent entity behind GNUS.AI, with a focus on AI/ML cryptotoken infrastructure.","source":""},{"date":"2024-03-22","event":"GNUS token reaches an alleged all-time high of approximately $101.92 according to some market trackers, prior to the exploit.","source":""},{"date":"2024-05-05","event":"GNUS.AI Discord server is compromised. Attacker gains access to team's private communications and the 0x18 deployment wallet private key. 100 million counterfeit GNUS tokens are minted on Fantom via the Axelar bridge, then bridged to Ethereum and Polygon and sold, causing $1.27 million in losses.","source":""},{"date":"2024-05-07","event":"GNUS.AI team publicly discloses the exploit. CEO 'SuperGenius' acknowledges Discord was the attack vector. Team urges all users to stop purchasing the compromised token. Buyback-and-burn strategy announced along with a white-hat bounty of 10% of stolen funds.","source":""},{"date":"2024-05-07","event":"Blockchain security firm CertiK confirms the exploit mechanism: attacker generated tokens from nothing and exchanged them for legitimate assets. Estimated loss confirmed at approximately $1.25-1.27 million.","source":""},{"date":"2024-05-07","event":"GNUS.AI announces remediation plan: $500,000 in ETH deposited to new token liquidity pool at launch, plus $500,000 in locked fees (available February 2025), targeting coverage of approximately 80% of losses.","source":""},{"date":"2025-02-01","event":"Alleged unlock date for the second $500,000 tranche of locked compensation fees per the team's stated remediation plan.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision ae1d9d2a-98f4-4ce2-88a9-8ed3b7d43637 - #2rescoreby systemsystem2026-10-10 18:46:46ZScore: 28 → 60 (+32)Rescored under Scoring v2, the published formula (avoid.net/scoring): 28 → 60. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −3.2, problems around the subject, caused by others −2.4; legitimacy credit long-running +10.anchoranchored
- chain
- ●mainnet-betaslot 455,366,564
- sig
58NQ2Fn2nPDx…ENqLyrZwexplorer ↗- hash
9wmGnjQQyoj6…aQTEF71Hsha256 → base58
verifying row…full verify ↗canonical bytes (640 B) ▸
{"actor":"system","decided_at":"2026-10-10T18:46:46.895Z","decision":"rescore","investigation_id":"9caf0d23-f3a5-4cfd-8cc2-13b8afe83513","new_score":60,"page_slug":"geniusai","prev_score":28,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 28 → 60. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −3.2, problems around the subject, caused by others −2.4; legitimacy credit long-running +10.","score_delta":32,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision d4bb2bd4-dced-49a8-8d64-0a232912b9a2 - #3reviewby reviewerreviewer2026-11-02 03:30:05ZScore: 60 → 60 (no score change)The core exploit facts (May 5 2024, about $1.27M, Discord-derived key, Axelar bridge, 100M counterfeit tokens) are corroborated. The 80% coverage figure is wrongly attributed to CertiK. The bounty, $1 repurchase and buyback-and-burn details were not found in the cited sources I read, and the ZachXBT flag is unsupported by any cited source. Price figures are out of date. Founder background and corporate history claims were not checked. The subject is still operating.anchoranchored
- chain
- ●mainnet-betaslot 464,344,657
- sig
5E97zB6Z6yq5…joUgX1Vsexplorer ↗- hash
6jJg8Za83DT6…EzdiCSESsha256 → base58
verifying row…full verify ↗canonical bytes (1318 B) ▸
{"actor":"reviewer","artifact_identity":"a8dcd5f6a22f7ae5c4f11b01556b71bd","decided_at":"2026-11-02T03:30:05.576Z","decision":"review","disputed_pct":0.4286,"findings_hash":"Fz8kVfv7MqKp1xb5A1uVMvYCqYHNGWK7mpSPxhvUFDDS","investigation_id":"9caf0d23-f3a5-4cfd-8cc2-13b8afe83513","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"omissions":{"material":0,"total":1},"page_content_hash":"0d288c464b8873504c11c87b491541985232674946b191e4c57684c635f8ab18","page_slug":"geniusai","prev_score":60,"reason":"The core exploit facts (May 5 2024, about $1.27M, Discord-derived key, Axelar bridge, 100M counterfeit tokens) are corroborated. The 80% coverage figure is wrongly attributed to CertiK. The bounty, $1 repurchase and buyback-and-burn details were not found in the cited sources I read, and the ZachXBT flag is unsupported by any cited source. Price figures are out of date. Founder background and corporate history claims were not checked. The subject is still operating.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 230eabff-32e8-4411-abd0-c35df7451e3b - #4review reviseby judgejudge2026-11-02 03:30:05ZScore: 60 → 60 (no score change)The core exploit account (May 5, 2024, about $1.27M, Discord-derived key, 100M counterfeit tokens) was corroborated by two sources (claim_findings[0]). However, 3 of 7 checked claims (about 43%) were disputed or could not be verified: the 80% remediation figure is attributed to CertiK but is the project's own goal (claim_findings[1]), the bounty, $1 repurchase and buyback details were not found in the cited sources (claim_findings[2]), and the ZachXBT flag, which is repeated in the page summary, is not supported by any cited source (claim_findings[4]). The price range is also out of date (claim_findings[6]). The penalty sits at the milder end of the band because the reviewer's confidence is moderate (0.5), the central exploit facts hold, and the only omission (contract proxy risk) is minor. A high-priority gap remains: no on-chain evidence such as transaction hashes or attacker addresses.anchoranchored
- chain
- ●mainnet-betaslot 464,344,663
- sig
3Kg8PXt68Tea…XxxxEoE8explorer ↗- hash
52v7jX6nX7RK…EZzBAbrisha256 → base58
verifying row…full verify ↗canonical bytes (1543 B) ▸
{"actor":"judge","artifact_identity":"a8dcd5f6a22f7ae5c4f11b01556b71bd","band_override":null,"decided_at":"2026-11-02T03:30:05.576Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4286,"investigation_id":"9caf0d23-f3a5-4cfd-8cc2-13b8afe83513","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"page_slug":"geniusai","prev_score":60,"reason":"The core exploit account (May 5, 2024, about $1.27M, Discord-derived key, 100M counterfeit tokens) was corroborated by two sources (claim_findings[0]). However, 3 of 7 checked claims (about 43%) were disputed or could not be verified: the 80% remediation figure is attributed to CertiK but is the project's own goal (claim_findings[1]), the bounty, $1 repurchase and buyback details were not found in the cited sources (claim_findings[2]), and the ZachXBT flag, which is repeated in the page summary, is not supported by any cited source (claim_findings[4]). The price range is also out of date (claim_findings[6]). The penalty sits at the milder end of the band because the reviewer's confidence is moderate (0.5), the central exploit facts hold, and the only omission (contract proxy risk) is minor. A high-priority gap remains: no on-chain evidence such as transaction hashes or attacker addresses.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision fb94c598-1e8b-4864-a135-4c8223ba0f89 - #5rescoreby systemsystem2026-11-02 03:30:06ZScore: 60 → 64 (+4)Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 60 → 64. Problems weighed by who is responsible: concerns that are not fraud −6.4, incidents the subject suffered −3.2, problems around the subject, caused by others −1.6; legitimacy credit long-running +10; 2 section(s) set aside until a failed fact-check is resolved.anchoranchored
- chain
- ●mainnet-betaslot 464,344,668
- sig
kgjskXy2Dj7B…Sk3sVNPPexplorer ↗- hash
GEMygcUhJ4ZP…aFhqWHupsha256 → base58
verifying row…full verify ↗canonical bytes (750 B) ▸
{"actor":"system","decided_at":"2026-11-02T03:30:05.576Z","decision":"rescore","investigation_id":"9caf0d23-f3a5-4cfd-8cc2-13b8afe83513","new_score":64,"page_slug":"geniusai","prev_score":60,"reason":"Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 60 → 64. Problems weighed by who is responsible: concerns that are not fraud −6.4, incidents the subject suffered −3.2, problems around the subject, caused by others −1.6; legitimacy credit long-running +10; 2 section(s) set aside until a failed fact-check is resolved.","score_delta":4,"score_model":"v2","sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision d9ef4155-82f7-4380-999a-b743f16a3efe
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine —
python -m src.verify_decision <event_id>.