Verify a decision

{"actor":"judge","decided_at":"2026-06-14T23:16:01.082Z","decision":"review_approve","investigation_id":"9d227bdb-3345-4be5-aa9a-d03dcf819c80","new_score":57,"page_slug":"zksync","prev_score":38,"reason":"This was a severity-calibration review, not a content dispute. All six claim_findings[0–5] are supported, and disputed_pct is 0%. The review establishes that ZKsync's current score of 38 (WARNING band) is miscalibrated: the April 2025 airdrop exploit affected only unclaimed reserve tokens — core user funds were never at risk — and ~$5.7M was recovered under a safe harbor agreement (claim_findings[1]). The Upbit price surge was caused by third-party market manipulators on a separate regulated exchange with no operational link to ZKsync (claim_findings[2]). The X account compromise was a phishing attack on delegated accounts, making ZKsync the victim (claim_findings[4]). The BANKEX lawsuit remains unresolved and denied (claim_findings[3]), and the entity is backed by credible institutional investors with no fraud conviction or exit-scam mechanics (claim_findings[5]). WARNING band is reserved for entities with elevated fraud/loss risk or unresolved severe incidents attributable to the entity itself; ZKsync fits CAUTIONARY (50–69). A score of 57 reflects the legitimate caveats — unresolved IP suit, two operational-security failures in one month, ecosystem engagement decline — without penalizing the entity for incidents it suffered. The page content is accurate and must remain published.","score_delta":19,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}