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_approve · Cryptsy
- Sequence
- #3
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 425023532
- Off-chain at
- 2026-06-08T02:49:35.807Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- ATB8gREPha244AUWgAv3DqZLtrJxuBg2NRkvw8ybkxzz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1228 chars)
{"actor":"judge","decided_at":"2026-06-08T02:49:35.610Z","decision":"review_approve","investigation_id":"dd92c0c7-2b73-4efa-971d-710c22c5f467","new_score":2,"page_slug":"cryptsy","prev_score":2,"reason":"The reviewer found 0 disputed claims across 32 total findings (disputed_pct = 0.0%), placing this page in the approve band. The four partially_supported findings (claim_findings[5], claim_findings[9], claim_findings[34], claim_findings[35]) concern peripheral details — a $1.00 discrepancy in a reported LTC starting price, a timeline date (July 2) that appears to be a minor sequencing error preceding the confirmed July 29 theft, and a January 1 placeholder for an August 2019 indictment filing. None of these affect the core allegations, which are confirmed by multiple Tier 1 sources including DOJ filings, CoinDesk, SecurityWeek, and Elliptic. The reviewer confidence of 0.85 supports a firm approval. One high-priority coverage gap exists (post-2022 on-chain fund movement), which is noted for editorial expansion but does not affect the factual integrity of the current page.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}