The encyclopedia · Product & Design · Product decision · 2024–2025
The Ring added an AI judge to boxing — and won Lynx's Digital Craft Grand Prix
Boxing's The Ring trained an AI on 103 years of fight data and let it score live as a '4th judge', turning judging controversy into a global data story.
The Ring
The solution
Boxing's three human judges produced endless disputed decisions, and the first Usyk–Fury fight reignited outrage. The Ring, boxing's most trusted voice for over a century, saw a chance to do more than report the controversy.
With Genosha AI it built an AI judge trained on 103 years of its own archives. Seven cameras tracked every exchange in real time; the system scored live at the Usyk–Fury rematch on December 21, 2024, its card broadcast on DAZN and TNT Sports, validated by the WBC and framed as a fourth, data-driven voice.
The AI scored Usyk 118-112 against the officials' 116-112, igniting a global debate: 158 countries, 4.2B impressions and 12.4M+ interactions. It returned for Beterbiev–Bivol and became a fixture, winning Dubai Lynx's Digital Craft Grand Prix.
Why it worked
- Positioning it as a fourth judge rather than a replacement disarmed purists and governing bodies that resist tech in scoring.
- Training on 103 years of The Ring's own data gave the AI a legacy credibility no startup could claim.
- Debuting on the year's biggest fight turned a product launch into a live global conversation about fairness.
What can be applied
To change a tradition-bound system, don't fight the institution — add a transparent voice beside it. Credibility came from the brand's century of data and WBC validation.
Aftermath
The 4th Judge kept scoring The Ring events through 2025 — including the Beterbiev–Bivol card and later high-profile fights — and its scorecards continued to feed debate. What began as a magazine's brand activation became a permanent fixture in boxing coverage.
Sources
- The Ring Magazine | 4th Judge
- The 4th Judge — Golden Drum Showcase
- How controversial AI boxing judge works as Tyson Fury brutally responds to scorecard
spotted an error? The archive wants to know.