Skip to main content
Sign in
← 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.

Decision
review · Bitget
View on Solana ↗
Sequence
#4
Score
38 → 38 (0)
Cluster
mainnet-beta
Slot
426514794
Off-chain at
2026-06-14T23:16:14.656Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
CjTV4p2dooB4YjK6yMCMz1FxFVRUgULTdLPfY5bTgBVD
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2201 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:14.609Z","decision":"review","investigation_id":"1297716a-0f85-4f49-905d-8e9cddae14b8","new_score":38,"page_slug":"bitget","prev_score":38,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Bitget is a legitimate, large-scale cryptocurrency exchange (120M registered users, ranked 6th globally by CoinGecko, $300M+ proof-of-reserves protection fund, AA CER.live safety rating, Forbes top-8 trusted exchanges) that has never been hacked. The incidents driving its WARNING score fall into two categories: (1) licensing non-compliance in France, Australia, Japan, and the Philippines — regulatory failures that simultaneously applied to Bybit, OKX, KuCoin, Kraken, and MEXC and therefore represent a sector-wide compliance gap rather than fraud-specific behavior; and (2) the April 2025 VOXEL bot flaw, in which 8 external accounts exploited a system vulnerability while Bitget responded with rollbacks, compensation from its protection fund, and legal proceedings against the exploiters. The most serious unresolved issue is ZachXBT's May 2026 allegation that Bitget knowingly enabled market-maker supply-control schemes — a credible on-chain-based allegation by a respected investigator, but currently unconfirmed allegations rather than proven fraud, with Bitget characterized as an enabler rather than perpetrator. Under the post-policy band semantics, a score of 38 (WARNING) requires 'elevated fraud/loss risk or unresolved severe incident'; the correct band is CAUTIONARY (50-69) for a 'legitimate operator with material caveats,' with the score set at 52 to weight the unresolved ZachXBT governance allegations meaningfully without treating unconfirmed allegations as confirmed fraud. An outside skeptic can verify the regulatory actions at official AMF, ASIC, and Philippines SEC URLs; verify VOXEL remediation in The Block; and verify ZachXBT's allegation framing in CryptoTimes and Bitcoin.com News.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}