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
- Sequence
- #2
- Score
- 50 → 67 (+17)
- Cluster
- mainnet-beta
- Slot
- 455367113
- Off-chain at
- 2026-10-10T18:47:16.781Z
- Anchored at
- 2026-10-10T19:15:43.323Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EkqBfQp7QPriCEw4tKzruqKmnk8BbDGUmhoKp1ruwN33
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (569 chars)
{"actor":"system","decided_at":"2026-10-10T18:47:16.687Z","decision":"rescore","investigation_id":"c3924f21-aaa7-4939-8ff1-19f9a2ba75cd","new_score":67,"page_slug":"7uh2uvf8hpqjlduwr7gffjwjfymvcjvlvvc7j9tdcuvd","prev_score":50,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 50 → 67. Problems weighed by who is responsible: problems around the subject, caused by others −0.6.","score_delta":17,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}