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
- 464267739
- Off-chain at
- 2026-11-01T22:55:36.294Z
- Anchored at
- 2026-11-01T22:55:55.000Z
- Block time
- 2026-11-01T22:55:55.000Z
Independent verification
- 1. Database (off-chain)
- HR28qwBH3Jaf2zncbRVQJghgbitok7RdrBZUbLzbQzAu
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1367 chars)
{"actor":"reviewer","artifact_identity":"ce57b7378bd3fd593e0c893b06359c45","decided_at":"2026-11-01T22:55:36.230Z","decision":"review","disputed_pct":0.1818,"findings_hash":"6DUE435bpLURLk4ANnTGJSz1A74vuAakAAuqarjg8AJ7","investigation_id":"6088bbf8-f446-4353-956a-09ef5f824fb9","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":2,"omissions":{"material":0,"total":1},"page_content_hash":"8287c7c069fb2007b425a985e539166cdd38216572eb186ead74c55aaf135767","page_slug":"socket-security-malicious-browser-extension-campaign-august-2026","prev_score":2,"reason":"The page is well sourced and the core figures (19 extensions, 18/1 split, 14/5 split, 80,000 users, Feb 2024, 16 modules, dates) match Socket's report and secondary coverage. One attribution is wrong: the page credits The Hacker News with reporting Google's removal of the Chrome version, but THN's article does not state that; CyberInsider does. The version 5.8 detail was not found in THN. The page lags on later reporting that both stores removed the extensions.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}