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 · Bitget
- Sequence
- #5
- Score
- 38 → 52 (+14)
- Cluster
- mainnet-beta
- Slot
- 426514797
- Off-chain at
- 2026-06-14T23:16:14.717Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 3LH3EQAvoW1ZzQvrykDPwBP9cJoG5dbR7enGBVALeKcE
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1462 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:14.609Z","decision":"review_approve","investigation_id":"1297716a-0f85-4f49-905d-8e9cddae14b8","new_score":52,"page_slug":"bitget","prev_score":38,"reason":"Severity-calibration review found 0% disputed claims — all six claim_findings[0–5] returned 'supported.' Bitget is a legitimate large-scale exchange (ranked 6th globally, 120M users, no direct hack on record, AA CER.live safety rating) whose WARNING score of 38 was driven by two categories of incident that do not support that severity band. First, the multi-jurisdiction regulatory warnings (France AMF, Australia ASIC, Philippines SEC, Japan FSA) were applied simultaneously to peer exchanges Bybit, OKX, KuCoin, and MEXC — they reflect a sector-wide offshore licensing gap, not Bitget-specific fraud. Second, the VOXEL April 2025 incident (claim_findings[4]) was caused by external exploiters, not Bitget; the company responded with trade rollbacks, fund compensation, and legal action. The unresolved ZachXBT May 2026 allegations (claim_findings[5]) allege enablement, not direct perpetration, and remain unconfirmed. CAUTIONARY (score 52) is the correct band for a legitimate operator with material but unproven governance caveats. Page content stands as accurate and is approved with a +14 score correction.","score_delta":14,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}