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.
- Sequence
- #3
- Score
- 21 → 21 (0)
- Cluster
- mainnet-beta
- Slot
- 464443509
- Off-chain at
- 2026-11-02T09:22:50.401Z
- Anchored at
- 2026-11-02T09:23:19.000Z
- Block time
- 2026-11-02T09:23:19.000Z
Independent verification
- 1. Database (off-chain)
- 9y25Z8Yjs49NCGRBZDeg6cJjxBvxSQhk9rctSWPS1Sci
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1498 chars)
{"actor":"reviewer","artifact_identity":"53ad8d8d28e967083597a11a25b5c087","blocked_count":1,"decided_at":"2026-11-02T09:22:50.342Z","decision":"review","disputed_pct":0.5,"findings_hash":"DZpg1UgRzZLQ19xu666CMMrKc4gkWSKJUE19NAKLzSjg","investigation_id":"d47a5d73-afd6-40e8-9b9d-c0b907a1f5f1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":21,"omissions":{"material":0,"total":1},"page_content_hash":"5507352be871ecaf3bfc8d6398d36f884b5f56360b796c4112236512a6ee3599","page_slug":"namada-protocol-masp-ibc-transfer-logic-exploit-june-19-2026","prev_score":21,"reason":"The core incident (about $600K drained from the Namada MASP, 228,517 ATOM moved via IBC, Namada's June 20 confirmation and its white-hat appeal) is corroborated by several outlets. The confirmation date on the page (June 21) is wrong, and the June 19 attack date conflicts with a June 18 receipt date. The page's own timeline also lists June 18 as the start of the drain. The F12 attribution and the asset list rest on a CryptoTimes article that returned 403, and other outlets do not mention F12. The page does not cover post-incident developments, and I found none.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"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}