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 · Shelbit Exchange
- Sequence
- #2
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 443518103
- Off-chain at
- 2026-08-25T22:49:34.028Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- E2HJY6R5XDGf5PMtYUTJZnKraTvHSZhWpfHa2yPabkS1
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1506 chars)
{"actor":"reviewer","decided_at":"2026-08-25T22:49:33.943Z","decision":"review","investigation_id":"4b1608f0-b1d0-41e6-893f-f4656b6af442","new_score":2,"page_slug":"shelbit-exchange","prev_score":2,"reason":"The page's central factual architecture — the August 7, 2026 OFAC designation of Shelbit and Kayvanpour, the July 24, 2026 VARA fines, the $4 billion Reuters-reported flow figure, and the named individuals' convictions and denials — is well-supported by primary regulatory sources (Treasury, OFAC, VARA) and multiple independent news outlets, and the OFAC designation is confirmed still in force as of the review date with no indication of delisting. Two specific defects were identified: an incorrect claim that Shelbit's designation falls under both E.O. 13224 and E.O. 13902 (OFAC's own listing shows E.O. 13902 applies only to the separately designated Aban Tether network, not Shelbit), and an internal, self-contradictory statement about the timing of $540 million in Binance-bound flows. The page also selectively omits Reuters' own caveat that it could not confirm direct IRGC control, and does not reference TRM Labs' larger, more current $6.3 billion total-flow figure or its underlying on-chain research. No unsourced claim about secondary-sanctions screening obligations extending to counterparties of designated parties was found on this page.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}