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
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443505715
- Off-chain at
- 2026-08-08T03:33:59.164Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EJq1RvYAgLLDxoXsysqZF4GgAWJwha3FLJF1Bo9KYmyq
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1130 chars)
{"actor":"reviewer","decided_at":"2026-08-08T03:33:59.044Z","decision":"review","investigation_id":"9b3e7fc9-d98c-4d79-8b5d-852d1bd6f02b","new_score":0,"page_slug":"chaindrop-mini-shai-hulud-npm-supply-chain-worm-august-2026","prev_score":0,"reason":"The investigation is well-sourced, technically accurate, and substantiated by credible primary sources across 23 atomic claims. The main weaknesses are: NHS CC-4781 is contextually misplaced (issued May 2026 for the TanStack wave, not ChainDrop), the @ornikar package count (42 vs JFrog's 60+) is internally inconsistent, SANDWORM_MODE is dated March 2026 by the cited Tenable FAQ but was disclosed in February 2026 by independent sources, and a handful of granular technical IOCs (75 RPC endpoints, HashiCorp '17 regions', specific commit author name, branch name pattern) appear in only one primary source and could not be cross-validated. No major claims were found to be outright fabricated or contradicted by a more credible source.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}