Skip to main content
AVOID.NET
← 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_revise · Huobi / HTX
View on Solana ↗
Sequence
#3
Score
14 → 7 (-7)
Cluster
mainnet-beta
Slot
443506711
Off-chain at
2026-08-10T18:23:04.493Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
ATWAWbNv7LkDdB5aStzqYNNsv9CWEDKfZ4vxUhNub68G
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1742 chars)
{"actor":"judge","decided_at":"2026-08-10T18:23:04.224Z","decision":"review_revise","investigation_id":"2ece5745-c331-49f2-8a6b-cbd578cfd4e5","new_score":7,"page_slug":"huobi-htx","prev_score":14,"reason":"The page's central allegations hold up well: the May 2026 UK sanctions designation, the $1.5B FCDO figure, the A7/Garantex network details, the TRM Labs and Global Ledger flow figures, the FCA promotions case, the SEC/Justin Sun history, and the 2023-2025 security incidents were all independently confirmed against primary or credible secondary sources (claim_findings 0-6, 9-23, 25). No claim was found to be substantively disputed and disputed_pct is 7.4%, which sits at the low end of the scale. However, several secondary details need correction: the 47 million user figure is stale and superseded by HTX's own later 55 million disclosure (claim_findings[7]); the Garantex 2022 OFAC timeline entry cites the wrong Treasury press release URL, a link_rot issue that should be swapped for the correct source (claim_findings[13]); the stated cause of Grinex's April 2026 shutdown is vaguer than, and inconsistent with, independent reporting attributing it to a specific cyberattack (claim_findings[15]); and the reviewer also flagged a high-priority coverage gap around the absence of any address- or transaction-level on-chain evidence backing the aggregate dollar figures cited throughout (coverage_gaps[0]). None of this undermines the page's core findings, but the mix of a mis-cited critical-section source and a high-priority evidence gap warrants revision rather than a clean approval.","score_delta":-7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}