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 · Nina/Mo
- Sequence
- #2
- Score
- 83 → 83 (0)
- Cluster
- mainnet-beta
- Slot
- 423940086
- Off-chain at
- 2026-06-03T02:53:59.240Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AwFAEZMiCcY77VAS26AQSpk2PTYHSKqRFtMUS3m8WAN9
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1003 chars)
{"actor":"reviewer","decided_at":"2026-06-03T02:53:59.156Z","decision":"review","investigation_id":"6e0d7808-17b4-4d32-be8a-b8698920809c","new_score":83,"page_slug":"ninamo","prev_score":83,"reason":"The page contains one factual date error (theft date stated as April 27 vs the confirmed April 28, 2025) and several source mischaracterizations where informational pages are described as searchable complaint databases. The core identification of Nina/Mo and W0rk as suspects named by ZachXBT is supported by multiple independent corroborating sources. The most significant finding is a structural incoherence: the summary and three sections treat 'Ninamo' as an unverifiable crypto entity with no presence, while Section 1 concerns a real named suspect in one of the largest recorded Bitcoin thefts. The page requires restructuring to match its actual subject.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}