Skip to main content
Sign in
← 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_approve · WazirX: India
View on Solana ↗
Sequence
#3
Score
10 → 42 (+32)
Cluster
mainnet-beta
Slot
426699681
Off-chain at
2026-06-15T19:41:27.253Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
3RK9mwdar333KYPFpMv3Fgin95hiLpTY4XhbcQ1ci5ui
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1414 chars)
{"actor":"judge","decided_at":"2026-06-15T19:41:27.064Z","decision":"review_approve","investigation_id":"42e23449-f4f3-44d4-aef7-aaa09ba97824","new_score":42,"page_slug":"wazirx-india","prev_score":10,"reason":"The reviewer found 0 of 20 claims disputed and confirmed 15 outright, with 3 partially supported (minor framing issues: Binance 'acquisition' terminology at timeline[1], litigation timing at timeline[4], and Mandiant/Liminal conflicting forensics at timeline[6]) and 2 dead citation URLs. Disputed_pct is effectively 0%, well within the review_approve threshold. The calibration correction is the primary action here: the page's current CRITICAL score of 10 is demonstrably miscalibrated. The entity's defining event — a $234.9M hack confirmed by a US/Japan/South Korea joint statement (claim_findings[1], claim_findings[8]) — is a suffered nation-state cyberattack, not own-fraud. Own-conduct findings are limited to 2022 AML compliance failures (ED raid, claim_findings[2]) and an overreaching XRP redistribution attempt blocked by the Madras High Court (claim_findings[14]), neither of which meets the CRITICAL bar. A score of 42 (WARNING band) correctly reflects genuine but non-criminal own-conduct issues alongside an externally perpetrated primary harm.","score_delta":32,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}