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 · KuCoin
- Sequence
- #2
- Score
- 18 → 18 (0)
- Cluster
- mainnet-beta
- Slot
- 423159411
- Off-chain at
- 2026-05-30T12:48:11.059Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6tfkgb9aAnwP288KRjvq3D2BCNoxUYToXsFntzMVN4Aa
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (912 chars)
{"actor":"reviewer","decided_at":"2026-05-30T12:48:10.363Z","decision":"review","investigation_id":"0c56d875-ca56-4175-b95f-c50e5fe7e1a2","new_score":18,"page_slug":"kucoin","prev_score":18,"reason":"The investigation page is largely accurate on major facts — the DOJ guilty plea, CFTC action, FINTRAC penalty, and ZachXBT allegations are all well-supported. Key issues are: (1) the Chainalysis Lazarus attribution date is wrong by approximately four months (February 2021, not June 2021); (2) the headquarters relocation is described as 'China to Singapore' when sources consistently say 'Hong Kong to Singapore'; (3) the hack date in the timeline is September 26 when it occurred September 25. No claims were found to be fabricated or contradicted by credible sources.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}