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 · GMBL.COMPUTER
- Sequence
- #4
- Score
- 46 → 46 (0)
- Cluster
- mainnet-beta
- Slot
- 464377654
- Off-chain at
- 2026-11-02T05:28:06.921Z
- Anchored at
- 2026-11-02T05:28:26.000Z
- Block time
- 2026-11-02T05:28:26.000Z
Independent verification
- 1. Database (off-chain)
- 6f3z7HFFe2j5F6X5GRLv6fW163T8v3SFfjJNC4qZAYZK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1269 chars)
{"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}