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_approve_with_notes · Bit.com
- Sequence
- #5
- Score
- 42 → 56 (+14)
- Cluster
- mainnet-beta
- Slot
- 443509243
- Off-chain at
- 2026-08-19T04:00:07.954Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 97QeA5hFuNN42mQqmYVNaV9H61Mc4kSxsHTLaB6fcaJW
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2168 chars)
{"actor":"judge","decided_at":"2026-08-19T04:00:07.574Z","decision":"review_approve_with_notes","investigation_id":"cc3fbcec-6e6a-4760-96d9-3cb179d61864","new_score":56,"page_slug":"bit-com","prev_score":42,"reason":"Every claim the reviewer independently checked held up: launch history, corporate structure, the phased wind-down timeline, the Matrixport-to-BIT rebrand figures, and — most importantly for the score — the absence of any regulatory action, hack, exit fraud, or misappropriation tied to Bit.com's closure (claim_findings[0-3,5-8,12-13], disputed_pct 0.2 driven entirely by link_rot/unverifiable, not by contradiction). A current score of 42 (WARNING) implies own-entity fraud or negligence that no source reviewed supports; the wind-down was voluntary, disclosed, phased, and paired with an explicit no-confiscation commitment. That said, VERIFIED is not earned either: the exchange never published proof-of-reserves, one of the two SLA-commitment sources has gone dark (claim_findings[4]), and — per coverage_gaps[0] — no post-deadline reporting exists on whether backup-station recovery actually worked roughly 4.5 months after the March 31, 2026 deadline. That is a live, unresolved custody caveat, not a resolved clean record, which is exactly what the CAUTIONARY band (legit with caveats) is for. Notes: (Replace or archive-link the dead helpcenter.bitexch.io SLA source (1hr/2hr response commitments) — currently unverifiable from a live source.) (Replace or archive-link the dead mexc.com/news/358004 source backing the 51% YoY volume-decline figure.) (Add coverage of post-March-31-2026 outcome reporting (Trustpilot/Reddit/X complaints, successful vs. stuck recoveries) before the next review pass — this is the single highest-value gap per the reviewer.) (Confirm or drop the bitex.com/BCSC sub-claim, which currently has no cited source at all.) (Consider noting FX Empire's low third-party trust ratings (Cer.Live D, CryptoCompare C) alongside the 'clean security track record' claim for balance.)","score_delta":14,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}