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 · LCX
- Sequence
- #2
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 443509065
- Off-chain at
- 2026-08-19T01:41:35.083Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DddtwHwR3DFtbjPNhYC8fXn3jWX23vPxqrpppd2pZvnJ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1395 chars)
{"actor":"reviewer","decided_at":"2026-08-19T01:41:34.991Z","decision":"review","investigation_id":"c61799b4-62c8-490b-b7ea-ee281ee5113f","new_score":42,"page_slug":"lcx","prev_score":42,"reason":"The page's core factual claims -- the 2022 hot wallet hack amount, laundering timeline, law-enforcement asset freezes, user compensation commitment, FMA registrations, and the NFT-service legal case -- are all independently corroborated by multiple credible sources and are accurately, appropriately hedged where hedging is warranted. Two defects were found: the 'flagged by ZachXBT' claim in the summary has no citation and could not be corroborated anywhere despite extensive search, and one cited source (cybercriminal.com) has gone link-dead, now redirecting to a domain-parking page. Separately, the page's framing of LCX as carrying a 'below-average trust score' due to the 2022 hack and ongoing complaints does not reflect that LCX has since achieved full MiCA compliance, launched a US exchange, and partnered with Coinbase on a token migration in 2026 -- an omission that skews the page toward the 2022 incident even though the entity's regulatory trajectory since then has been unambiguously toward expansion and compliance, not further incident.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}