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 · Ramzinex
- Sequence
- #3
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 425429929
- Off-chain at
- 2026-06-09T23:44:28.614Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5dX4FTPJUZnuTxuTi5XkcekMR35nJ2pmehSH9EmfK8Lj
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1304 chars)
{"actor":"judge","decided_at":"2026-06-09T23:44:28.079Z","decision":"review_approve","investigation_id":"50d0d8ed-d4d0-4f10-a3fc-57c7dab3b37c","new_score":2,"page_slug":"ramzinex","prev_score":2,"reason":"The review confirmed 16 of 23 claims from Tier 1 and Tier 2 sources, with zero disputed claims and a reviewer-computed disputed_pct of 9%, placing this in the approve band. All core facts about Ramzinex's OFAC designation — the date, the executive order, the $2.45B figure, the co-designated exchanges, and the sanctions consequences — are confirmed by the Treasury primary source. The most notable factual error (claim_findings[5]) concerns co-designated exchanges Wallex and Bitpin: the page incorrectly states they were designated under both EO 13902 and EO 13224, when the Treasury press release confirms only Nobitex received the dual designation. This error pertains to entities other than Ramzinex and does not undermine Ramzinex's own record. Two high-priority coverage gaps remain (on-chain wallet attribution and named executive verification), which suggest the page would benefit from expansion but do not warrant denial or revision at this time.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}