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 · Bitpin
- Sequence
- #3
- Score
- 4 → 0 (-5)
- Cluster
- mainnet-beta
- Slot
- 425430732
- Off-chain at
- 2026-06-09T23:49:47.914Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GmHQ5NmCgvVDDg2ke6WaLrfRP5hruh2omqF5MCHtWDPy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1225 chars)
{"actor":"judge","decided_at":"2026-06-09T23:49:47.728Z","decision":"review_revise","investigation_id":"e33b7aad-7706-43e0-b707-2f447e12fb52","new_score":0,"page_slug":"bitpin","prev_score":4,"reason":"Zero claims were factually disputed. Core regulatory facts — OFAC designation date, executive orders, campaign name, co-designated exchanges, volume figures, and market-share percentage — are all confirmed by Tier 1 and Tier 2 sources. The reviewer's 10% disputed figure reflects two unverifiable administrative details (claim_findings[6] registration number, claim_findings[7] street address) that could not be fetched directly from OFAC but are unchallenged and plausible, plus one partially-supported investor allegation (claim_findings[10] Patco Company / Arya Hamrah Samaneh) backed only by a community-tier Substack while Treasury's own language is notably more hedged. The page requires revision to attribute that investor claim as a community-sourced allegation and to add on-chain address attribution and officer-level detail, both flagged as high-priority coverage gaps.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}