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 · Ramzinex
- Sequence
- #2
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 425429924
- Off-chain at
- 2026-06-09T23:44:28.323Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- J7BUam3YEoVSDV2UjKRCxaKbnJA5H54BJNABhaouMAK7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1070 chars)
{"actor":"reviewer","decided_at":"2026-06-09T23:44:28.079Z","decision":"review","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","new_score":2,"page_slug":"ramzinex","prev_score":2,"reason":"The page is substantively accurate with respect to the core OFAC designation facts, transaction volumes, and enforcement context. The most significant factual error is the claim that Wallex and Bitpin were designated under both EO 13902 and EO 13224 — the Treasury primary source confirms only Nobitex received the dual designation; Wallex, Bitpin, and Ramzinex were all designated solely under EO 13902. Minor issues include a founding-year ambiguity (2017 vs. 2018), an attribution error in the timeline (Sharif University detail cited to Treasury rather than third-party sources), and an overstated characterization of compliance analyst consensus on secondary sanctions language. All primary sources are live and accessible.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}