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 · HookedPad
- Sequence
- #4
- Score
- 22 → 17 (-5)
- Cluster
- mainnet-beta
- Slot
- 462040840
- Off-chain at
- 2026-10-27T10:42:49.329Z
- Anchored at
- 2026-10-27T10:43:10.000Z
- Block time
- 2026-10-27T10:43:10.000Z
Independent verification
- 1. Database (off-chain)
- 6NsqgvqeJipiLf1HsSGwFf37GcuKPdbssv7yb9rZ7wbM
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1383 chars)
{"actor":"judge","artifact_identity":"6d41182b89d0dc3d83ed79ec4a127c18","band_override":null,"decided_at":"2026-10-27T10:42:49.018Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1,"investigation_id":"90f8a94c-c24b-4345-9af5-b70ca3fd82f0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":17,"page_slug":"hookedpad","prev_score":22,"reason":"Of 10 claim findings, 8 were confirmed, 1 was partially supported (live tracker price drifted slightly, the roughly 85-90% decline still holds), and 1 could not be verified: claim_findings[7], an internal review note placed in the timeline that is not a fact about the entity and cites an unrelated source. That puts the unverified share at exactly 10%, the edge of the approve band. The review also lists a high-priority coverage gap (coverage_gaps[0]: upgrade authority of the launchpad and hook programs and holder distribution were not checked on-chain), so the page is revised rather than approved. No shutdown, exploit or sanction was found, and the only omission (the site's inconsistency about devnet versus mainnet testing) is minor.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}