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.
- Sequence
- #2
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 425406114
- Off-chain at
- 2026-06-09T21:07:26.742Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9to4VitfoBgtWJBAoDijRhT7zMkPvfnhf4ytpxcyZvkb
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1197 chars)
{"actor":"reviewer","decided_at":"2026-06-09T21:07:26.619Z","decision":"review","investigation_id":"dbd7d8a8-5677-4df6-93ab-f3b0bbbdca65","new_score":2,"page_slug":"lazarus-group-graphalgo-fake-recruiter-npm-pypi-campaign","prev_score":2,"reason":"The page is substantially well-sourced, with the vast majority of claims confirmed by the primary ReversingLabs research and corroborated by multiple secondary sources. The three unverifiable claims are specific granular details (typosquatting account name, a weekly download snapshot metric, and one precise package wave date) that could not be confirmed from available source summaries but are not contradicted by any credible source. The four partially-supported claims involve minor discrepancies: the LLC is legally named 'Blocmerce' not 'Blockmerce', the August 2025 LLC date is month-level not day-level, the $5B theft figure is an industry approximation without a single citable source, and the public disclosure date of February 15 is contested by at least one secondary source showing February 12.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}