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
- 3 → 3 (0)
- Cluster
- mainnet-beta
- Slot
- 465095204
- Off-chain at
- 2026-11-04T00:09:51.425Z
- Anchored at
- 2026-11-04T00:10:19.000Z
- Block time
- 2026-11-04T00:10:19.000Z
Independent verification
- 1. Database (off-chain)
- 7hKiytAuCKdjhokbJhwFahfbhtiGge3JbaEKpofXHkZL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1306 chars)
{"actor":"reviewer","artifact_identity":"e48c32d802e59e0b4b1218508aade627","decided_at":"2026-11-04T00:09:51.357Z","decision":"review","disputed_pct":0.375,"findings_hash":"8RqTyZ6fB62661263fpFxwuMzoVvtNw7dPgZ5v2QngfF","investigation_id":"8655eeea-1d2f-4d0d-b554-e117ba889570","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":3,"omissions":{"material":0,"total":1},"page_content_hash":"f158ee6ad11bf9ac62e3621574f9a67df4f39f772a9c1f0feb91499f740cf5b2","page_slug":"leo-platform-npm-supply-chain-attack-june-2026","prev_score":3,"reason":"Core incident facts (20 packages, 23:04:55 UTC, 13,600 weekly downloads, czirker account, Phantom Gyp, orphan Dependabot branches) match StepSecurity and SafeDep. The named individual attached to czirker, the liuende501/236-repo claim, the killswitch/C2 details and the upgrade-after-compromise advice are not supported by the cited sources. TeamPCP attribution was not fully verified. Many secondary claims were not checked.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":2,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}