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 · Loopring
- Sequence
- #2
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 426514480
- Off-chain at
- 2026-06-14T23:15:58.519Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8tzKv7qMEzmCuUDxqx4Gjhfb5SLjv8GauMcZhAo8WP2Z
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2004 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:15:58.476Z","decision":"review","investigation_id":"15b3c909-e064-48fc-a855-ee546aee8fff","new_score":32,"page_slug":"loopring","prev_score":32,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Loopring is a legitimate Ethereum Layer-2 zkRollup DEX protocol with real technical infrastructure independently verified by L2Beat ($8.35M TVL, Stage 0 ZK Rollup classification, live as of June 2026). The primary incident driving the WARNING band — a $5M hack in June 2024 — was suffered by Loopring users when an external attacker compromised Loopring's Official Guardian 2FA server; the page's own summary explicitly frames this as an external attack, not fraud by the entity. No evidence of fraud, Ponzi mechanics, exit scam, or regulatory enforcement action was found across multiple independent searches. The company's subsequent product shutdowns (consumer wallet, DeFi services) and CEO resignation are consistent with a project in a difficult transition pivot to L3 DEX infrastructure, not a fraudulent wind-down. Exchange delistings (Upbit, Bithumb, Binance) were driven by business sustainability and disclosure concerns. Under the post-policy band semantics, a score of 32/WARNING is over-penalized: the entity belongs in CAUTIONARY (50-69) reflecting legitimate operations with material caveats — a real security incident affecting users, significant declining TVL ($8.35M), major exchange delistings, leadership turnover, and an unproven strategic pivot — but none of these constitute evidence of fraud or deception by Loopring itself. A score of 54 is appropriate: comfortably within CAUTIONARY, reflecting the serious operational challenges while correctly not treating a hack-victim incident as fraud.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}