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
- #7
- Score
- 54 → 54 (0)
- Cluster
- mainnet-beta
- Slot
- 464265972
- Off-chain at
- 2026-11-01T22:49:13.166Z
- Anchored at
- 2026-11-01T22:49:37.000Z
- Block time
- 2026-11-01T22:49:37.000Z
Independent verification
- 1. Database (off-chain)
- 3MZCeajEiw7MMKZR2t3UA8f72RuhvYG3sBVR1hNd3qoo
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1296 chars)
{"actor":"reviewer","artifact_identity":"c0740761cb4db1e092e5ff2a9afc5392","decided_at":"2026-11-01T22:49:13.088Z","decision":"review","disputed_pct":0.1,"findings_hash":"45PCz1ZchxvsZu3WXGBQegrv7eCAUpgneooXya2AVE5u","investigation_id":"c61799b4-62c8-490b-b7ea-ee281ee5113f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":54,"omissions":{"material":2,"total":2},"page_content_hash":"892ef0d7f6a12e35d6de89b2fdf56be65339f201e8a19d2c5a2a18b5b0b8c2c9","page_slug":"lcx","prev_score":54,"reason":"The 2022 hack narrative (amounts, timing, 60% frozen, NY court action) matches LCX's official reports. The page is stale on current status: LCX's own site says it is not MiCA-authorised and has wound down EEA service, while the page cites a passed December 2025 compliance target and calls it a regulated, operating exchange. One cited source is a parked domain, one timeline entry cites the wrong page for the 611k EURe freeze, and one entry has no source.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":7,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}