Who Keeps the Third Umpire's Ledger? From Timed Out to Blockchain — Cricket's Review Archive and the Accountability Gap

On November 6, 2026, at the Arun Jaitley Stadium in Delhi, a Sri Lankan wicket fell and Angelo Mathews walked out as the next batter. On his way to the crease, his helmet strap snapped. He paused and gestured for a replacement. Moments later he was out — timed out, the first such dismissal in the 146-year history of international cricket. Shakib Al Hasan appealed, the umpire ruled, and Mathews walked back with zero runs.

Most of the argument that followed was emotional: who had crossed the line of the game's spirit, and who had defended it. My interest sits elsewhere. Where was the zero point of that two-minute clock written down? Who wrote it? Could anyone edit it afterwards? Television gave us replays, over and over, but never a timestamp in the corner of the frame. I started the Dhaka VAR-Log because the debate itself never bothered me as much as this: who keeps the evidence of the debate?

Start with the law. Timed out lives in Law 40 of the MCC's code. For decades the limit was three minutes; from October 2026 it was cut to two. The condition is simple to state and slippery to apply: the incoming batter must be ready to receive the ball within two minutes of the previous wicket falling. But what does ready mean? Does fixing a broken helmet strap before entering the field of play fall inside preparation, or outside the limit? Where is the clock's zero point — the fall of the wicket, the batter's arrival at the crease, or the umpire's signal to him? The law is silent there, and that silence produced the most expensive announcement of the match.

Set that beside the architecture of the Decision Review System. In one-day internationals each side gets two unsuccessful reviews per innings; a batter has 15 seconds to decide; ball-tracking governs lbw, where the on-field call survives unless at least half the ball's diameter is hitting the stumps — the familiar Umpire's Call; UltraEdge's audio trigger covers edges and catches. Some incidents are factual reviews, some are judgement reviews. The Mathews case was neither. It was a time review, and time has no review system at all.

A ball that may clip the stumps by a few millimetres gets three reviews. A clock that can change the result of a match gets none. The asymmetry tells you where cricket invested: in physics, not in administration.

To see who keeps the ledger, you have to count four hands. The MCC writes the Laws. The ICC's Cricket Committee and Chief Executives' Committee write the playing conditions and the ICC Board approves them, which is to say how much a rule flexes from tournament to tournament is a contractual question. The host broadcaster produces the footage and decides which angles the world sees. The raw ball-tracking file, its confidence intervals and the audio trigger threshold sit on a technology provider's servers. Four parties, four interests, and a single copy of the evidence — held privately.

On every disputed decision I hold myself to a limit: three decisive frames, one citation from the rulebook. Beyond that, frame-by-frame rewinding turns analysis into storytelling. In the Mathews case the frames that genuinely exist are three: the appeal, the umpire's signal, the strap being fixed. The frames that would have settled the argument — the clock's zero point, the moment the umpire signalled the batter, the seconds elapsed after the repair — do not exist in public at all.

This is where blockchain becomes a serious question rather than a slogan. A hash-chained, append-only ledger is easy to describe: every entry carries a fingerprint of the entry before it, so altering one entry mid-chain breaks the chain and exposes the edit. Timestamp proof is not new technology. The problem is administrative, not computational.

A ledger can prove when something happened. It cannot prove that what happened was fair. In Delhi a ledger could have shown the exact second the previous wicket fell, the exact interval before the umpire's signal, the exact delay before Mathews was ready. But where the two minutes begin would still have been a human reading, open to interpretation. Technology does not erase ambiguity; it marks the location of it.

Cricket's actual blockchain experiment went to the wrong market. In 2026 FanCraze signed a multi-year digital collectibles deal with the ICC, selling moments from ICC events as limited-edition assets, and raised a $100 million Series A that same year. Rario-type platforms tied themselves to boards and leagues. Then the global NFT market collapsed across 2026 and 2026 and the companies cut staff. The industry turned a 2026 World Cup catch into a scarce digital asset, and left the mechanism of a decision un-audited.

I read that as an incentive failure rather than a technological one. Blockchain's real value in cricket is not scarcity, it is auditability. If a highlight can be hashed, a review log can be hashed — and the social value of the second is many times the first.

Then there is the philosophy of Umpire's Call. When the ball is projected to hit the stumps with less than half its diameter, we keep the human decision. That is an admission: the machine is more precise than the human, and the game is unwilling to carry that precision. A public ledger would produce years of rows in which the machine says clipping and a human call decides a team's fate. The ledger would not close that gap; it would give the gap an address.

Time is also an administered object. Over-rate sanctions work off an average — a required rate of overs per day, smoothed across a long passage of play. An average erases the distribution. Which side delays, in which phase, under which conditions, whether the delay suits the fielding captain — none of that reaches a ledger. This is the part of the argument I find most concrete. During the empty-stadium period of 2026 I audited 1,840 penalty-area incidents across leagues. With crowds absent, the home-team penalty rate fell from 0.31 to 0.22 per match and added time rose by 1.4 minutes. Nobody's character changed; the environment did. Cricket's over-rate debate deserves the same reading — who delays, how often, and whose advantage the delay serves.

The human consequence should not be lost either. Mathews walked back for zero, Sri Lanka's innings broke on that jolt, Bangladesh won the match. The larger change happened in the argument itself. Within a week nobody was asking whether the strap had really snapped; everyone was asking whether the law should exist. A ledger would have accelerated that shift, and made it colder.

Here I part with the conventional wisdom that transparency produces calm. European football's armpit offside teaches the opposite. Pixel-level proof arrived and the anger grew, because the anger was never about a toe. Cricket's public tolerance for Umpire's Call survives partly because it hides the machine's precision. Publish a complete log — names, timestamps, confidence ranges — and two things follow. Collective frustration with the umpires fractures into timestamped anger at named individuals, which is a new phone line for abuse. And the argument migrates from fact to philosophy, which is where reform of Law 40 actually has to happen.

The second trap is structural rather than technical: the permissioned ledger. If the ICC writes the chain, signs the chain and audits the chain, then immutability means only that nobody but the author can write to it. A single-writer ledger is not accountability; it is a press release wrapped in cryptography. For the word to mean anything, an independent verification node has to sit outside — with the MCC, or with the member boards.

So who writes, who signs, who verifies? The MCC writes the Laws. Playing conditions travel from the ICC Cricket Committee to the Chief Executives' Committee, with final approval at Board level. The host broadcaster selects the evidence. The technology provider holds custody of the raw tracking data. Four doors, one key to the evidence, and nobody says clearly whose pocket it is in.

My proposal is narrow and practical. Call it the ICC Officiating Data Minimum. Within 24 hours of every televised international, publish a hash-anchored review log: the clock's start timestamp, the angles reviewed, the confidence range on the tracking data, the audio trigger threshold, the final decision, and the law cited — under the match referee's digital signature. The point is not to change decisions but to leave them verifiable, so that a referee's report and a fan's opinion are different categories of document.

I know this will not reduce the pressure on third umpires. It will do the reverse: decisions that used to hang in the air as the system's fault will acquire an address. But reform does not happen without addresses. Complaints have been circulating for years between Dhaka, Dubai and the broadcast booth precisely because nobody owns the paperwork.

One question stays open. If the clock's zero point remains a human judgement, a ledger will only prove how uncertain we were at the exact moment we claimed to be certain. Once the record is verifiable, will anyone be willing to rewrite the first sentence of Law 40 — that the incoming batter must be ready? Or will we simply accumulate better evidence and leave the rule untouched?