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
- #4
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 457583762
- Off-chain at
- 2026-10-16T09:15:16.571Z
- Anchored at
- 2026-10-16T09:15:19.782Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6p2NLWWkGcrY4BNWHaH29UzVmN2imGEmwz8wSxbjKw9x
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1685 chars)
{"actor":"reviewer","artifact_identity":"3c59fa56f7599ba78e70ee4090d65d77","decided_at":"2026-10-16T09:15:16.355Z","decision":"review","disputed_pct":0.2143,"findings_hash":"Dz1iCFjXZCgpnHcxbuSFF5EDqTFnCqTRwbCtu4QLwXkm","investigation_id":"e9d60bed-425b-4fc6-b70b-15d7d8e9722d","mode":"findings_only","new_score":0,"page_content_hash":"e4cee30b245f32c2d6f7cd6384514015674f196a63ccfdaa92dff716dd7bc2d7","page_slug":"lazarus-group-mach-o-man-macos-campaign-2026","prev_score":0,"reason":"The page is largely well-sourced and its central technical claims (malware stages, hashes, C2 ports/domains, persistence mechanism, OPSEC failures) are confirmed verbatim against the live primary source (ANY.RUN). The KelpDAO, Drift Protocol, Bybit, and TRM/Chainalysis macro-statistics are also independently corroborated. However, the page contains one clear, repeated factual error: it states OFAC designated Lazarus Group on the SDN list on April 14, 2022, when the group was actually designated on September 13, 2019 — the 2022 action (which the page's own cited source shows is dated April 22, not April 14) only added three Ethereum addresses to an existing entry. This error appears in both the Attribution section and the timeline and should be corrected in both places. A secondary, softer issue is that specific sub-unit attribution (TraderTraitor for the Drift exploit) is contested in some reporting, and a few figures ($625M Ronin, 76% stat) lack inline sourcing. No community evidence was submitted for this page, so evidence_review is empty.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}