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 · Cypher Protocol
- Sequence
- #3
- Score
- 35 → 35 (0)
- Cluster
- mainnet-beta
- Slot
- 466742378
- Off-chain at
- 2026-11-08T02:10:50.596Z
- Anchored at
- 2026-11-08T02:11:00.000Z
- Block time
- 2026-11-08T02:11:00.000Z
Independent verification
- 1. Database (off-chain)
- 6AQFmHax2CLU9C3XUsj7FK4ymtEMhXEfSkprMe5EyCmK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1256 chars)
{"actor":"reviewer","artifact_identity":"6537dd1c67892c94905a43c76783d5cb","decided_at":"2026-11-08T02:10:50.542Z","decision":"review","disputed_pct":0.4286,"findings_hash":"8gU2Lhzk9i9kPGox7CXK1EtZX1Qt3U9WgEGa7rLijEXb","investigation_id":"9cbcb3e6-020e-41d7-9222-e8dcd77d99cf","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":35,"omissions":{"material":0,"total":1},"page_content_hash":"ef2545962932f3742bf38acb4bbcd83be2c4e2970de1b377d4434267061d2e7b","page_slug":"cypher","prev_score":35,"reason":"The core narrative (August 2023 exploit, December 2023 to May 2024 insider theft, Hoak's confession, Barrett's law-enforcement referral) is supported. Three unsupported or overstated points: the ZachXBT 'high-risk' flag, the inference that contracts were unaudited attributed to Halborn, and the Hoak denial of exploit involvement. Timeline entries have empty source fields. Only a sample of sources was checked.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}