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
rescore · Cryptsy
- Sequence
- #4
- Score
- 2 → 0 (-2)
- Cluster
- mainnet-beta
- Slot
- 455371249
- Off-chain at
- 2026-10-10T18:51:01.418Z
- Anchored at
- 2026-10-10T19:30:42.772Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4aHeDNmccpr4oDAk3rmkAuMc7Pu9JLGjkYRV1WkK2wkQ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (513 chars)
{"actor":"system","decided_at":"2026-10-10T18:51:01.313Z","decision":"rescore","investigation_id":"dd92c0c7-2b73-4efa-971d-710c22c5f467","new_score":0,"page_slug":"cryptsy","prev_score":2,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 2 → 0. The page establishes that the subject is itself a scheme, so the score is 0.","score_delta":-2,"score_model":"v2","sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}