Decision Without Proof: The Invisible Gap in Cricket's Review System and the Case for an Immutable Ledger

On 14 July 2026, at Lord's, the World Cup final between England and New Zealand finished level at 241 apiece, and the Super Over finished level too. The trophy was decided on boundary count: England 26, New Zealand 17. It was the first time the clause had been applied in a World Cup final, and many people inside the ground — including several commentators — were not certain of the exact wording. I remember that night for a different reason. The fate of the match was settled by a stream of information whose verification chain nobody had ever audited. Cricket's decision architecture sits precisely here: data that looks immaculate, with no immutable ledger behind it.

The Decision Review System was first used in 2026, in a Sri Lanka–India Test. Ball-tracking, UltraEdge and the third umpire's screen form the three pillars of the modern review. The system entered the World Cup stage in 2026, and a side gets two reviews per innings in a Test or ODI; a successful one is retained. The ICC's playing conditions require 'conclusive evidence' to overturn an on-field decision. Umpire's Call survives in ball-tracking because Hawk-Eye carries its own margin of error; at least 50 per cent of the ball must be hitting the stumps. In June 2026, the ICC abolished the soft signal after years of argument.

Every review produces an information point: the frame at which the ball pitched, where impact occurred, what percentage of the stumps was struck. By volume, cricket is far ahead of football — a single Test records the speed, spin axis and pitch map of thousands of deliveries. But being recorded is not the same as being verifiable. Data the public cannot reach is, in effect, non-existent. What each review generates is never stored in a public, time-stamped, tamper-evident ledger.

The VAR crisis I saw while tracking 29 reviews at the 2026 World Cup in Russia casts a deeper shadow in cricket, because there is more data here and less transparency. Why is a blockchain valuable? Because every transaction is time-stamped, chained, and impossible to alter without detection. Cricket's officiating system lacks precisely that property.

My central argument is blunt: the real source of controversy in cricket is not accuracy, it is verifiability. The error is rarely in the pixel; it is in the premise.

Consider how a review works. Ball-tracking draws a probable path, the third umpire watches it, and a result appears on the scoreboard. The question is whether the same threshold is applied in the third over and the forty-seventh over for the same pitch, impact and stump coverage. Nobody can answer, because none of it is logged. Where there is no ledger, fairness cannot be measured.

The 2026 boundary-count episode is the perfect illustration. The rule was written before the match, but nobody tested it in live conditions before the final. The information point was created at the exact moment there was no way back. Ben Stokes's overthrow, Martin Guptill's Super Over run-out, Kane Williamson's captaincy — all remain in history; the result was decided by an unaudited clause.

The heaviest damage falls on Umpire's Call. Same ball, same pitch — out one time, not out the next. The crowd reads it as injustice. In truth, the problem is not unfairness but the absence of audit. Had every review's data, threshold and timestamp sat in a public ledger, spectators could have verified for themselves whether consistency held.

This is where the idea of blockchain becomes relevant. Its power is not cryptocurrency — it is interpretability and immutability. Suppose the ICC ran a 'decision ledger': every review's sensor data, Hawk-Eye's probable path, the third umpire's decision, published in time-stamped form and impossible to alter afterwards. Two things would follow. First, umpires would gain protection, because the public would see the process and not merely the outcome. Second, the system's weaknesses would surface on their own.

A comparison makes it plain. At the 2026 World Cup in Qatar, semi-automated offside technology pushed a 3D model to broadcast within seconds, letting viewers see for themselves why a decision was given. In cricket, the ball-tracking model stays behind the screen. That gap in transparency creates the gap in trust.

Accountability matters too. When a review is disputed, who is responsible — the on-field umpire, the third umpire, or the technology provider? No one takes full responsibility, because no one releases full information. This blurred accountability keeps the controversy alive.

The instinctive response is more technology and more accuracy. I would argue the reverse. Over fifteen years cricket's technology has multiplied several times over; the controversy has not shrunk. Technology improves accuracy, not verifiability. The problem has migrated from the umpire's eye to the definition of the threshold — and that definition has never been opened to the public.

I accept that cricket cannot return to a pre-technology era, and that Hawk-Eye has broadly moved the game in the right direction. I would not argue for scrapping the review system. I am arguing that the cost is being paid in transparency. I would change my position if someone could show that the same threshold has been applied consistently in every over — but for that, the evidence must first be preserved.

The way forward is clear. Cricket should build a public, time-stamped decision ledger in which every review's data is permanently stored, verifiable and tamper-evident. This is not a mechanism for punishing umpires; it is a mechanism for protecting them. The question is no longer 'is the technology right?' It is 'is the decision verifiable?' Until that is answered, cricket's results will not be free of dispute.