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
- 443519532
- Off-chain at
- 2026-08-26T06:07:49.654Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 697xHL7wPh2hpwLGDy2iVZBM6ZLw8QLzorow7RhNKXeE
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1086 chars)
{"actor":"reviewer","decided_at":"2026-08-26T06:07:49.295Z","decision":"review","investigation_id":"dd0db8d8-86d7-4988-95a1-b35ea4d655cf","new_score":0,"page_slug":"north-korea-lazarus-group-h1-2026-systematic-crypto-theft-campaign","prev_score":0,"reason":"The large majority of claims -- including the headline TRM Labs H1 2026 figures, the Drift and KelpDAO exploit mechanics, OFAC sanctions details, and IT-worker infiltration statistics -- are confirmed against primary or well-corroborated secondary sources. However, the page contains a clear subgroup-naming error (equating 'TraderTraitor' with 'UNC4736' when Mandiant tracks TraderTraitor as UNC4899, a distinct cluster from UNC4736/Golden Chollima), a disputed year-by-year historical theft table whose 2024 figures conflict sharply with widely corroborated reporting, and a DeFi TVL/outflow figure that both conflicts with independent reporting and fails its own internal arithmetic.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}