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
- #8
- Score
- 9 → 0 (-20)
- Cluster
- mainnet-beta
- Slot
- 464112703
- Off-chain at
- 2026-11-01T13:41:31.996Z
- Anchored at
- 2026-11-01T13:41:52.000Z
- Block time
- 2026-11-01T13:41:52.000Z
Independent verification
- 1. Database (off-chain)
- ELB4ifVddBSTXtxgaS37UZ5m2bKNCHozrtsqQ1nNmkKF
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1915 chars)
{"actor":"judge","artifact_identity":"beae6bc252c51f2c3c835e985260eef8","band_override":null,"decided_at":"2026-11-01T13:41:31.737Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2727,"investigation_id":"90f8a94c-c24b-4345-9af5-b70ca3fd82f0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"hookedpad","prev_score":9,"reason":"Of 10 checked claims, 2 were disputed and 1 could not be verified, which is 30%. The disputed claims (claim_findings[6] and [7]) are in the wallet-flow section: it says tracked wallets were net accumulating and that the net-seller claim is no longer supported, but the live tracker now shows net distributing. The page also omits a material risk reported by Bittime, that the deploy wallet can still upgrade the hook program and some rules can restrict selling. The rule counts and market cap figures are out of date but the overall decline narrative holds, the fee mechanics, launch date and absence of a named team were confirmed, and no shutdown or exploit was found. The reviewer's confidence was moderate (0.6), so the penalty sits in the lower-middle of the band and the page is not delisted.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-20,"sequence_num":8,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"disputed_pct is 30% (2 disputed + 1 unverifiable of 10), on the line between minor and significant. omission_findings[0] is material: the deploy wallet can still upgrade the hook program and some rules can restrict selling, and the page says neither. The coverage gap on upgrade authority and holder concentration is high priority. Together these put the page in the significant band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}