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_with_notes · WazirX (India)
- Sequence
- #5
- Score
- 42 → 55 (+13)
- Cluster
- mainnet-beta
- Slot
- 443509420
- Off-chain at
- 2026-08-19T12:33:09.380Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8R5foWqz4ErTmYD4BsPjMAwMB4MpQQE14FCjhAdwdsuV
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2370 chars)
{"actor":"judge","decided_at":"2026-08-19T12:33:09.227Z","decision":"review_approve_with_notes","investigation_id":"42e23449-f4f3-44d4-aef7-aaa09ba97824","new_score":55,"page_slug":"wazirx-india","prev_score":42,"reason":"This is a calibration review: the page's facts hold up (14/20 confirmed, 0 disputed, only link rot and access-blocked 2022-era sources unresolved per claim_findings), but the current score of 42 (WARNING) does not match the entity's documented conduct. The page's dominant and defining incident -- the $234.9M hack -- is independently attributed to North Korea's Lazarus Group by a joint US/South Korea/Japan government statement (claim_findings[0], claim_findings[13]), making it a 'suffered' external attack, not own-fraud or entity negligence. The secondary incidents (2022 director-level ED asset freeze, 2025 terror-financing probe) implicate a single director or third-party customers rather than an adjudicated finding against WazirX/Zanmai Labs as a corporate entity (calibration_assessment incident_attributions). Per the rubric, a 'suffered' primary incident with no adjudicated corporate fraud caps at CAUTIONARY rather than WARNING; the reviewer's recommended_band/score of CAUTIONARY/55 is well supported and I agree with it. Notes: (Replace the dead coinpedia citation for the Feb 14, 2025 FIU/ED item (claim_findings[13], link_rot) with a live source or remove the specific 'ED summons Binance executives' detail if it cannot be re-sourced.) (Add a citation for the 2026-05-13 crypto futures launch timeline entry; none is currently attached.) (The 2022 ED raid/freeze and account-unfreeze timeline entries rely on sources that returned 403/429 in this review pass -- verify they are still live and re-cite with an accessible mirror if not.) (All six section bodies are empty in this snapshot (only headings/sources present) -- populate narrative content so the analytical sections are reviewable, not just the summary and timeline.) (Clarify in the body text whether any charge or chargesheet has ever been filed against WazirX/Zanmai Labs as a corporate entity, versus a director or third-party customers, to make the own-conduct vs. suffered/third-party distinction explicit to readers.)","score_delta":13,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}