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_revise · Shuffle (shuffle.com)
- Sequence
- #3
- Score
- 38 → 26 (-12)
- Cluster
- mainnet-beta
- Slot
- 443513183
- Off-chain at
- 2026-08-25T10:04:01.452Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DxjRWXkof8xyWgmaZxmTwhQ8qN9Pej1Z6yxzY79Wi3wi
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1447 chars)
{"actor":"judge","decided_at":"2026-08-25T10:04:01.009Z","decision":"review_revise","investigation_id":"abe68948-0c6d-437a-9c8a-629b64c141cd","new_score":26,"page_slug":"shuffle-shuffle-com","prev_score":38,"reason":"The fact-check found 23 of 31 claims fully confirmed, including the entity's core identity, licensing (verified directly against the regulator's own record), the October 2025 data breach, and the ZachXBT/Milanovich account-lock allegation, which was quote-matched against its cited source. However, claim_findings[24] — the '~$20,000 withdrawal held since July 31, 2026' complaint used as the flagship example of the page's withdrawal-complaints section — does not match its own cited AskGamblers source, which describes a smaller withdrawal (3,000 USDC + 14 SOL) filed roughly a year earlier. Combined with a high-priority coverage gap calling for that section to be re-sourced, plus a second high-priority gap noting the ZachXBT theft allegations lack on-chain corroboration, this pushes the page into revise territory even though the overall disputed rate (12.9%) is low. Several minor imprecisions among partially-supported claims (an 'FTX employee' characterization, wager-timing, and Trustpilot review-count figures) further support a moderate correction rather than a clean pass.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}