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 · Gate.io
- Sequence
- #4
- Score
- 30 → 30 (0)
- Cluster
- mainnet-beta
- Slot
- 426514324
- Off-chain at
- 2026-06-14T23:15:50.229Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7nKxcoBqBnSQT4TgVz4ZydVBDHe9YJDNoV1SiCZupaS6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2230 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:15:50.178Z","decision":"review","investigation_id":"ba1440aa-37bd-4263-9369-af270f4a4a8d","new_score":30,"page_slug":"gateio","prev_score":30,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Gate.io (now Gate.com) is a legitimate, top-5 global cryptocurrency exchange founded in 2013 with over 27-50 million users and active regulatory licenses from VARA (Dubai), MiCA/MFSA (Malta), CySEC, and AUSTRAC. The incidents driving the WARNING score are predominantly third-party attacks: the 2018 $234M Lazarus Group hack was a nation-state cyber attack against Gate.io, not a fraud committed by Gate.io; the 2018 StatCounter incident was a third-party supply-chain attack targeting Gate.io's users via an external analytics vendor; and the 2019 ETC loss was caused by a blockchain-level 51% attack on Ethereum Classic, for which Gate.io compensated users. The $LA futures incident (June 2025) involved a price feed infrastructure failure for which Gate.io paid $30M+ in compensation — consistent with operational negligence, not intentional fraud. The CIMA notice is a real and material concern (misrepresentation of regulatory domicile), and withdrawal freeze complaints are sustained and credible. However, no confirmed fraud, exit scam, Ponzi mechanics, or criminal conviction exists. Under post-policy-decision band semantics, the WARNING band (20-49) is reserved for elevated fraud/loss risk or unresolved severe incidents; a CAUTIONARY band (50-69) covering legitimate operators with material caveats is more appropriate given Gate.io's active multi-jurisdiction licensing, consistent proof-of-reserves (115-123% ratio, Hacken-audited), and status as a hack victim rather than fraudster. A score of 57 reflects the real concerns — CIMA misrepresentation, sustained withdrawal complaints, non-disclosure of the 2018 hack, and the $LA futures failure — while correctly not penalizing the exchange for being the victim of external attacks.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}