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 · WazirX
- Sequence
- #3
- Score
- 2 → 38 (+36)
- Cluster
- mainnet-beta
- Slot
- 426699673
- Off-chain at
- 2026-06-15T19:41:24.577Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AWgNEL74AMGdS1j6FzccGGGn9R1wMaHiJNqocAgVcrJL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1771 chars)
{"actor":"judge","decided_at":"2026-06-15T19:41:24.344Z","decision":"review_approve","investigation_id":"d32c6324-cf7c-4195-8d4f-05c20913c10d","new_score":38,"page_slug":"wazirx","prev_score":2,"reason":"The reviewer evaluated 36 claims and found zero disputed. Thirty-one claims are fully confirmed by Tier 1 and Tier 2 sources; three are partially supported with minor framing imprecision (the '55% recovery' figure understates the court-approved plan's upside, per claim_findings[3] and claim_findings[32]); one is unverifiable (the INR 25,60,000 cash seizure and DOJ MLAT detail, claim_findings[27]). No link rot, no stale citations on critical claims. The page's current score of 2 (CRITICAL) is a calibration error: the primary incident — the $234.9 million July 2024 hack — is attributed by three national governments, Elliptic, and ZachXBT to North Korea's Lazarus Group, placing it squarely in the 'suffered' category under AVOID.NET's anti-conflation rule. Own-conduct risk factors are real but pre-adjudicated: the ED FEMA show-cause notices (claim_findings[8], claim_findings[28]) establish compliance failures warranting WARNING-band treatment, and the undisclosed Panama entity (Zensui Corporation, claim_findings[30]) reflects a transparency failure during restructuring proceedings. Neither constitutes confirmed large-scale fraud. Reviewer confidence is 0.88; the calibration rationale is detailed and analytically sound. A score of 38 (WARNING band) correctly represents an entity with unresolved regulatory allegations and governance concerns that was also a high-profile victim of a nation-state cyberattack.","score_delta":36,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}