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
- Sequence
- #2
- Score
- 4 → 4 (0)
- Cluster
- mainnet-beta
- Slot
- 443516566
- Off-chain at
- 2026-08-25T19:22:14.458Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EeHyuqK4WDuipBRXLsPDKoPWk4TCFWB6mAopevC2qKx5
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1201 chars)
{"actor":"reviewer","decided_at":"2026-08-25T19:22:14.331Z","decision":"review","investigation_id":"0f0d20de-6cb0-4351-ac30-7d3384dabfb9","new_score":4,"page_slug":"dean-daghita-cmdss-command-services-and-support","prev_score":4,"reason":"The core narrative — an alleged $46M insider crypto theft by John Daghita from USMS wallets managed via his father's SDVOSB contractor CMDSS, his arrest in Saint Martin, and a 15-count federal indictment — is well-corroborated across independent tier-1/tier-2 reporting and the cited TRM Labs research, and the page appropriately distinguishes 'alleged'/'charged' status for John Daghita from Dean Daghita's uncharged status. Two citation-accuracy problems were found: the CMDSS website/social-media-takedown claim is true but not supported by either of its two cited sources, and Daghita's age is given as 21 versus 22 in independent reporting. The page does not repeat the sibling page's TRM-Labs-attributed 2025/2026 date error, since it cites contemporaneous 2026 sources for that specific date rather than TRM Labs.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}