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.

Decision
review_revise · Siavash Kayvanpour
View on Solana ↗
Sequence
#3
Score
20 (-10)
Cluster
mainnet-beta
Slot
443517983
Off-chain at
2026-08-25T22:46:49.777Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
6ZcGMngxFvFArj32jANiKwrDofromePaDZEEtAj8ocns
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2021 chars)
{"actor":"judge","decided_at":"2026-08-25T22:46:49.391Z","decision":"review_revise","investigation_id":"c085b4ca-51b9-4be4-bcf4-a89fd7148bed","new_score":0,"page_slug":"siavash-kayvanpour","prev_score":2,"reason":"The page's central allegations — Kayvanpour's personal OFAC/E.O. 13224 designation, the sanctioned corporate network, and the IRGC/Nobitex/Binance dollar flows — are all confirmed directly against the Treasury press release and independent reporting (claim_findings[0]-[6], [10]-[13]). However, claim_findings[9] found that the page inverts a regulatory enforcement sequence: it describes Dubai's VARA as issuing a fine in January 2025 followed by a cease-and-desist order in July 2026, when both the regulator's own notice and the page's own cited source state the reverse — cease-and-desist first, fine 18 months later. That reversal changes the story from 'enforcement escalating over time' to 'a strict order followed by an 18-month gap before a fine,' which misrepresents the regulator's actual posture toward the company. Separately, claim_findings[8] found that the page's section on Kayvanpour's 2023 Iranian gambling conviction omits that the conviction was rendered in absentia, a detail that changes how much weight a reader should put on it, and claim_findings[7] found the page understates how flatly two co-defendants denied any connection to Kayvanpour or Shelbit. The timeline also assigns a fabricated precise date (January 1, 2023) to an event sources only date to the year. Individually these are secondary-characterization problems rather than fabrications of the core sanctions basis, but on a page naming a living, sanctioned individual and describing a criminal conviction, the combination of an inverted enforcement narrative and softened conviction/denial framing is enough to warrant revision before the page is treated as fully settled.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}