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_revise · WazirX
- Sequence
- #7
- Score
- 60 → 60 (0)
- Cluster
- mainnet-beta
- Slot
- 464276832
- Off-chain at
- 2026-11-01T23:28:04.057Z
- Anchored at
- 2026-11-01T23:28:22.000Z
- Block time
- 2026-11-01T23:28:22.000Z
Independent verification
- 1. Database (off-chain)
- 9NdK7L3ZbyRFdA4CicyyyXirGPsmvT18gySrvGXeicst
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1829 chars)
{"actor":"judge","artifact_identity":"76e23688c6923dc8e23c23798b30a335","band_override":null,"blocked_count":2,"decided_at":"2026-11-01T23:28:03.805Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.125,"investigation_id":"d32c6324-cf7c-4195-8d4f-05c20913c10d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"page_slug":"wazirx","prev_score":60,"reason":"Of 10 claims reviewed, 2 could not be checked because the sources blocked the reviewer and were left out of the count; of the remaining 8, one is disputed (claim_findings[0]), giving about 12.5% disputed, which falls in the minor-issues band. The disputed item is a dating error: the page says the Singapore High Court declined to sanction the first restructuring scheme on 16 June 2025, but WazirX announced the rejection on 4 June 2025, and the page's own cited article is dated 5 June. The core narrative (the $234.9M hack, the January 2025 attribution to North Korea, the October 2025 court sanction and the 24 October 2025 restart) was confirmed. The one partially supported item (claim_findings[7], the 'jurisdictional grounds' wording in the summary) is a loose characterization and was not counted as disputed. The review found no sign the exchange has shut down, and the one omission (no 2026 update after the restart) is minor, so the penalty is kept small. The reviewer's confidence is moderate (0.55), and the blocked sources (the Indian ED claims and the Binance 2022 statement) are a coverage limit on this review, not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}