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 · SushiSwap
- Sequence
- #2
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 426276968
- Off-chain at
- 2026-06-13T21:05:07.320Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- FRAWZEdca3DMPD8VRcZuwBUSfihQ7EUHCdXWABFvvoNg
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1148 chars)
{"actor":"reviewer","decided_at":"2026-06-13T21:05:07.185Z","decision":"review","investigation_id":"df79decd-dab0-46e7-a234-b7db05d89ce2","new_score":32,"page_slug":"sushiswap","prev_score":32,"reason":"The SushiSwap investigation page is substantially accurate with no outright disputed or fabricated claims. Eight of 26 claims are partially supported — primarily due to minor date inaccuracies (launch date listed as August 1 vs confirmed August 28; Grey appointment listed as October 11 vs confirmed October 3), dollar figure ranges at the high end of reported values ($42.5M treasury), and the price collapse percentage (~90% vs more commonly cited 73%). The North Korean IT worker claim is accurately labeled as allegation but rests on a single expert source. No cited URLs appear dead based on search verification, though several returned 403 during direct fetch attempts. Major coverage gaps include the absence of on-chain transaction citations and no tracking of the SEC subpoena's current status.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}