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
- #2
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 464281586
- Off-chain at
- 2026-11-01T23:45:05.015Z
- Anchored at
- 2026-11-01T23:45:18.000Z
- Block time
- 2026-11-01T23:45:18.000Z
Independent verification
- 1. Database (off-chain)
- 3qbnW3kHdPWcT1u38jvoLBo55goCjjxhkWTGkZzNo8Ht
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1393 chars)
{"actor":"reviewer","artifact_identity":"fe33a2d06f228c5fc2926be7d80a16a0","blocked_count":2,"decided_at":"2026-11-01T23:45:04.943Z","decision":"review","disputed_pct":0,"findings_hash":"GPHqfkhuSUwcqnPp1CuGWdFcVmkgXQEuah2geV6mAP5Q","investigation_id":"68de517f-5b4c-44f5-b9e0-8d9ace985e16","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":2,"omissions":{"material":3,"total":4},"page_content_hash":"42e010b12d856e569446d450c4b9ff05e7cd4fd01827487d4bc7675eb3aecc18","page_slug":"hu-xiaowei-prince-group-second-in-command","prev_score":2,"reason":"Treasury-sourced claims (designation date, counts, entities, subordinates, quotes) are confirmed. Weaknesses: the summary says arrested on 'charges' where sources say suspicion only, and implies the June designation was Hu's first when Treasury says he was designated in October 2025 as Chen Xiao'er. OCCRP-only claims could not be read (403) and are not scored. The page omits post-June developments, including a reported July expulsion to the US, a Japan re-arrest and UK actions.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":2,"subject_status":"sanctioned","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}