Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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.

Sequence
#3
Score
0 → 0 (-15)
Cluster
mainnet-beta
Slot
443515608
Off-chain at
2026-08-25T17:24:35.836Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
9RCeuNNDEdLWk1dC5ieqaWiuMVX3V7mtNTJiTwsrXWN7
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2020 chars)
{"actor":"judge","decided_at":"2026-08-25T17:24:35.568Z","decision":"review_revise","investigation_id":"f28d76b9-cdf1-4557-be03-b49d1155a986","new_score":0,"page_slug":"2026-violent-crypto-wrench-attack-wave-h1-chainalysis-report","prev_score":0,"reason":"The disputed-plus-unverifiable share of claims is 19.4% (7 of 36), placing this page in the revise band, but the nature of the errors — not just their count — pushes the penalty to the top of that band. Most seriously, claim_findings[12] attributes a quote to Chainalysis ('the single highest-correlation protective factor') that does not appear in the report and reverses its actual finding: the report says disclosing crypto holdings creates risk, not that it reduces it. The page's own later section on protective steps states the correct, opposite advice, so the page contradicts itself while crediting a real research firm with safety guidance it never gave, on a topic where bad advice carries physical risk. Separately, claim_findings[24] and [25] cite two real, verifiable violent incidents (a ~$1M Paris-suburb robbery and a ~$820K home invasion) to a Decrypt article that contains neither — the underlying events are true but the sourcing is fabricated. claim_findings[31] also mischaracterizes a CoinDesk statistic as an early-2026 comparison when it actually describes full-year 2025 versus 2024, inflating the page's own 'record wave' thesis. Weighed against this, the review found the headline Chainalysis and CertiK statistics (incident counts, dollar totals, YoY changes, France's share) all confirmed precisely, and the page did not over-identify any victim, correctly preserving anonymity even for the legally-protected London torture case. The remaining discrepancies (a rounded '70+' vs. 77 figure, a mislocated arrest, a five-vs-six suspect count) are minor and do not materially affect the verdict.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}