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 · Bitget Exchange (Shawn Liu)
- Sequence
- #3
- Score
- 42 → 34 (-8)
- Cluster
- mainnet-beta
- Slot
- 443505668
- Off-chain at
- 2026-08-08T03:02:07.906Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AZQ1etCpQDRxMQrwekfpofJ3raWQmfBx7Z3EaEZ2GnFS
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1641 chars)
{"actor":"judge","decided_at":"2026-08-08T03:02:07.691Z","decision":"review_revise","investigation_id":"3d4730c1-4369-4e11-80d9-494b6fb43800","new_score":34,"page_slug":"bitget-exchange-shawn-liu","prev_score":42,"reason":"The page is accurate on its highest-stakes claims — the ZachXBT/LAB token investigation, VOXEL incident mechanics, and six-jurisdiction regulatory warnings are all confirmed by Tier 1 and Tier 2 sources. One clear factual error was identified: claim_findings[27] places the India onboarding pause on February 6, 2025, but multiple independent sources including Bitget's own support documentation place it on February 6, 2026. Three further claims are partially supported but overstated — BGB's 2024 price gain is reported as 'over 1,000%' by the page while most credible sources report approximately 900% (claim_findings[3]), copy trading user figures are materially understated relative to current platform data (claim_findings[2]), and the Protection Fund's $716M figure is described as a high-water mark despite being exceeded in subsequent months (claim_findings[25]). These are revisions to factual precision, not challenges to the page's core risk characterizations. Three high-priority coverage gaps — the absence of a regulatory enforcement vs. investor alert distinction, no independent on-chain BGB supply analysis, and no verified corporate structure for Bitget's holding entities — represent material expansions that would strengthen the page's evidentiary basis.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}