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 · BitcoinDepot
- Sequence
- #4
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462277441
- Off-chain at
- 2026-10-28T00:41:47.480Z
- Anchored at
- 2026-10-28T00:42:34.000Z
- Block time
- 2026-10-28T00:42:34.000Z
Independent verification
- 1. Database (off-chain)
- 3jxBFfetmBoEq7TP7JhnAQWK71ki92bk5A9TSbis2bxW
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1415 chars)
{"actor":"judge","artifact_identity":"8103d63c70b1aa5be705e8ca0065a229","band_override":null,"blocked_count":1,"decided_at":"2026-10-28T00:41:47.281Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"cb6daff0-104b-4618-8467-22580c2112f4","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"bitcoindepot","prev_score":26,"reason":"Of the six claims checked, none were disputed or unverifiable for reasons other than a blocked source, so the disputed share is 0%. The Massachusetts figures (claim_findings[1]) could not be checked because Mass.gov refused the fetch; that is a coverage limit, not a defect of the page. Two findings were only partly supported: the Washington charging-document date (claim_findings[2]) and the Nasdaq suspension entry (claim_findings[4]), which cites an unrelated pre-bankruptcy 8-K although the suspension date itself is right. The omissions found are minor, and the page already reflects the company's shutdown. Only a sample of claims was checked, so the page should be revised to fix the timeline source and add the Nasdaq delisting.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":5,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}