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 · OKX
- Sequence
- #5
- Score
- 35 → 44 (+9)
- Cluster
- mainnet-beta
- Slot
- 426514970
- Off-chain at
- 2026-06-14T23:16:23.747Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- G69xkHXiEfxZAi9e27arW38beB5dJJEpDKCJXUQh32gM
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1606 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:23.503Z","decision":"review_approve","investigation_id":"37ff6a21-bdb8-47a7-908e-f9841fe89699","new_score":44,"page_slug":"okx","prev_score":35,"reason":"All six claim_findings in the review are supported with no disputed claims (disputed_pct = 0%). The page content is accurate and stands as published. This is a severity-calibration adjudication: the current score of 35 is modestly below where the evidence warrants within the WARNING band. The DOJ SDNY guilty plea (claim_findings[0]) and the pattern of multi-jurisdictional AML failures (claim_findings[1]) constitute affirmative misconduct by OKX's own staff and clearly anchor placement in the WARNING band. However, measurable remediation steps documented in claim_findings[3] and claim_findings[4] — specifically ICE's $200M strategic investment at a $25B valuation, full MiCA licensure across all 30 EEA states, and the court-supervised external compliance monitor through February 2027 — support a marginal upward adjustment to 44, keeping the page firmly in WARNING while crediting verifiable progress. The Lazarus Group/Bybit laundering incident (claim_findings[2]) applies only a partial own-negligence penalty as it is primarily third-party abuse of OKX's DEX aggregator. A score_modifier_delta of +9 moves the score from 35 to the reviewer-recommended 44, consistent with the WARNING band and proportionate to the severity of the criminal conviction.","score_delta":9,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}