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 · Hu Xiaowei (Prince Group second-in-command)
- Sequence
- #3
- Score
- 2 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 464281591
- Off-chain at
- 2026-11-01T23:45:05.249Z
- Anchored at
- 2026-11-01T23:45:19.000Z
- Block time
- 2026-11-01T23:45:19.000Z
Independent verification
- 1. Database (off-chain)
- 3cShNVaXCUnWz5mSGeUGVTe8iJ8NyLdr7eu1Fcyvc6jD
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2126 chars)
{"actor":"judge","artifact_identity":"fe33a2d06f228c5fc2926be7d80a16a0","band_override":null,"blocked_count":2,"decided_at":"2026-11-01T23:45:04.943Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"68de517f-5b4c-44f5-b9e0-8d9ace985e16","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"hu-xiaowei-prince-group-second-in-command","prev_score":2,"reason":"Core claims drawn from the U.S. Treasury release (designation date, counts, entities, subordinates, quotes) were confirmed (claim_findings[0], [5], [6], [7], [8]). However, the page says Hu was arrested 'on charges' of filing falsified residency records when sources report only suspicion (claim_findings[2], [3]), and its summary implies the June 2026 designation was his first when Treasury says he was previously designated in October 2025 under the alias Chen Xiao'er (claim_findings[1]). The page also omits post-June developments, including a reported Japan re-arrest and UK sanctions, so it is revised with a modest penalty. Two OCCRP-sourced findings could not be read because the source blocked the reviewer; this is a coverage limit, not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"scored_claims":9,"sequence_num":3,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"Computed disputed_pct is 0% (0 disputed or unverifiable of 9 scored findings; 2 source_blocked findings excluded), but the review reports three material omissions (reported July 2026 Japan re-arrest, UK sanctions and asset freeze, reported expulsion to the US) and a high-priority coverage gap on post-June developments. Three findings are also only partially supported, including wording on a named living person. Escalated to the minor band rather than significant because the omissions are partly weakly sourced and the page's core Treasury claims are confirmed."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}