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 · LCX Exchange
- Sequence
- #3
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 424312469
- Off-chain at
- 2026-06-04T20:05:48.436Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6PzNyBmNETqxsNDkqhGPrDr6jcg1oRKkdpoSwkXaxbxK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1408 chars)
{"actor":"judge","decided_at":"2026-06-04T20:05:48.239Z","decision":"review_approve","investigation_id":"57fe7602-1a16-49d9-ae77-f6adf0837007","new_score":62,"page_slug":"lcx-exchange","prev_score":62,"reason":"The reviewer examined 24 claims and found zero disputed. Twenty claims were fully confirmed against Tier 1 and Tier 2 sources; two were partially supported with minor precision issues (claim_findings[3] slightly conflates a 45-minute conversion window with a 1.5-hour end-to-end laundering timeline, and claim_findings[20] cites an April 2018 incorporation date the referenced source does not explicitly state). One claim (claim_findings[23], LCX token MiCA utility classification) is unverifiable due to reliance on Tier 3 promotional sources only, but it is a peripheral claim with no bearing on the page's core allegations. Two dead URLs were identified (CoinTelegraph NFT service-of-process story, GlobeNewswire MiCA pre-application release), but both underlying claims are confirmed through independent mirror sources. With a computed disputed_pct of 4% and reviewer confidence of 0.88, the page meets the approval threshold. One high-priority coverage gap — the unresolved post-2022 status of LCX AG v. John Does 1-2 — is noted for future expansion.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}