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
- #3
- Score
- 5 → 0 (-20)
- Cluster
- mainnet-beta
- Slot
- 443518928
- Off-chain at
- 2026-08-26T00:04:37.319Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 3fUTbGRJuVCPWckQmMDRzZ8H9Ptdz8mqb8E8Uwem8p5b
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1994 chars)
{"actor":"judge","decided_at":"2026-08-26T00:04:37.008Z","decision":"review_revise","investigation_id":"bba44da0-a72e-4e24-8e86-51fcdfad5505","new_score":0,"page_slug":"global-pig-butchering-enforcement-cluster-276-arrests-m-seizures-2026","prev_score":5,"reason":"Recounting the reviewer's 31 claim findings by hand (16 confirmed, 5 partially supported, 6 disputed, 4 unverifiable) and applying the disputed-plus-unverifiable formula yields 10/31 = 32.3%, just over the 30% line into the significant-issues band; the reviewer's own summary block undercounted total claims as 30 but the underlying array and math check out. The disputed findings are not minor date slips: the page's centerpiece section attributes a $701.96 million crypto restraint, 503 seized domains, a Telegram channel takedown, and device counts to the April 29 arrests, when the review shows independent reporting ties those same figures to a separate DOJ announcement six days earlier, and the April 29 release itself discloses no dollar figure at all (claim_findings[5], [9], [10], [11]). A phrase describing a Thai arrest as a distinct 'additional fugitive' obscures that the person is one of the four defendants named two sentences later (claim_findings[7]). Separately, the page asserts a February 26 aggregate figure 'encompasses' three later, and in one case larger, recoveries — which is not possible on the page's own numbers (claim_findings[28]). These are reinforced by two high-priority coverage gaps flagging the same attribution and chronology problems. Weighing against denial: every individual enforcement action, defendant, and charge is independently confirmed against primary sourcing, no charged individual is described as convicted, and the reviewer's confidence (0.72) is moderate rather than low, arguing for revision rather than the more severe outcomes.","score_delta":-20,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}