The Decision Ledger: Who Owns Cricket's Review System, and Can Blockchain Change It

Hook

At the Sher-e-Bangla National Stadium in Mirpur, the 18th over was underway. The spinner released, ball struck pad, a slip fielder screamed, and the umpire did not raise a finger. What followed was no longer cricket — it was protocol. A message rose on the giant screen, six icons lit up in the third umpire's room, and the entire stadium hung in silence for three minutes and twelve seconds.

What the crowd saw in those minutes was a verdict. What the crowd never saw was a six-step chain: the camera frame, the camera calibration, the tracking algorithm version, the threshold, the third umpire's voice, and the match referee's report. I wrote the time in my notebook and added two lines: nobody showed me which frame confirmed the ball hit the stump; nobody told me which software build was running.

I went back to the Rajshahi touchline to see what the cameras missed. There I saw other things: the umpire's foot position, his distance from the wicket, the tremor in his hands under pressure. Blockchain will not erase that tremor. But every decision node inside those three minutes can be marked indelibly — and that is the subject of this piece.

Context

The Decision Review System entered international cricket in 2026, in the India–Sri Lanka Test series in Colombo. It was experimental then; today it is a mandatory part of ICC flagship events. The system rests on several layers: ball-tracking, sound-based edge detection, in some cases thermal imaging, and the third umpire's display software. Hawk-Eye's ownership passed to Sony in 2026 — meaning the core tracking technology is the property of a commercial firm, not a cricket board.

Two thresholds generate most of the argument. The impact threshold: if the ball strikes the batter more than three metres from the stumps, the on-field call stands. The projection threshold: if less than half the width of the ball is hitting the stumps, it stays Umpire's Call.

Here is the real question. Umpire's Call is ultimately an output of software whose internal algorithm is closed and whose version notes are never published. When the on-field umpire rules, the basis is the human eye, angle and conviction. When the third umpire rules, the basis is 50 to 90 seconds of computation, synchronisation across four to six cameras, and an interface. Two completely different pathways, the same three-word vocabulary.

In my twenty-four years of watching the game, spectators rarely rage at error. They rage at opacity. People tolerate mistakes, not the absence of explanation. Most of the VAR controversies I covered as a commentator were about the curtain, not the verdict. Cricket now stands at the same junction.

Consider one fact: franchise leagues move enormous money and betting markets reprice by the second, yet the data behind a no-ball or a review sits on a few private servers with no public hash. Those two realities cannot coexist indefinitely.

Core Analysis: Six Nodes of the Decision Chain

Node one, capture. At what frame rate is the ball-tracking camera running — 50, 100, higher? A higher frame rate changes bounce and deflection projection. I have seen the same delivery appear in different places on two broadcast feeds. What must be recorded immutably here is the camera configuration, the synchronisation lag, and a hash of the calibration certificate used for that match. This is the easiest and most valuable addition a ledger can make.

Node two, transmission. Which feed reached the third umpire's room, at what latency, on which monitor. None of this is logged today. After a match it is lost forever, even though it is exactly the evidence needed in a fixing investigation.

Node three, interpretation. Ball-tracking draws a future path — a mathematical estimate built on assumptions about bounce, spin, air density and pitch friction. Change the model version and the answer changes. The frame rate changed, but the referee — the technology shifted, the burden of the decision never did. The weight once carried on an umpire's shoulders is now wrapped in a software package, with the same human inside.

Node four, threshold. Where exactly does Umpire's Call begin, what is the impact limit, what does half the ball mean. Publishing these definitions before the match, with an immutable version history, would recover much of the crowd's trust. The ledger's job is not to write the law but to preserve the law's edit history.

Node five, communication. The third umpire's voice reaches the on-field umpire by one channel and the broadcast by another, and a few seconds can open between them: the screen shows out while the umpire is still waiting. That gap is itself data, and nobody keeps it.

Node six, governance. The referee writes a report, umpires are assessed, third umpires are dropped or retained — all internal. This is the widest gap. Who audits the auditor? A ledger cannot answer that question, but it removes the option of pretending the question does not exist.

Now imagine a Merkle root published at the end of each match — a single hash summarising the existence of every decision node. Any journalist or scout could later verify whether the camera configuration changed, whether the algorithm build matched the previous match, and how many consecutive hours the third umpire had been on duty.

That last item matters most to me. My work on the Referee Load Index after the 2026–21 empty-stadium period taught one lesson clearly: a tired official decides differently. In football, the fall in home-win rates without crowds pointed to environment; in cricket, the shift in third-umpire outcomes late in long tournaments points to fatigue. Fatigue is measurable, recordable, and can sit on a ledger.

The same logic extends to player movement. Transfer rumours are fouls waiting for a replay. In an auction cycle where crores change hands, contract terms, payment schedules and player registrations sitting on one ledger would make anti-corruption work far simpler. Smart contracts can automate instalments and conditions — but they clarify the path of money, not the path of a decision. Cricket needs both.

Contrarian Angle: Blockchain Relocates Controversy, It Does Not Remove It

When DRS arrived, nobody claimed controversy ended. The claim was that pressure was redistributed — from the umpire's shoulders to the third umpire's room. Blockchain will do exactly the same. Three branches matter.

First, the custodian problem. If the ICC or the broadcaster runs the chain, it is not a public ledger; it is a private ledger with a public face. Anyone can verify a hash, nobody can inspect the algorithm. Trust migrates from the umpire to the vendor. That is not safer. When a supporter was angry at an out, they used to curse the umpire; tomorrow they will curse the technology company.

Second, risk aversion. The more logging, the more accountability — and the more defensive the decision. An umpire who knows every call is permanently recorded will, in a moment of doubt, push the decision toward Umpire's Call. Technology may make decisions less accurate by making them more hesitant. Football's early VAR years showed precisely this.

Third, the player and the spectator. A batter who stands for ninety seconds staring at a screen is not experiencing cricket; he is experiencing waiting. A bowler who beats the edge and gets no wicket must bowl again — that physical and mental cost appears on no ledger. And think of the umpire back on the Rajshahi touchline, keeping time in the background. His gesture will never be captured by a hash. Not everything is a node. Some things remain human.

My objection is not to the technology but to its monopoly. Cricket's problem is not the absence of a blockchain; it is the absence of transparency — and here is a concrete fact worth citing: two reviews per innings apply equally to Bangladesh, India and Australia, yet the commercial accounts behind the underlying technology remain private.

Takeaway

Before the 2026 ICC Men's T20 World Cup, a pilot decision ledger could run on three conditions. Publish the algorithm's version history, so that every definitional change since the 2026 threshold adjustments is dated and immutable. Commission independent third-party calibration audits and publish their certificate hashes before the match. And cap the third umpire's duty load, recorded on the ledger, so a sixth consecutive day of work stops being a matter of guesswork.

I publish predictions before matches so they can be graded later. A ledger needs the same discipline: write the conditions before the verdict, so no explanation is needed afterwards. If the reasoning behind each frame is stored at the end of the second rather than the end of the day, pressure in cricket will not disappear — it will simply stop hiding.

One question stays with me. When the third umpire finally ruled, and the screen told everyone, what was the batter actually looking at — the pad line, not the sticks. What happens if we place one additional camera angle between those two viewpoints. That is the first test for the next ledger.