Verify a decision

{"actor":"judge","decided_at":"2026-08-25T17:24:22.966Z","decision":"review_revise","investigation_id":"6269bb42-c37e-4361-a723-04ab3cc5f416","new_score":0,"page_slug":"harmony-protocol-one-token-unauthorized-mint-exploit-august-2026","prev_score":8,"reason":"The review confirms this page's technical reporting is solid: the cross-shard receipt vulnerability, the emergency patch, and the GitHub PR/commit hash all match primary sources exactly (claim_findings[6], claim_findings[7]), and the page correctly avoids attributing the 2026 exploit to the Lazarus Group despite that attribution belonging only to a separate 2022 incident (claim_findings[20]) - a distinction two comparable pages in this batch got wrong. However, the page's central numbers are now materially misleading to a current reader. It reports approximately 4 billion ONE minted (about 26% of supply, claim_findings[1]), while later reconstruction found the true forged total was 2.385 to 3.01 trillion ONE - roughly 600 to 750 times larger - which also undercuts the derived exchange-inflow and dollar-value figures (claim_findings[2], claim_findings[9]). The page still describes a blockchain rollback as merely 'pending' (claim_findings[13]); Harmony has since actually executed a rollback of two shards, discarding over 109,000 transactions. These numbers were accurate as of the sources the page drew on (Aug 12-13) and are correctly labeled by the reviewer as superseded rather than factually disputed, but because they sit at the core of the page's story and are still presented as the current picture, the page substantially understates the scale and status of the incident today. A separate citation for a December 2023 staking bug points to an article that never mentions that event at all (claim_findings[19]), a distinct sourcing error. The mechanical disputed-claim rate (about 9%) does not capture this because these are 'stale' rather than 'disputed' findings, but the review's own high-priority coverage gap on this exact point, combined with how central and how large the gap is, means the page needs a mandatory update and closer monitoring rather than a routine pass.","score_delta":-22,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}