Verify a decision

{"actor":"reviewer","decided_at":"2026-06-14T23:15:44.133Z","decision":"review","investigation_id":"4353b260-3c61-49c0-b2b6-baf8e07bd172","new_score":16,"page_slug":"cryptocom","prev_score":16,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Crypto.com is a large, legitimate, regulated exchange — not a fraudulent entity. The primary loss events driving the 28/WARNING score are a 2022 hack and a 2023 social-engineering breach, both of which were suffered by Crypto.com at the hands of third parties, and in both cases no user funds were permanently lost (users were fully reimbursed after the 2022 hack; no funds were accessed in the Scattered Spider incident). The SEC investigation that hung over the company was closed with no enforcement action in March 2025, placing Crypto.com in the same regulatory-cleared category as Coinbase, Gemini, and Robinhood. The company has since obtained the full CFTC derivatives license stack and an OCC conditional bank charter — the strongest U.S. regulatory footprint in crypto. The genuine concern is the March 2025 CRO governance incident, where management effectively overrode a 77.97% community opposition to re-mint 70 billion previously burned tokens by wielding 70-80% of validator voting power. This is a material governance controversy warranting a CAUTIONARY designation — it reflects a meaningful failure of decentralization promises and drew credible public criticism from blockchain investigator ZachXBT — but it does not constitute fraud, a Ponzi, or an exit scam under any standard definition. The CEO background note about Ensogo is a real red flag but relates to a prior company's operational failure, not Crypto.com itself. A score of 58 (CAUTIONARY) appropriately acknowledges these governance concerns and the CEO's mixed history while reflecting that this is an actively regulated, operationally sound, 150M-user exchange that makes customers whole after incidents.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}