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 · CrossCurve
- Sequence
- #3
- Score
- 64 → 67 (+3)
- Cluster
- mainnet-beta
- Slot
- 464266870
- Off-chain at
- 2026-11-01T22:52:40.839Z
- Anchored at
- 2026-11-01T22:52:48.000Z
- Block time
- 2026-11-01T22:52:48.000Z
Independent verification
- 1. Database (off-chain)
- ACfyQ6WmZH9PmsibXPUsYRD65xTvaLDfaA4P6qrhjhzA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (743 chars)
{"actor":"system","decided_at":"2026-11-01T22:52:39.931Z","decision":"rescore","investigation_id":"c18c86d7-2fb4-4de4-9c16-385555f1a0cb","new_score":67,"page_slug":"crosscurve","prev_score":64,"reason":"Re-read and rescored after the page was re-researched (2026-11-01). Rescored under Scoring v2, the published formula (avoid.net/scoring): 64 → 67. Problems weighed by who is responsible: incidents the subject suffered −20, problems around the subject, caused by others −3.3; legitimacy credit long-running +10, regulated +5; the penalty for incidents it suffered is capped at 20.","score_delta":3,"score_model":"v2","sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}