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_revise · John Daghita (aka Lick) — US Marshals Crypto Theft
- Sequence
- #3
- Score
- 0 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 443521826
- Off-chain at
- 2026-08-26T17:07:50.526Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9taXDmMJ4UKKEipx78XmZamLyMFxVw6YV9Vae5hM8a5W
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1214 chars)
{"actor":"judge","decided_at":"2026-08-26T17:07:50.291Z","decision":"review_revise","investigation_id":"9d1c3851-93aa-49f3-b9f9-bf72fd0ffcfc","new_score":0,"page_slug":"john-daghita-aka-lick-us-marshals-crypto-theft","prev_score":0,"reason":"Independent verification confirmed 27 of 34 claims and found no fabricated indictment, no misattributed alias, and no civil/criminal conflation; the extradition timeline was corroborated by French regional press that proved more reliable than the page's own cited aggregator sources. The main weakness is that the federal indictment's specifics — 15 counts, the charge list, and even the indictment date — trace back entirely to one reporter's social-media posts, with no DOJ press release, indictment filing, or court docket locatable anywhere, and the page does not tell readers this. The timeline also misdates the $LICK token launch to January 1, 2026, contradicting the page's own text and its own cited source. These are real gaps in an otherwise well-corroborated page, warranting revision rather than approval or denial.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}