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 · OKX DEX
- Sequence
- #3
- Score
- 28 → 18 (-10)
- Cluster
- mainnet-beta
- Slot
- 426269868
- Off-chain at
- 2026-06-13T20:18:09.609Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EfLVeFX2JF6j5Xgniv2NVMDFsQrYnLeY4du3uzRDgXRk
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1431 chars)
{"actor":"judge","decided_at":"2026-06-13T20:18:09.399Z","decision":"review_revise","investigation_id":"ce84ec9f-aae8-4f31-8aec-4fb339bbc913","new_score":18,"page_slug":"okx-dex","prev_score":28,"reason":"The review found zero formally disputed claims, but two high-priority structural problems require correction before the page can be approved. First, claim_findings[13] establishes that the page's description of a 'Three-year compliance monitor' in the DOJ settlement is inaccurate — OKX voluntarily retained a compliance consultant through February 2027; no court-ordered or government-appointed monitor was accepted. This distinction is material to assessing regulatory severity. Second, a high-priority coverage gap notes that all eight analytical page sections contain empty content, meaning the sourced evidence exists but the written body of the page has not been generated. Additionally, claim_findings[1] and claim_findings[7] present the PeckShield $2.7M exploit estimate as the page's sole figure without noting OKX's own confirmed loss of approximately $370K-$430K — a factual qualification readers should have. The major regulatory claims (DOJ settlement amount, Malta FIAU fine, Lazarus laundering, Bybit hack) are confirmed by credible sources including Tier 1 outlets.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}