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 · Blazar Token / John A. DeSalvo
- Sequence
- #2
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 443516438
- Off-chain at
- 2026-08-25T19:21:27.592Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- H6Sri1AmkXcgjqNpR5BguKKoANJecTGWqoPyHaVmUbjJ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (968 chars)
{"actor":"reviewer","decided_at":"2026-08-25T19:21:27.438Z","decision":"review","investigation_id":"0a172da3-8249-44fd-a8fa-21542a823994","new_score":2,"page_slug":"blazar-token-john-a-desalvo","prev_score":2,"reason":"The page's core factual narrative (scheme mechanics, amounts, criminal charges, guilty plea, and 2026 civil settlement terms) is well-supported by primary and convergent secondary sources. Two defects were found: a citation misattribution (the 2026 settlement is credited to SEC Litigation Release LR-25814, which actually documents the 2023 charging complaint; the correct release is LR-26599) and a geographic error (Linwood, NJ is labeled as Cape May County when it is in Atlantic County). Several DOJ primary sources were bot-blocked (403) and had to be corroborated via independent secondary reporting.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}