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 · DOJ $225M Pig Butchering Seizure Campaign (2026)
- Sequence
- #3
- Score
- 10 → 0 (-18)
- Cluster
- mainnet-beta
- Slot
- 462181114
- Off-chain at
- 2026-10-27T19:00:03.784Z
- Anchored at
- 2026-10-27T19:00:21.000Z
- Block time
- 2026-10-27T19:00:21.000Z
Independent verification
- 1. Database (off-chain)
- MkYuv1HyJ5MpqUoWsTv2ZQ2fF3Fbmsz4CciTZvn9nQp
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1450 chars)
{"actor":"judge","artifact_identity":"104db7edbfe80492d35016746b8fca9c","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T19:00:03.440Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4667,"investigation_id":"b2c52957-6027-4544-8e3d-8f7e0bb93f79","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"doj-225m-pig-butchering-seizure-campaign-2026","prev_score":10,"reason":"Of 17 checked claims, 2 could not be read because the source blocked the reviewer and are left out of the count. Of the remaining 15, 6 were disputed (claim_findings[0], [1], [2], [3], [4], [5]) and 1 could not be verified (claim_findings[11]), a disputed share of about 47%. The disputes are mostly date, attribution and case-number errors: the takedown announcement date (April 29, not May 8), Awang's arrest by Thai police rather than Dubai, the Zoomex freeze lead time, and a case number the page contradicts elsewhere. The core allegations (the $225M action, the 276 arrests, the Level Up statistics, the $580M milestone) were confirmed, and the omissions are minor, so the penalty sits at the lower end of the significant band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-18,"scored_claims":15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}