← GMBL.COMPUTER5 decisions on this page
Audit log
Every state-changing event for GMBL.COMPUTER: 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-29 17:03:41ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 422,980,027
- sig
5WhMA8SAhrgW…gAtqkyyZexplorer ↗- hash
4NvnGWz44zM9…21EDYif1sha256 → base58
verifying row…full verify ↗canonical bytes (6212 B) ▸
{"actor":"system:backfill","investigation_id":"58e16f5e-e997-46fd-93c1-c837c9e45ba3","kind":"publish","page_slug":"gmblcomputer","published_at":"2026-05-29T17:03:41.783Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"GMBL.COMPUTER","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://gmblcomputer.gitbook.io/gmbl.computer","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/gmbl-computer/","type":"other","url":""},{"credibility":3,"name":"https://arbiscan.io/token/0xE9A5aF50874c0ef2748b5DB70104B5ccb5557f6d","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/ico/gmbl-computer","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://gmblcomputer.medium.com/gmbl-computer-exploit-postmortem-a09aa3297405","type":"other","url":""},{"credibility":3,"name":"https://beincrypto.com/defi-gmbl-computer-exploited-eth-funds-returned/","type":"other","url":""},{"credibility":3,"name":"https://www.web3isgoinggreat.com/single/gmblcomputer-exploit","type":"other","url":""},{"credibility":3,"name":"https://coincu.com/215747-gmblcomputer-key-leaked-loss-nearly-500-eth/","type":"other","url":""},{"credibility":3,"name":"https://slowmist.medium.com/slowmist-weekly-security-report-september-4rd-to-10th-3310d4258f48","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://beincrypto.com/defi-gmbl-computer-exploited-eth-funds-returned/","type":"other","url":""},{"credibility":3,"name":"https://www.web3isgoinggreat.com/single/gmblcomputer-exploit","type":"other","url":""},{"credibility":3,"name":"https://gmblcomputer.medium.com/gmbl-computer-exploit-postmortem-a09aa3297405","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://gmblcomputer.gitbook.io/gmbl.computer","type":"other","url":""},{"credibility":3,"name":"https://www.web3isgoinggreat.com/single/gmblcomputer-exploit","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://gmblcomputer.gitbook.io/gmbl.computer","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/gmbl-computer/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://gmblcomputer.medium.com/gmbl-computer-exploit-postmortem-a09aa3297405","type":"other","url":""},{"credibility":3,"name":"https://slowmist.medium.com/slowmist-weekly-security-report-september-4rd-to-10th-3310d4258f48","type":"other","url":""},{"credibility":3,"name":"https://gmblcomputer.gitbook.io/gmbl.computer","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://coinmarketcap.com/currencies/gmbl-computer/","type":"other","url":""},{"credibility":3,"name":"https://dexscreener.com/arbitrum/0x70eb6e93e1f8bfb850126e23a1964fd3db789948","type":"other","url":""},{"credibility":3,"name":"https://www.coingecko.com/en/coins/gmbl-computer-chip","type":"other","url":""},{"credibility":3,"name":"https://coinbrain.com/coins/eth-0xa395bd32dd0ac0823bf160cd6e0db2ac08d7cdcd","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.web3isgoinggreat.com/single/gmblcomputer-exploit","type":"other","url":""},{"credibility":3,"name":"https://slowmist.medium.com/slowmist-weekly-security-report-september-4rd-to-10th-3310d4258f48","type":"other","url":""},{"credibility":3,"name":"https://twitter.com/gmblcomputer","type":"other","url":""}]}],"sources_used":[],"summary":"GMBL.COMPUTER is an Arbitrum-based DeFi gambling protocol that launched in September 2023 and was exploited within hours of going live, losing approximately 471 ETH (~$770,000) due to an off-chain server signature vulnerability and a flaw in its referral system. The exploiter returned roughly half of the stolen funds (235 ETH) after the team issued a conditional bug bounty offer. The protocol operates with an anonymous team, no disclosed security audits, no regulatory licensing, and as of 2025 shows near-zero trading volume and minimal on-chain activity.","timeline":[{"date":"2023-08-25","event":"GMBL token launches via Liquidity Bootstrapping Pool on Camelot Exchange on Arbitrum. Presale raised approximately $100,000.","source":""},{"date":"2023-09-05","event":"GMBL.COMPUTER protocol officially launches on Arbitrum mainnet.","source":""},{"date":"2023-09-06","event":"Exploit occurs within approximately 24 hours of launch. Attacker spoof-calls GMBL's off-chain server to obtain a valid signature, withdrawing approximately 471 ETH (~$770,000) worth of GMBL tokens. A secondary referral abuse vector allows approximately 8 million GMBL to be claimed on ghost bets. GMBL token price drops approximately 75%.","source":""},{"date":"2023-09-06","event":"GMBL team suspends all contract interactions and publicly identifies the attacker. Team issues a conditional bug bounty: return 90% of funds by 9 PM EST or face legal action.","source":""},{"date":"2023-09-06","event":"Attacker returns 235 ETH (~$382,000), approximately 50% of stolen funds, to GMBL's multisig wallet. Remaining ~236 ETH is not recovered.","source":""},{"date":"2023-09-07","event":"GMBL team publishes exploit postmortem on Medium, acknowledging the vulnerability was an off-chain server signature issue and a flaw in the referral system described as a 'one-line fix.' Team commits to third-party audits before relaunch.","source":""},{"date":"2023-09-10","event":"SlowMist includes the GMBL.COMPUTER exploit in their weekly security report covering September 4-10, 2023.","source":""},{"date":"2023-11-30","event":"GMBL token reaches all-time high price of approximately $0.171.","source":""},{"date":"2025-01-01","event":"Protocol shows near-zero trading volume and approximately 19 token holders. Market cap approximately $156,000. No confirmed successful relaunch with promised security enhancements has been publicly documented.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision ca9f8e47-ee24-4e03-8106-d5c2dd385b6c - #2rescoreby systemsystem2026-10-27 06:03:35ZScore: 38 → 46 (+8)Rescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 46. Problems weighed by who is responsible: concerns that are not fraud −12.8, incidents the subject suffered −6.4, problems around the subject, caused by others −1.6; legitimacy credit long-running +2.anchoranchored
- chain
- ●mainnet-betaslot 461,963,169
- sig
iyZLA424Se2a…zuJcuGaAexplorer ↗- hash
5gkb1QMp4ZmR…3HmZxGKzsha256 → base58
verifying row…full verify ↗canonical bytes (643 B) ▸
{"actor":"system","decided_at":"2026-10-27T06:03:35.834Z","decision":"rescore","investigation_id":"58e16f5e-e997-46fd-93c1-c837c9e45ba3","new_score":46,"page_slug":"gmblcomputer","prev_score":38,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 46. Problems weighed by who is responsible: concerns that are not fraud −12.8, incidents the subject suffered −6.4, problems around the subject, caused by others −1.6; legitimacy credit long-running +2.","score_delta":8,"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 ac371079-0ecb-4de7-af94-fa5cae00b8c4 - #3reviewby reviewerreviewer2026-11-02 05:28:06ZScore: 46 → 46 (no score change)The core incident facts (about 471 ETH lost, signature spoof, referral ghost bets, 235 ETH returned, bounty terms, team anonymity, software-company framing) are supported by Web3 Is Going Great, the project's GitBook and search snippets of coverage. Weaker parts are the fundraising and supply figures, the 2025 holder and market data (possibly a different token) and the ZachXBT section, for which no cited source gives support. No claim was found to be disputed. Several primary sources could not be fetched directly.anchoranchored
- chain
- ●mainnet-betaslot 464,377,648
- sig
4U5uswHs2FFa…mvnmfUmmexplorer ↗- hash
AByvFsKUhbuv…sFNX4ciasha256 → base58
verifying row…full verify ↗canonical bytes (1332 B) ▸
{"actor":"reviewer","artifact_identity":"6bd7ce340ed7ccf3a21e576a9b245352","decided_at":"2026-11-02T05:28:06.700Z","decision":"review","disputed_pct":0.4286,"findings_hash":"AAc3ekF1CGyAEqNj3uThAw7eR8iSSBjTRtvHiQcFoYKS","investigation_id":"58e16f5e-e997-46fd-93c1-c837c9e45ba3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":46,"page_content_hash":"50042d42c525d10584bc6cbd893d885450a1f64c86e7e4c5bef25fb2fa874b4e","page_slug":"gmblcomputer","prev_score":46,"reason":"The core incident facts (about 471 ETH lost, signature spoof, referral ghost bets, 235 ETH returned, bounty terms, team anonymity, software-company framing) are supported by Web3 Is Going Great, the project's GitBook and search snippets of coverage. Weaker parts are the fundraising and supply figures, the 2025 holder and market data (possibly a different token) and the ZachXBT section, for which no cited source gives support. No claim was found to be disputed. Several primary sources could not be fetched directly.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"unknown","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 baf74bbb-c1bd-4de7-8293-14800ad02b70 - #4review reviseby judgejudge2026-11-02 05:28:06ZScore: 46 → 46 (no score change)The core incident facts (about 471 ETH lost, off-chain signature spoof, referral abuse, 235 ETH returned, anonymous team) were confirmed, and no claim was disputed. However, 3 of 7 claims (about 43%) could not be verified: the $100,000 raise and 100 million supply (claim_findings[3]), the 2025 holder and market cap data, which may refer to a different token (claim_findings[5]), and the ZachXBT association, which no cited source supports (claim_findings[6]). Because nothing was contradicted and reviewer confidence is moderate, the penalty is set at the lower end of the band and the page is revised rather than denied.anchoranchored
- chain
- ●mainnet-betaslot 464,377,654
- sig
ATqfnnFG4hEy…apsQnDQiexplorer ↗- hash
6f3z7HFFe2j5…C4qZAYZKsha256 → base58
verifying row…full verify ↗canonical bytes (1269 B) ▸
{"actor":"judge","artifact_identity":"6bd7ce340ed7ccf3a21e576a9b245352","band_override":null,"decided_at":"2026-11-02T05:28:06.700Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4286,"investigation_id":"58e16f5e-e997-46fd-93c1-c837c9e45ba3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":46,"page_slug":"gmblcomputer","prev_score":46,"reason":"The core incident facts (about 471 ETH lost, off-chain signature spoof, referral abuse, 235 ETH returned, anonymous team) were confirmed, and no claim was disputed. However, 3 of 7 claims (about 43%) could not be verified: the $100,000 raise and 100 million supply (claim_findings[3]), the 2025 holder and market cap data, which may refer to a different token (claim_findings[5]), and the ZachXBT association, which no cited source supports (claim_findings[6]). Because nothing was contradicted and reviewer confidence is moderate, the penalty is set at the lower end of the band and the page is revised rather than denied.","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 4d36603c-f73d-4e9d-9376-0206b7c992d8 - #5rescoreby systemsystem2026-11-02 05:28:07ZScore: 46 → 51 (+5)Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 46 → 51. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −6.4; legitimacy credit long-running +2; 3 section(s) set aside until a failed fact-check is resolved.anchoranchored
- chain
- ●mainnet-betaslot 464,377,659
- sig
2bemQr2VkXN8…v8pRrWmvexplorer ↗- hash
7GEZf6zyf9qC…LmEsyM7esha256 → base58
verifying row…full verify ↗canonical bytes (701 B) ▸
{"actor":"system","decided_at":"2026-11-02T05:28:06.700Z","decision":"rescore","investigation_id":"58e16f5e-e997-46fd-93c1-c837c9e45ba3","new_score":51,"page_slug":"gmblcomputer","prev_score":46,"reason":"Recalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 46 → 51. Problems weighed by who is responsible: concerns that are not fraud −9.6, incidents the subject suffered −6.4; legitimacy credit long-running +2; 3 section(s) set aside until a failed fact-check is resolved.","score_delta":5,"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 56f206f1-69f7-486b-9469-0ef4054479a1
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>.