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
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 425239808
- Off-chain at
- 2026-06-09T02:45:07.580Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GvujERHteBSvsriUEJQEaMToXTT7VDsSmmGviisDEumh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1338 chars)
{"actor":"reviewer","decided_at":"2026-06-09T02:45:07.375Z","decision":"review","investigation_id":"39fa81fa-065d-4dbd-9013-342ab1bedc38","new_score":0,"page_slug":"faris-ali-uk-crypto-home-invasion-ring","prev_score":0,"reason":"The investigation's core narrative — robbery date and location, perpetrator names and ages, charges, individual sentence lengths, weapon type, arrest timeline, and crypto recovery — is well-supported across multiple independent outlets. The most significant factual error is a chronological impossibility: ZachXBT's post-sentencing statement is dated June 2025 in the timeline despite sentencing occurring November 7, 2025 (likely a year transcription error, given the tweet ID is consistent with June 2026). A second material error attributes a US DOJ case to a Metropolitan Police UK operation when citing the Hacker News thread about twelve defendants. The TRM Labs citation for database compromise does not support the specific claim made. The ZachXBT eight-to-nine-figures claim omits its stated context (Coinbase users specifically). The weapon description inconsistency across sources is acknowledged implicitly by the court charge of 'possession of a knife.'","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}