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_revise · AutoShark Finance
- Sequence
- #3
- Score
- 14 → 4 (-10)
- Cluster
- mainnet-beta
- Slot
- 465094772
- Off-chain at
- 2026-11-04T00:08:36.036Z
- Anchored at
- 2026-11-04T00:08:47.000Z
- Block time
- 2026-11-04T00:08:47.000Z
Independent verification
- 1. Database (off-chain)
- DmKEKNdgv8UJV4zb95erw6RaaaJ4cFrxwG52cuUGAxn6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1413 chars)
{"actor":"judge","artifact_identity":"ab643d2553f2ae785b551d8f67e3454f","band_override":null,"blocked_count":2,"decided_at":"2026-11-04T00:08:35.775Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"5f76d9b3-9cd6-4f9e-a525-a9df2295e596","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":4,"page_slug":"autoshark","prev_score":14,"reason":"Of 7 claims reviewed, 2 could not be checked because the source (Medium) blocked the reviewer, so they are excluded; of the remaining 5, 1 was unverifiable (20%). The summary's ZachXBT attribution (claim_findings[0]) has no supporting source and the page itself concedes this. The May 2021 profit figure (claim_findings[1]) differs from Rekt's reported figure of about $745k, and the PeckShield cause attribution (claim_findings[2]) is only partly supported. A cited shutdown link is dead (claim_findings[4]), and most primary sources could not be read, which limits this review. The core narrative of a May 2021 exploit, later exploits and a 2022 shutdown held up, and no omissions or contradictions of the subject's status were found.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-10,"scored_claims":5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}