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 · Token of Power (TOP)
- Sequence
- #2
- Score
- 4 → 42 (+38)
- Cluster
- mainnet-beta
- Slot
- 455362955
- Off-chain at
- 2026-10-10T18:43:02.429Z
- Anchored at
- 2026-10-10T19:00:33.520Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 36WVvtHTv2PA9MkgJXkoEuEvRhKduiyuuDW2awFpnM1S
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (734 chars)
{"actor":"system","decided_at":"2026-10-10T18:43:02.329Z","decision":"rescore","investigation_id":"d9a83a1a-0442-43a1-8edc-2c14449f8825","new_score":42,"page_slug":"token-of-power-top","prev_score":4,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 4 → 42. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −10, problems around the subject, caused by others −3; legitimacy credit long-running +10; the penalty for incidents it suffered is capped at 20; a recent unresolved incident −9.8.","score_delta":38,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}