Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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_revise · LCX
View on Solana ↗
Sequence
#8
Score
54 → 34 (-20)
Cluster
mainnet-beta
Slot
464265976
Off-chain at
2026-11-01T22:49:13.339Z
Anchored at
2026-11-01T22:49:37.000Z
Block time
2026-11-01T22:49:37.000Z

Independent verification

1. Database (off-chain)
6oyNV7FFH6NuUgbG7Azd3XG1ZcUdfGKHQY2P8jows86Y
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1832 chars)
{"actor":"judge","artifact_identity":"c0740761cb4db1e092e5ff2a9afc5392","band_override":null,"decided_at":"2026-11-01T22:49:13.088Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1,"investigation_id":"c61799b4-62c8-490b-b7ea-ee281ee5113f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":34,"page_slug":"lcx","prev_score":54,"reason":"The 2022 hack account (amounts, timing, roughly 60% frozen, New York court action) matches LCX's official reports (claim_findings[0], [2]). However, 4 of 10 claims (40%) are stale, link-rotted or unsourced: the December 2025 MiCA target and the 'regulated exchange' wording are out of date (claim_findings[4], [5]), a cited source is now a parked domain (claim_findings[7]), and one timeline entry has no source (claim_findings[6]). The page also omits that LCX says it is not MiCA-authorised and no longer serves EEA clients (omission_findings[0], critical), so the page's current-status picture is misleading. Reviewer confidence is moderate (0.6), so the penalty sits in the middle of the significant band and the page is not denied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-20,"score_limit":{"applied":-20,"limited":true,"proposed":-25,"rule":"second_opinion_agreed","second":-20},"sequence_num":8,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"The review reports a critical omission (LCX states it is not MiCA-authorised and has wound down service to EEA clients) and subject_status.contradicts_page is true. The 40% claim band is already significant; the omission confirms that band and rules out a lower one."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}