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
review · Opacus
- Sequence
- #3
- Score
- 23 → 23 (0)
- Cluster
- mainnet-beta
- Slot
- 464245381
- Off-chain at
- 2026-11-01T21:35:32.448Z
- Anchored at
- 2026-11-01T21:36:00.000Z
- Block time
- 2026-11-01T21:36:00.000Z
Independent verification
- 1. Database (off-chain)
- HnZbMbkPMbhjHgTBP7oN2pjLuGSyi4usUYGemGS8Ncgq
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1175 chars)
{"actor":"reviewer","artifact_identity":"5a612a1e43e9550195a7f0b809c709e4","decided_at":"2026-11-01T21:35:32.356Z","decision":"review","disputed_pct":0.3333,"findings_hash":"E6bquQYL6WeNR2tjjWJ7hLyV8jfZy5BzWWjQQVwPD1sQ","investigation_id":"db70d8e6-b464-41ed-81c3-e2e9c02d75b8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":23,"page_content_hash":"bef381ff8e9968a746d0db419ba5c06576717c6c341845935c2ada94e9f8f617","page_slug":"opacus","prev_score":23,"reason":"The page is largely accurate about the library (dates, repo stats, license, PyPI release) and cautiously declines to assert any token exists. One factual error: CVE-2020-28477 affects versions before 0.12.0 and is rated High, not low-severity and not tracked against 0.12.0. The final timeline entry is internal process commentary that cannot be verified externally.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}