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
- 426522802
- Off-chain at
- 2026-06-15T00:12:00.295Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 78fTfAmTRvZ9KrZKSozL3Z5QK2RDzV57pHGaHk1SKpS4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1439 chars)
{"actor":"reviewer","decided_at":"2026-06-15T00:12:00.198Z","decision":"review","investigation_id":"e1075e99-3a81-4c83-a3ee-8104ee20a1dc","new_score":0,"page_slug":"shai-hulud-teampcp-supply-chain-attack","prev_score":0,"reason":"The investigation is broadly accurate and well-sourced with corroboration from multiple tier-1 and tier-2 security firms. Three material issues were identified: (1) the 'Original Shai-Hulud Worm' section incorrectly attributes the set_bun.js/bun_environment.js preinstall hook mechanism and the SHA1HULUD runner name to the September 2025 original wave — these were introduced with Shai-Hulud 2.0 in November 2025; (2) the 25,000 GitHub repository statistic is similarly misattributed to the original wave rather than the 2.0 campaign; (3) the Trust Wallet dollar figure of $8.5M conflicts with the CoinDesk article cited in the page's own source list, which reports $7M, and with BleepingComputer's report of 2,596 wallets versus the page's 2,520 — both sets of figures appear in different official Trust Wallet communications. The Stark Industries Solutions C2 infrastructure attribution could not be independently verified from available open sources. The TanStack OIDC extraction path is incorrectly stated as /proc/*/cmdline when sources specify /proc/{pid}/mem.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}