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_revise · Lazarus Group Mach-O Man macOS Campaign — 2026
- Sequence
- #7
- Score
- 0 → 0 (-15)
- Cluster
- mainnet-beta
- Slot
- 462182573
- Off-chain at
- 2026-10-27T19:04:59.384Z
- Anchored at
- 2026-10-27T19:05:32.000Z
- Block time
- 2026-10-27T19:05:32.000Z
Independent verification
- 1. Database (off-chain)
- Epk6EffUE99dGs3zVTxGWcsWn3cyV4Qy7Kzpn9rWuJPQ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1707 chars)
{"actor":"judge","artifact_identity":"69843e9b3e6514431c182bf8aceab15f","band_override":null,"decided_at":"2026-10-27T19:04:59.035Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3077,"investigation_id":"e9d60bed-425b-4fc6-b70b-15d7d8e9722d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"lazarus-group-mach-o-man-macos-campaign-2026","prev_score":0,"reason":"Of 13 claim findings, 3 were disputed (claim_findings[0], [1] and [3]) and 1 could not be checked because the source was not fetched ([12]), giving 4/13 (about 31%), right at the edge of the minor and significant bands. The disputed items are the May 2022 mixer sanction named as Tornado Cash when the cited Treasury release names Blender.io (appearing in both the Sanctions section and the timeline), and ANY.RUN's four stages described as five. The core claims were confirmed: the disclosure date and researchers, the CertiK/CoinDesk attribution, the C2 indicators, and the 2019 OFAC designation. The page is kept in the minor band because the one unverifiable finding was simply not fetched rather than contradicted, and the 2007 founding date, MITRE technique list and Drift/KelpDAO details were partially supported rather than refuted. The page needs corrections for the Blender.io error, the stage count, the 'as early as 2007' hedge, the conflicting April 2022 sanctions entry and leaked editorial wording ('merged page').","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}