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_approve · Typus Perp
- Sequence
- #4
- Score
- 63 → 63 (0)
- Cluster
- mainnet-beta
- Slot
- 464343897
- Off-chain at
- 2026-11-02T03:27:16.074Z
- Anchored at
- 2026-11-02T03:27:46.000Z
- Block time
- 2026-11-02T03:27:46.000Z
Independent verification
- 1. Database (off-chain)
- 4789boatn8LPazu6tz8zk57VV6wZwv1WjRYSTRoFYK8M
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1417 chars)
{"actor":"judge","artifact_identity":"217a88a8ebcda961be404a61d288902d","band_override":null,"blocked_count":2,"decided_at":"2026-11-02T03:27:15.871Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"c904afdd-65c3-4db7-98bb-c96d6f81e74b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":63,"page_slug":"typus-perp","prev_score":63,"reason":"Of six claims checked, four were confirmed against readable sources and none were disputed (claim_findings[0], [1], [2], [5]), including the $3.44 million exploit, the Nov 13, 2024 deployment and the audit exclusion. The other two (claim_findings[3], [4]) could not be read because the sources blocked the reviewer, so they are excluded from the disputed rate, which comes to 0%. That is a third of the claims left unchecked, which limits how far this review can be relied on, but it is not a defect of the page. The page's May 2026 TVL figure is dated (the reviewer's snippet suggests about $6K by October 2026), but the reviewer rated this omission minor and found no shutdown or status contradiction. It is worth a refresh, not a penalty.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":4,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}