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
- 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. - 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.
- 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 · Bitfinex Hack
- Sequence
- #1
- Score
- 10 → 10 (0)
- Cluster
- mainnet-beta
- Slot
- 419601689
- Off-chain at
- 2026-05-14T03:02:35.719Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AVxzpX8mavGu59F5oPmmJNBxVZsgShL1GuuPLXGGtZtE
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1209 chars)
{"actor":"reviewer","decided_at":"2026-05-14T03:02:35.600Z","decision":"review","investigation_id":"755ee9e6-8b69-4f8a-a4f5-629dff9274f1","new_score":10,"page_slug":"bitfinex-hack","prev_score":10,"reason":"The Bitfinex Hack investigation is highly accurate across all major claims. Core facts — the hack date and mechanism, BTC quantity stolen, socialized loss percentage, BFX token mechanics, arrest dates and charges, guilty plea counts, sentencing dates and terms, and the early release details — are all confirmed by authoritative sources including official DOJ/ICE press releases and multiple tier-1 news outlets. Three claims are rated partially_supported: a minor internal BTC count discrepancy (119,754 vs 119,756), a slight overstatement of Heather Morgan's time served, and an unconfirmed January 1 date for the AlphaBay fund movement (documented as 'early 2017' rather than specifically January 1). No claims are disputed or unverifiable. Coverage gaps exist around Bitfinex's broader regulatory history, current fund return status, and on-chain evidence.","score_delta":0,"sequence_num":1,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}