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
- #7
- Score
- 30 → 30 (0)
- Cluster
- mainnet-beta
- Slot
- 462183712
- Off-chain at
- 2026-10-27T19:09:07.719Z
- Anchored at
- 2026-10-27T19:09:34.000Z
- Block time
- 2026-10-27T19:09:34.000Z
Independent verification
- 1. Database (off-chain)
- CQ4uYm5qhrHY2sqiia3UxmZsYwxM78vvWfLbFJVFXBqd
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1468 chars)
{"actor":"reviewer","artifact_identity":"18f3821ebc35e8c6020162f09d26277a","blocked_count":2,"decided_at":"2026-10-27T19:09:07.547Z","decision":"review","disputed_pct":0.1429,"findings_hash":"F36KA8kg1xL6tPirH5w3j8isci9z2YTHRgjgsxnu72Kq","investigation_id":"4ae6a329-6762-4493-a983-9752d79f1fc0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":30,"omissions":{"material":2,"total":3},"page_content_hash":"4fe8a227d38acb7cb2d3e22cbf68be6076722fab8596c37e017d4430ee6bdad8","page_slug":"bitmex-exchange-closure-september-2026","prev_score":30,"reason":"The core facts check out against the official BitMEX notice, CoinDesk and crypto.news: announcement date, closure time, reduce-only date, fee structure and the class action figures. Problems are an overstated 'buyers rejected $1B' claim, a speculative advance-knowledge inference, and merge residue that refers to other pages. The larger issue is that the page is written as if the Sept 23 closure were still ahead, and it omits the staged wind-down and post-closure withdrawal mechanics. Many regulatory and market figures were not independently fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":7,"subject_status":"shut_down","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}