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 · HookedPad
- Sequence
- #12
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 464635356
- Off-chain at
- 2026-11-02T20:48:39.111Z
- Anchored at
- 2026-11-02T20:49:06.000Z
- Block time
- 2026-11-02T20:49:06.000Z
Independent verification
- 1. Database (off-chain)
- GWmZ8JyEwnMxzJYVR6RDUHkg6kVdm5j6C57HzGaTRDNe
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1250 chars)
{"actor":"judge","artifact_identity":"1a70453b1548477452298793a89ed860","band_override":null,"decided_at":"2026-11-02T20:48:38.759Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"90f8a94c-c24b-4345-9af5-b70ca3fd82f0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"hookedpad","prev_score":0,"reason":"Of five claims checked, four were confirmed and one (claim_findings[2]) was partially supported because the cited Cryptoast article is dated 2022-11-24, one day after the stated 2022-11-23 announcement date. None were disputed or unverifiable, so the disputed share is 0%. The only omission (launch date and price volatility) is minor, and no shutdown, exploit or sanction was found. The two high-priority coverage gaps, on-chain checks and team or audit information, are already stated openly on the page, which also labels its single-source, promotional basis, so they call for expansion rather than a penalty.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":12,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}