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 · WhiteBIT Coin
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 443526519
- Off-chain at
- 2026-08-27T16:10:31.747Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6K5JpE3gGVTNLHAVpk9qCTBAmFQqJRkodwnL4BtvmuTc
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1482 chars)
{"actor":"reviewer","decided_at":"2026-08-27T16:10:31.501Z","decision":"review","investigation_id":"750f207a-72ac-4e22-9e78-a86daa24d1d2","new_score":38,"page_slug":"whitebit-coin","prev_score":38,"reason":"The page's core narrative (disputed ownership, multiple money-laundering allegations, the Ukrainian drug-cartel investigation, and Russia's 'undesirable organization' designation) is well-corroborated by independent reporting and generally appropriately hedged as unadjudicated allegation. However, the review found a materially misattributed fact (the 2023 citizenship revocation applied to Mykyta Shentsev, not Dmytro Shentsev, as the page states), a citation mismatch on the S&P indices claim (the page's own source names a fifth index it omits), an ATH date/figure that the cited source does not actually support, an unreconciled 25M-token gap in the page's own tokenomics arithmetic, and a stale Regulatory Status section that omits WhiteBIT's real, current MiCA CASP authorization via Austria's FMA in favor of a superseded Lithuania-centric framing. The timeline shows a pronounced placeholder-date pattern, with 12 of 20 entries falling on the first of a month; several of these were checked against underlying sources and found to be materially imprecise (off by weeks to a full month) rather than merely stylistic rounding.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}