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
- #10
- Score
- 0 → 0 (-5)
- Cluster
- mainnet-beta
- Slot
- 464245572
- Off-chain at
- 2026-11-01T21:35:48.999Z
- Anchored at
- 2026-11-01T21:36:40.000Z
- Block time
- 2026-11-01T21:36:40.000Z
Independent verification
- 1. Database (off-chain)
- Ah5uzycYrqfNTbH44YCjd1Pq5terMszzuZUjG7d9z4Qn
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1262 chars)
{"actor":"judge","artifact_identity":"ad5524ba70735c8e248d6960ff3607cd","band_override":null,"decided_at":"2026-11-01T21:35:48.753Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.125,"investigation_id":"90f8a94c-c24b-4345-9af5-b70ca3fd82f0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"hookedpad","prev_score":0,"reason":"Seven of the eight checked claims match their cited sources (claim_findings[0] to [6]). One claim, that other tokens such as Hooked Protocol share the HOOKED name (claim_findings[7]), could not be verified against a fetched source, which puts 1 of 8 findings (12.5%) in the minor-issues band. That claim is low-stakes and widely known, so the penalty is kept at the lightest end. The review also lists a high-priority coverage gap: upgrade authority, holder concentration and liquidity lock have not been checked on-chain. Most claims rest on a single Tier 3 article. No shutdown, exploit or material omission was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"sequence_num":10,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}