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
- #4
- Score
- 0 → 0 (-18)
- Cluster
- mainnet-beta
- Slot
- 464363911
- Off-chain at
- 2026-11-02T04:38:55.474Z
- Anchored at
- 2026-11-02T04:39:17.000Z
- Block time
- 2026-11-02T04:39:17.000Z
Independent verification
- 1. Database (off-chain)
- Ed6vnZYpM9NTtk3RFCkXaYzCMBDtKYxqJeSFDpgGT8kt
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1553 chars)
{"actor":"judge","artifact_identity":"e2d2ed39dc79016a716cca8d69661009","band_override":null,"decided_at":"2026-11-02T04:38:55.222Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3846,"investigation_id":"bce46df2-204a-4509-be16-8aac8a27b71d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"doj-global-pig-butchering-takedown-ko-thet-sanduo-giant-company","prev_score":0,"reason":"Of 13 claims checked, 4 were disputed and 1 could not be verified, giving a disputed rate of about 38%. The core facts (defendants, charges, the $701M restraint, 503 domains, the Shunda details and the OFAC designations) match DOJ and Treasury releases. The errors are real but mostly attributional or about precision: the 20,000 victims / 30 countries figure belongs to the separate Operation Atlantic (claim_findings[0]), the fugitive co-defendants are called 'named' when DOJ does not name them (claim_findings[1]), the Dubai arrests are over-attributed (claim_findings[2]), and the KNLA seizure date is more specific than the source allows (claim_findings[4]). Disruption Week wording also overstates 'disrupted' as 'eliminated' (claim_findings[5], [6]). No omissions or contradictions of subject status were found, and reviewer confidence is moderate.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-18,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}