← 8ball2 decisions on this page
Audit log
Every state-changing event for 8ball: 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.
- #1reviewby reviewerreviewer2026-11-01 13:52:06ZScore: 35 → 35 (no score change)The page is a cautious ambiguity page that discloses its own limits. The Solana Billiards Hub market details match what a search snapshot shows. The Blockspot claims about 8Ball Finance could not be read because of a 403, so they are not scored. The MEXC 'listing' wording overstates things: the MEXC page marks the token as Unlisted. No shutdown, exploit or enforcement was found.anchoranchored
- chain
- ●mainnet-betaslot 464,115,593
- sig
2yr4o7s4A8Gu…KE7sNibfexplorer ↗- hash
6YgxDRwKqQK1…6FsBJ7Gysha256 → base58
verifying row…full verify ↗canonical bytes (1218 B) ▸
{"actor":"reviewer","artifact_identity":"f2f5b8ef2927371ee1b3a8a74f1cb38f","blocked_count":2,"decided_at":"2026-11-01T13:52:06.208Z","decision":"review","disputed_pct":0,"findings_hash":"9NkyxJQ3feD7WtZUtUUvzMCMzhhQdykLFoBPtxBVdZrF","investigation_id":"277eb9c0-e8f0-42c1-a3c2-fb5b9a898f35","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":35,"page_content_hash":"8f6d0ba05c48b7c9342db7c232724d17250f25c6653947d579d1be536ddcbd8d","page_slug":"8ball","prev_score":35,"reason":"The page is a cautious ambiguity page that discloses its own limits. The Solana Billiards Hub market details match what a search snapshot shows. The Blockspot claims about 8Ball Finance could not be read because of a 403, so they are not scored. The MEXC 'listing' wording overstates things: the MEXC page marks the token as Unlisted. No shutdown, exploit or enforcement was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":5,"sequence_num":1,"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 e0655e99-00d4-4933-8f2b-6fe99d283d1a - #2review approveby judgejudge2026-11-01 13:52:06ZScore: 35 → 35 (no score change)Of 7 claim findings, 2 were unreadable because Blockspot refused the reviewer (claim_findings[2], [3]) and are left out of the count. None of the remaining 5 were disputed or unverifiable, so the disputed share is 0%. The MEXC wording in claim_findings[4] and [5] calls an 'Unlisted' information page a 'listing', which is a minor overstatement that can be fixed with the reviewer's proposed wording. No shutdown, exploit or sanction was found, and no omissions were reported. The page also states its own limits, and the Blockspot-based claims were not checked, which is a coverage limit rather than a defect.anchoranchored
- chain
- ●mainnet-betaslot 464,115,599
- sig
gHMiFprWN14C…bzm1dikaexplorer ↗- hash
9soe2qxwnHUF…upEyhFRGsha256 → base58
verifying row…full verify ↗canonical bytes (1281 B) ▸
{"actor":"judge","artifact_identity":"f2f5b8ef2927371ee1b3a8a74f1cb38f","band_override":null,"blocked_count":2,"decided_at":"2026-11-01T13:52:06.208Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"277eb9c0-e8f0-42c1-a3c2-fb5b9a898f35","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":35,"page_slug":"8ball","prev_score":35,"reason":"Of 7 claim findings, 2 were unreadable because Blockspot refused the reviewer (claim_findings[2], [3]) and are left out of the count. None of the remaining 5 were disputed or unverifiable, so the disputed share is 0%. The MEXC wording in claim_findings[4] and [5] calls an 'Unlisted' information page a 'listing', which is a minor overstatement that can be fixed with the reviewer's proposed wording. No shutdown, exploit or sanction was found, and no omissions were reported. The page also states its own limits, and the Blockspot-based claims were not checked, which is a coverage limit rather than a defect.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":5,"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 746b2737-8ab8-452b-925a-3f61fe7c52f7
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>.