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_deny · CoinEx
- Sequence
- #6
- Score
- 60 → 60 (0)
- Cluster
- mainnet-beta
- Slot
- 464366779
- Off-chain at
- 2026-11-02T04:49:20.227Z
- Anchored at
- 2026-11-02T04:49:31.000Z
- Block time
- 2026-11-02T04:49:31.000Z
Independent verification
- 1. Database (off-chain)
- 8dpsmU7fE4sUYRfrSt5Jrj5gf7DxTaZ8DLo6xe1imteS
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1754 chars)
{"actor":"judge","artifact_identity":"7b82725b5ea9b48c0e97e8bfa91c36a4","band_override":null,"blocked_count":2,"decided_at":"2026-11-02T04:49:19.957Z","decision":"review_deny","delist_requested":true,"disputed_pct":0.75,"investigation_id":"d92e1f6b-7eff-4736-87ca-242d88651e2e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"page_slug":"coinex","prev_score":60,"reason":"Of the 8 claims the reviewer could assess (2 were excluded because the source blocked access), 6 were disputed or unverified, about 75%. The Sinbad section attributes the CoinEx link to the Treasury release, which does not name CoinEx; that link comes from Elliptic (claim_findings[1], [3], [4]), and a Treasury quotation is slightly misworded (claim_findings[2]). The page also omits that CoinEx announced a wind-down in September 2026 and faces Iran sanctions-exposure allegations from June 2026 (omission_findings[0], [1]), so its recovery narrative is out of date. The core 2023 hack and Lazarus attribution are consistent with the coverage the reviewer could read, and the reviewer's confidence is moderate (0.65).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":6,"severity_override":{"applied":true,"band":"deny","from_band":"deny","reason":"The review reports critical omissions (CoinEx's September 2026 wind-down announcement and the June 2026 TRM Labs Iran sanctions-exposure allegations) and says the page contradicts the subject's current status. These reinforce the deny band that the claim percentage already implies."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}