Skip to main content
AVOID.NET
← 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.

Sequence
#4
Score
9 → 9 (0)
Cluster
mainnet-beta
Slot
457557161
Off-chain at
2026-10-16T07:39:16.484Z
Anchored at
2026-10-16T07:39:46.939Z
Block time
—

Independent verification

1. Database (off-chain)
D12EF4DgLe83KFa42PJfJrriCGK2pU8j9cRuij2ZYYPL
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2304 chars)
{"actor":"reviewer","artifact_identity":"5fd32bb51d0f3760b45e240761070f15","decided_at":"2026-10-16T07:39:16.011Z","decision":"review","disputed_pct":0.24,"findings_hash":"2B9b8mnHFPMssUqdtdJB7TgF5gXtK62rt5xkb9y4WTeH","investigation_id":"d9ede437-ae38-4d5f-b563-ac48f657c4d5","mode":"findings_only","new_score":9,"page_content_hash":"32032808830cefcca18a166a913bfc3c7759664abd17faf42fd7568202240063","page_slug":"bitmart-exchange-shutdown-2026","prev_score":9,"reason":"The page's core narrative -- the July 26, 2026 wind-down announcement, its timeline (trading ends Aug 26, 2026; full closure Jan 31, 2027), the BMX token collapse, Nenter Chow's termination two days before the announcement, the 2021 $196M hack, and the broader July 2026 exchange-closure wave (AscendEX, BitMEX) -- is well supported by multiple independent tier-1/tier-2 sources and holds up under verification. The most significant problems found: the On-Chain Reserve Concerns section misattributes a wallet-balance analysis to Nansen when independent reporting consistently attributes it to Arkham, and gives a $69 million post-announcement balance that several independent outlets report as $71 million (this same error is repeated in the timeline); the Industry Context section misattributes an 'over 30 crypto projects folded' figure to CoinDesk, when CoinDesk's own reported 2026 figure is over 100 and the '30' figure traces to a different analyst tracker; the claim that BitMart 'lost' FCA authorization in the UK as of October 2023 overstates what is actually an unauthorized-firm designation with no confirmed prior-authorization status; a 2025 data-breach timeline entry conflates two separate forum posts (exploit listing vs. database leak) under a single incorrect date; and the regulatory section's narrow true statement about no SEC/CFTC action omits a confirmed 2022 FTC investigation. The page is also noticeably stale on the fast-moving reserve story: independent reporting shows continued wallet depletion past the page's July 27 snapshot and a public denial from founder Sheldon Xia, neither reflected here. No accepted community submissions exist to separately evaluate.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}