Verify a decision

{"actor":"judge","decided_at":"2026-06-15T00:11:56.955Z","decision":"review_approve","investigation_id":"25a63bee-d211-406a-87b5-7f88d5de2606","new_score":20,"page_slug":"verus-protocol-ethereum-bridge","prev_score":20,"reason":"The reviewer examined 24 claims and found 18 confirmed, 3 partially supported, 1 unverifiable, and 1 disputed, yielding a disputed_pct of 8.3% — within the 0–10% approval band. The sole disputed finding (claim_findings[22]) concerns the dates of co-occurring third-party incidents cited for context: the page states that THORChain and Echo Protocol were exploited on the same day as Verus (May 18), but Tier 1 sources place the THORChain event on May 15 and the Echo Protocol event on May 19. This is a factual error in a peripheral contextual section, not in the core exploit narrative. All material claims — exploit date, amount, asset breakdown, root cause (checkCCEValues input/output gap), attacker wallet, Tornado Cash seeding, bounty terms, and fund recovery — are confirmed by Tier 1 sources. The Toutonghi title misattribution ('Technical Fellow' vs. 'Distinguished Engineer' at Microsoft) is a minor biographical detail that does not affect the investigation's integrity. Two high-priority coverage gaps remain open (no Verus team post-mortem, no GitHub audit trail check), but open gaps indicate expansion opportunities, not grounds for denial.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}