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 · Envar AI
- Sequence
- #3
- Score
- 40 → 40 (0)
- Cluster
- mainnet-beta
- Slot
- 464245079
- Off-chain at
- 2026-11-01T21:34:29.575Z
- Anchored at
- 2026-11-01T21:34:55.000Z
- Block time
- 2026-11-01T21:34:55.000Z
Independent verification
- 1. Database (off-chain)
- 7TLSfsT6mgVPS45gZFLJj9DXYdafnGWpAytuPNDWQNnv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1145 chars)
{"actor":"reviewer","artifact_identity":"6d78fd71da05868746ad62d06fad95a2","decided_at":"2026-11-01T21:34:29.452Z","decision":"review","disputed_pct":0.5,"findings_hash":"5LJbZ2rMyRCRffjwY85tjijF7htq6muUuub9oY3PZjWs","investigation_id":"c3ce9698-08dd-4582-990f-87da7c0afee5","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":40,"page_content_hash":"4f1545b70a2049875d59b1967a5e5f04e561a7f7b02fc4249157f71528f43ddf","page_slug":"envar-ai","prev_score":40,"reason":"The page makes only negative, appropriately hedged statements: the homepage is near-empty and no independent coverage was found. Both reproduce on independent fetch and search. The token-absence claim was not checked on-chain, and the 'requester' reference cannot be verified. No factual errors found; the page is thin but honest about it.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}