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
- #5
- Score
- 30 → 30 (0)
- Cluster
- mainnet-beta
- Slot
- 457876802
- Off-chain at
- 2026-10-17T02:51:04.967Z
- Anchored at
- 2026-10-17T02:51:21.122Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2mzMqKw5A7WiTacr4TMdBZkRCX1Bt4AEUUnr9jwqKGE2
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2082 chars)
{"actor":"reviewer","artifact_identity":"15e7dd44e33452e56e5cdc43c208443e","decided_at":"2026-10-17T02:51:04.762Z","decision":"review","disputed_pct":0.1724,"findings_hash":"NuUPhtC3VAN69fcf486mUup6w4eAPv4JkP33anUffu5","investigation_id":"4ae6a329-6762-4493-a983-9752d79f1fc0","mode":"findings_only","new_score":30,"page_content_hash":"4fe8a227d38acb7cb2d3e22cbf68be6076722fab8596c37e017d4430ee6bdad8","page_slug":"bitmex-exchange-closure-september-2026","prev_score":30,"reason":"The page's core narrative -- announcement date, closure mechanics, withdrawal-fee schedule, the BKX Services/Namdar lawsuit, the regulatory penalty history (indictment, FinCEN/CFTC settlement, founder penalties, HDR guilty plea and fine, Trump pardons including the corporate entity), the failed Broadhaven-led sale, and the BMEX token crash -- holds up well against primary sources (BitMEX's own blog, CFTC and FinCEN press releases, and independent news coverage) and is generally careful to flag where sources disagree. The clearest defect is in the low-severity Background section: the cited CoinGecko report actually states $85.3 trillion in 2025 perpetual volume (not $86.2 trillion in 2026) and a 3%-to-13% DEX:CEX volume ratio within 2025 (not a 2%-to-12% market-share rise from 2024 to November 2025), and a $84M/day BitMEX volume figure is attributed to CoinDesk when it traces elsewhere to an analyst's social-media post. The 13,000-14,000 BTC pre-rebalance insurance-fund figure (repeated in both a section and the timeline) rests on an unverified social-media claim that is internally inconsistent with other reporting of a 'roughly 90%' reduction. A BMEX market-cap figure ($497,000) could not be independently verified. The most significant gap is temporal: the page was evidently written before the September 23, 2026 closure date and has not been updated with any post-closure reporting, despite the review occurring nearly a month afterward.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}