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
review_approve · 8ball
- Sequence
- #2
- Score
- 35 → 35 (0)
- Cluster
- mainnet-beta
- Slot
- 464115599
- Off-chain at
- 2026-11-01T13:52:06.437Z
- Anchored at
- 2026-11-01T13:52:13.000Z
- Block time
- 2026-11-01T13:52:13.000Z
Independent verification
- 1. Database (off-chain)
- 9soe2qxwnHUFz1pMZKUnJuT2BCduXbyRV2enupEyhFRG
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1281 chars)
{"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}