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
- Sequence
- #3
- Score
- 18 → 10 (-8)
- Cluster
- mainnet-beta
- Slot
- 443505690
- Off-chain at
- 2026-08-08T03:11:39.480Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4TxnbvPjqtDin5xq7Z56tYoSvGzSgZwdP7LB8b5FiEsu
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1434 chars)
{"actor":"judge","decided_at":"2026-08-08T03:11:39.206Z","decision":"review_revise","investigation_id":"20a9d063-66d7-435f-82d1-5b2ba1af2c14","new_score":10,"page_slug":"bitmex-class-action-2026","prev_score":18,"reason":"The page's core factual claims — the July 23, 2026 SDNY filing, named parties, 622.66 BTC loss figure, BitMEX shutdown timeline, CFTC enforcement history, and Trump pardons — are well-confirmed by Tier 1 sources including PACER, CFTC press releases, and the official BitMEX blog. Two factual errors require correction: claim_findings[25] dates BitMEX's operational launch as September 2015 when multiple credible sources including BitMEX's own decade-anniversary blog confirm a November 2014 launch, and claim_findings[16] groups Samuel Reed's guilty plea with February 2022 when it was entered March 9, 2022. The BitMEX response quote in claim_findings[4] is real but truncated, dropping 'again this time' in a way that obscures a pattern-of-litigation implication. No link rot or stale critical citations were found. A high-priority coverage gap exists around on-chain analysis of the alleged liquidation events, and a medium-priority gap around the July 2024 corporate BSA guilty plea — a distinct enforcement event absent from the page's regulatory history section.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}