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
- 443519348
- Off-chain at
- 2026-08-26T06:05:11.111Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7GCYtySTrpyzwtAskXEZrQxViydUQJYyviuycSadb4Pw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1169 chars)
{"actor":"reviewer","decided_at":"2026-08-26T06:05:10.882Z","decision":"review","investigation_id":"e9d60bed-425b-4fc6-b70b-15d7d8e9722d","new_score":0,"page_slug":"lazarus-group-mach-o-man-macos-campaign-2026","prev_score":0,"reason":"The core technical disclosure (malware architecture, hashes, network indicators, ClickFix delivery, OPSEC failures) is confirmed in exact detail against the primary ANY.RUN research and corroborating outlets, and the broad Lazarus attribution and financial-loss figures for the concurrent Drift/KelpDAO exploits are independently corroborated. The page contains one clear factual error (misdating the original Lazarus OFAC designation to 2022 instead of 2019, contradicted by its own cited 2019 source), one instance of subgroup attribution (TraderTraitor for Drift Protocol) that outruns what higher-credibility sources say, and one unsupported inference presented as fact regarding cross-adoption of the malware by other criminal groups, which the page's own cited source does not support.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}