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 · Drift Protocol
- Sequence
- #8
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 466715479
- Off-chain at
- 2026-11-08T00:34:34.457Z
- Anchored at
- 2026-11-08T00:34:58.000Z
- Block time
- 2026-11-08T00:34:58.000Z
Independent verification
- 1. Database (off-chain)
- BwBfdk6UguwjHCkZ6vcRS2gtyERcajtoZQaBz2RwvKJs
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1181 chars)
{"actor":"reviewer","artifact_identity":"841017dd229a11f96d4316213977ae1a","decided_at":"2026-11-08T00:34:34.347Z","decision":"review","disputed_pct":0.2,"findings_hash":"XMRGip1QWpxrnBGgYV7SMiw987S7V9HL3A5dMQCM7Na","investigation_id":"3d2cc7b8-95f7-498d-b8b1-64ac61450e87","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":52,"page_content_hash":"d473589179bfc482c39cf58a3c1a35db19a9bf1687bfc64383c177bd4197aa8b","page_slug":"drift","prev_score":52,"reason":"A spot-check of the highest-risk claims (recovery-plan figures, attack dates, TRM timeline) matched primary sources. The page hedges unverified items well. One minor overstatement: the summary says Velocity has relaunched, but reporting shows only a private beta. The Class action, contagion and 2022 incident sections were not independently verified in this time-boxed review.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":8,"subject_status":"rebranded","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}