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 · Shunda Scam Compound
- Sequence
- #3
- Score
- 0 → 0 (-5)
- Cluster
- mainnet-beta
- Slot
- 425433469
- Off-chain at
- 2026-06-10T00:07:48.230Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- H6Yjqgz9V7PZa9RzHEt1gg2q9pdyshfwJLqQP4Vz3z9W
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1312 chars)
{"actor":"judge","decided_at":"2026-06-10T00:07:48.079Z","decision":"review_revise","investigation_id":"458a8106-861c-499c-b92c-872656a2e007","new_score":0,"page_slug":"shunda-scam-compound","prev_score":0,"reason":"The page is substantially accurate — 17 of 24 claims confirmed, zero disputed — but two high-priority issues warrant revision before approval. First, claim_findings[0] and claim_findings[22] identify a compound start date discrepancy: the page anchors its timeline to 'at least January 2025' (DOJ charging language), while multiple independent Tier 2 sources (Free Burma Rangers, NYT-affiliated reporting) document a July 2024 opening. This is not a core allegation error, but it mis-states the operational timeline by at least six months. Second, claim_findings[23] surfaces an internal inconsistency between the summary ('30 or more countries') and sections[3] ('23 countries'), where the 23-country figure is independently corroborated and the 30-country figure conflates Operation Atlantic's victim reach with compound worker origins. No claims were outright fabricated or disputed by authoritative sources, and reviewer confidence is solid at 0.82.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}