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
- Sequence
- #3
- Score
- 5 → 0 (-7)
- Cluster
- mainnet-beta
- Slot
- 462042545
- Off-chain at
- 2026-10-27T10:49:02.624Z
- Anchored at
- 2026-10-27T10:49:13.000Z
- Block time
- 2026-10-27T10:49:13.000Z
Independent verification
- 1. Database (off-chain)
- 4Zyk9XDdAjNNZvJmvMr5FaWWMVd3Km9qiKDgXKurLF7w
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2523 chars)
{"actor":"judge","artifact_identity":"dc3c919a4e32d57eb74cfd3aa9733af6","band_override":{"actual_delta":-7,"actual_verdict":"review_revise","disputed_pct":0.0714,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"Of 16 claim findings, 2 could not be checked because the source blocked the reviewer and were left out of the count. Of the remaining 14, none were disputed outright and 1 was unverifiable (claim_findings[3], the 11-token list), about 7%, which would normally be approved. Because 6 further findings were only partially supported, including the unhedged 'first known criminal prosecution' claim (claim_findings[5], [6]) and Hyperliquid short figures resting on tier-3 sources (claim_findings[11]), and because two high-priority coverage gaps remain (primary DOJ documents and the court docket), a small penalty and a minor-issues banner are applied. The core facts (charges, ages, penalties, employment spans, HYPE dates, Robinhood statement) were corroborated by multiple outlets, and the omissions found were minor."},"blocked_count":2,"decided_at":"2026-10-27T10:49:02.311Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.0714,"investigation_id":"b1d1eee2-65c9-4f2c-89c1-9297fa09ac82","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"robinhood-crypto-insider-trading-ring-chai-xiang-via-hyperliquid-2026","prev_score":5,"reason":"Of 16 claim findings, 2 could not be checked because the source blocked the reviewer and were left out of the count. Of the remaining 14, none were disputed outright and 1 was unverifiable (claim_findings[3], the 11-token list), about 7%, which would normally be approved. Because 6 further findings were only partially supported, including the unhedged 'first known criminal prosecution' claim (claim_findings[5], [6]) and Hyperliquid short figures resting on tier-3 sources (claim_findings[11]), and because two high-priority coverage gaps remain (primary DOJ documents and the court docket), a small penalty and a minor-issues banner are applied. The core facts (charges, ages, penalties, employment spans, HYPE dates, Robinhood statement) were corroborated by multiple outlets, and the omissions found were minor.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-7,"scored_claims":14,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}