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
22 (0)
Cluster
mainnet-beta
Slot
443516646
Off-chain at
2026-08-25T19:34:10.135Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
HU8WoxFvqqcXatgNv156UBs8YpqLWZQkVyd75NA7j8U
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1820 chars)
{"actor":"judge","decided_at":"2026-08-25T19:34:09.723Z","decision":"review_approve","investigation_id":"cd64718e-7aef-46c7-baa8-20107e9a16df","new_score":2,"page_slug":"siavash-kayvanpour-ofac-designated-shelbit-founder","prev_score":2,"reason":"The reviewer checked every factual claim on this page against primary sources and found none disputed and none unverifiable, putting the disputed rate at 0%. The central allegation — that OFAC personally designated Siavash Kayvanpour on August 7, 2026 for material support to the IRGC — was confirmed directly against Treasury's own press release (claim_findings[0]), and a set of Dubai regulator (VARA) enforcement dates that could easily have been a fabricated citation was instead verified against the regulator's own notice (claim_findings[11]). The page also correctly keeps a journalist's inability to confirm direct IRGC control of Shelbit separate from OFAC's own material-support finding, rather than blurring the two (claim_findings[10]). The only defect found is a timeline entry that lumps two January 2026 events under an imprecise placeholder date rather than the correct January 30, 2026 date for one of them (claim_findings[13], rated partially_supported, not disputed). No coverage gap was rated high priority. Given zero disputed claims, zero unverifiable claims, no link rot or staleness on critical citations, and a comparatively high reviewer confidence of 0.85, the page is approved as published; the date-bucketing issue and the two medium-priority gaps (a missing direct SDN List citation and no update on Kayvanpour's personal response) warrant a correction note and future monitoring, not a score penalty.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}