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
- 457977830
- Off-chain at
- 2026-10-17T08:55:30.250Z
- Anchored at
- 2026-10-17T08:55:45.068Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CSYqLGxt2BiQVzx8E3FJmuChjPdqZu2H6SHarpM9UJzK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2007 chars)
{"actor":"reviewer","artifact_identity":"1e92e68275d9bdfffd49b8fb8a5375bd","decided_at":"2026-10-17T08:55:30.063Z","decision":"review","disputed_pct":0.2759,"findings_hash":"3XbyB5YP83i3RbrJmE3rTEJVbaTdvYZ125GBuDhd3q2Q","investigation_id":"013a0a09-ae20-4647-a35a-080a0a5e1fd1","mode":"findings_only","new_score":0,"page_content_hash":"feff4a8376b7381239cfbbe05b4de200ca3557cc2c32c12794a85e9d60582190","page_slug":"mach-o-man-lazarus-chollima-macos-malware","prev_score":0,"reason":"The page's technical description of the Mach-O Man malware kit (four-stage chain, IOCs, ClickFix delivery) is strongly and precisely supported by the primary ANY.RUN report and cross-corroborated by secondary outlets. The Drift Protocol and KelpDAO sections are well sourced on their headline figures, dates (apart from one timeline error), and attribution, though the Drift section overstates an unconfirmed infection vector (VS Code/TestFlight) as established fact while omitting the durable-nonce multisig compromise that primary sources identify as the actual drain mechanism. Two clear defects stand out: the page's Tornado Cash sanctions claim (May 6, 2022) actually describes OFAC's Blender.io designation per its own cited press release — a factual swap repeated in four places (prose, two source labels, and the timeline) — and a CyberScoop-cited passage misattributes a 'professional financial operations' laundering-pace quote to Bybit CEO Ben Zhou when the cited article's laundering-pace commentary belongs to TRM Labs' Ari Redbord, alongside an 'institutional speed and scale' characterization not found in the source. The Arbitrum freeze timeline entry is dated two days later (April 22) than every source consulted, including the page's own cited article, which places it on April 20. Community evidence was not a factor: accepted_submissions is empty for this page.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}