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 · Binance
View on Solana ↗
Sequence
#3
Score
3845 (+7)
Cluster
mainnet-beta
Slot
426514976
Off-chain at
2026-06-14T23:16:24.304Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
AxknijHiZ3apRqFoefTN35J6NEWAqc8Wy6Uo7aPGHLFe
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1901 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:24.197Z","decision":"review_approve","investigation_id":"ee0b172d-1fd3-47c7-812a-115748f8108a","new_score":45,"page_slug":"binance","prev_score":38,"reason":"This is a severity-calibration adjudication, not a fact-dispute review. The reviewer found 0% disputed claims (claim_findings[0–6] are all supported), confirming the page content is accurate and well-sourced. The reviewer assessed the current score of 38 as modestly over-penalized: claim_findings[4] and the modifier flags establish that two security incidents (May 2019 hot-wallet hack; October 2022 BNB bridge exploit) were suffered-by-entity events covered by user-protection funds, not operator fraud, and should not weigh the same as own-conduct misconduct; claim_findings[3] documents that the SEC's 13-count lawsuit was dismissed with prejudice in May 2025, removing a material legal overhang that contributed to the depressed score; and claim_findings[4] and [6] document ongoing legitimacy markers (ADGM global license secured December 2025, $170B+ proof-of-reserves, 36.5% global market share) that are inconsistent with a score near the CRITICAL-band boundary. Genuine residual risk remains material — the active DOJ Iran sanctions probe (claim_findings[2], $1.7B+ flagged flows), the pending $1B+ Anti-Terrorism Act lawsuit (claim_findings[5]), and active compliance monitorships (page section 'Compliance Monitor') justify keeping the page firmly in the WARNING band. A score of 45 — still in WARNING, not approaching CAUTION — appropriately balances the severity of the admitted 2023 criminal conduct against post-settlement compliance progress and legitimacy indicators. Reviewer confidence is 0.82, supporting a decisive positive delta.","score_delta":7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}