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_revise · BitMart Exchange
- Sequence
- #3
- Score
- 22 → 10 (-12)
- Cluster
- mainnet-beta
- Slot
- 443519880
- Off-chain at
- 2026-08-26T09:07:00.907Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5q1bCSJZWHLh6Y9euc9AVXbGkJ6rLgsJEGinNX8rCx7B
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1685 chars)
{"actor":"judge","decided_at":"2026-08-26T09:07:00.465Z","decision":"review_revise","investigation_id":"79b0dc93-23eb-4d30-9963-5fbf898bad82","new_score":10,"page_slug":"bitmart-exchange","prev_score":22,"reason":"Independent verification confirms the page's core reporting: the 2021 hot-wallet hack, the July 26, 2026 shutdown announcement and its mechanics, the CEO's termination, the BMX token collapse, and the withdrawal-delay reporting all hold up (39 of 49 claims confirmed). Only 2 claims were actively disputed and 3 unverifiable, putting the disputed rate at 5/49 (10.2%) -- just over the 10% line that separates approval from revision. Two currency problems, not counted in that percentage but flagged by the reviewer as the page's most consequential issues, run in different directions: the page presents BitMart's full closure as a settled timeline when reporting from days before this review shows the company pivoting toward a restructuring option instead, and separately the page calls an FTC investigation's outcome 'unclear' when later reporting suggests the case was dismissed in 2023 -- though that finding rests on a secondary source citing a primary record rather than the record itself. A wallet-balance figure was also misattributed to the wrong analytics firm. Given a solid factual core alongside these two time-sensitive gaps and two high-priority coverage gaps, the page warrants revision to reflect the current closure status and clarify the regulatory record, rather than approval as-is or a deny/delist action.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}