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_revise · HTX
View on Solana ↗
Sequence
#5
Score
83 (-5)
Cluster
mainnet-beta
Slot
426262816
Off-chain at
2026-06-13T19:31:29.131Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
EmGaMz1cWoFtfTXV4ZCN6yH3H2S88tS3ngTrCmZSiUhg
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1295 chars)
{"actor":"judge","decided_at":"2026-06-13T19:31:28.937Z","decision":"review_revise","investigation_id":"209069f2-af57-47e8-baef-8d5873d176e2","new_score":3,"page_slug":"htx","prev_score":8,"reason":"The HTX page is substantially accurate: 14 of 20 claims are confirmed, the UK sanctions, FCA proceedings, and 2023 security breaches are all well-sourced, and the reviewer's confidence is 0.82. Two issues warrant revision before the page is considered final. First, claim_findings[1] (summary) conflates HTX-specific losses with the separately operated Poloniex exchange, causing the '$130 million in three incidents' figure to overstate HTX's own losses — the two confirmed HTX incidents total roughly $99–115 million. Second, claim_findings[8] (timeline entry for HECO Chain discontinuation) states January 25, 2024 as the formal shutdown date, but available sources show the retirement was announced in November 2024 with operations ending January 15, 2025 — an approximately one-year error. The disputed percentage is 5%, within the approve band, but these two corrections affect the page's summary-level accuracy and should be made before sign-off.","score_delta":-5,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}