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 · OKX DEX
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 426269866
- Off-chain at
- 2026-06-13T20:18:09.522Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8uvyDw5Vgt9ES8yW4L7XM53i1F8DE4G7ve2b4xFYvDmS
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1110 chars)
{"actor":"reviewer","decided_at":"2026-06-13T20:18:09.399Z","decision":"review","investigation_id":"ce84ec9f-aae8-4f31-8aec-4fb339bbc913","new_score":28,"page_slug":"okx-dex","prev_score":28,"reason":"The page's major regulatory and incident claims are directionally accurate and supported by credible sources, including the DOJ settlement, Malta FIAU fine, Bybit hack laundering connection, and OKX DEX exploit. Key inaccuracies include: (1) the exploit loss amount uses PeckShield's $2.7M external estimate without noting OKX's lower confirmed figure of ~$370K-$430K; (2) the DOJ settlement's compliance requirement is described as a 'three-year compliance monitor' when it was actually a voluntary compliance consultant; (3) several timeline dates use placeholder values (Jan 1, Apr 1) rather than actual dates. All eight page sections have completely empty content, meaning the sourced URLs exist but the written analytical body of the page has not been generated.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}