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 · HTX (Huobi) Exchange
View on Solana ↗
Sequence
#5
Score
8 → 25 (+17)
Cluster
mainnet-beta
Slot
426514657
Off-chain at
2026-06-14T23:16:07.886Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
FReNG3zE4kWxC1ALCKVM3tgvgTTW4uHyiGUvqAAKd235
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1762 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:07.770Z","decision":"review_approve","investigation_id":"849c6623-be9b-4a8a-a85c-418a2d270d97","new_score":25,"page_slug":"htx-huobi-exchange","prev_score":8,"reason":"All 7 claim_findings returned 'supported' with 0% disputed content — the page's factual record is accurate and stands. The calibration review correctly identifies that a score of 8/CRITICAL misclassifies HTX alongside exit scams and Ponzi schemes when the page's own content describes an operational exchange (59M+ users, $3.3T 2025 volume) subject to compliance failures, not fraud against users. The two 2023 security incidents (claim_findings[2], claim_findings[3]) were suffered-by hacks that HTX remediated through full user compensation; the SEC settlement (personal action against Justin Sun, settled via Rainberry Inc., with exchange-level charges dismissed) was misweighted as exchange-level fraud. The genuine own-negligence risks — UK sovereign sanctions designation (claim_findings[0], RUS3619), $4.9B documented flows to sanctioned Russia-linked entities (claim_findings[1]), and FCA civil proceedings for unlawful promotions (claim_findings[6]) — are real and material, placing HTX firmly in WARNING territory. A score of 25/WARNING is calibrated correctly: it signals serious, active compliance risk without misidentifying a major exchange as a scam. The positive score_modifier_delta of +17 moves the page from the fraud/scam band (0-19/CRITICAL) to the WARNING band (20-39), consistent with band policy for entities that facilitate compliance failures rather than perpetrate user fraud.","score_delta":17,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}