The Third Umpire's Ledger: Cricket's Review System, the Transparency Deficit, and the Case for Ledger Logic

Hook — Two Millimetres and an Invisible Ledger

Two millimetres. On the giant stadium screen the ball-tracking graphic creeps forward, the projected path clips the inner edge of leg stump, and a line appears: 'Umpire's call — decision stands.' Thirty thousand people exhale together, the commentator says 'by a hair,' and three seconds later the graphic dissolves into an advertisement.

The crowd saw a projection. It did not see how many cameras fed that projection, how many frames per second were captured, who issued the calibration certificate for the venue, whether an operator nudged a boundary point by hand, or what was said inside the third umpire's room before the verdict. I began with 1,058 incidents, and the anomaly was hiding in plain sight: we watch the technology's decision, never the technology's ledger. The habit of counting was built at a Sylhet sports desk in 2026, logging penalty-area incidents in football; after 2026 I carried it into cricket, because a review is not one decision but a stack of decisions, and the last layer of that stack is never published.

Nobody in cricket talks about distributed ledgers seriously, because everyone assumes blockchain means fan tokens and NFT trading cards. Yet the parts of this game that generate the loudest arguments — reviews, no-objection certificates, age verification, anti-corruption investigations — each rest on one question: who keeps the ledger, and who is allowed to read it.

Context — 2026 to 2026: The Technology Arrived, the Ledger Did Not

Hawk-Eye entered cricket in 2026 for Channel 4's coverage in England. It was a broadcast garnish then — a visual aid for commentary. In 2026, during India's Test tour of Sri Lanka, the Decision Review System was first used in a match, which meant decisions themselves were handed to the technology. In 2026 Sony acquired Hawk-Eye, moving ownership of ball-tracking into a private company whose relationship with the ICC is a licensing arrangement, not an audit relationship. In 2026 the ICC made DRS mandatory across Tests and ODIs. UltraEdge arrived in between, replacing the older Snickometer.

Look at the architecture. Each team gets two unsuccessful reviews per innings, retained if a review succeeds. In the lbw context, if the projected path clips the inner edge of the stumps — meaning the model says less than half the ball is inside the stump line — the on-field call stands: 'umpire's call.' Here is the first fracture. Umpire's call is not a truth claim; it is a decision rule. The ICC's minimum broadcast standards set floors for camera numbers, angles and frame rates. But who verified that those floors were met, with what record, is nowhere published. Whether raw tracking data is stored after a match, for how long, and who may inspect it, is not written down anywhere either.

On 6 November 2026 in Delhi, that gap surfaced on the boundary between law and technology. In the Bangladesh–Sri Lanka World Cup match, Angelo Mathews's helmet strap broke, he was not ready within two minutes, Bangladesh captain Shakib Al Hasan appealed, and the third umpire ruled him timed out — the first such dismissal in international cricket. The decision did not come from technology; it came from the law book. The 2026 MCC code had cut timed out from three minutes to two, and no player was consulted on who wrote that amendment or why. The rulebook gave me a verdict; the freeze-frame gave me a question.

— Root: Delhi, 6 November 2026 | Scenario: the incident that proved cricket's deepest decision crisis belongs to lawmakers, not machines.

Core — Four Layers Where Transparency Stops

Layer one: 'Umpire's call' is a confidence band, not a statement of fact.

Ball-tracking captures a handful of positional points, then applies a physics model — friction, bounce, pitch behaviour, air resistance — to project the rest of the path. That projection carries a confidence interval. Umpire's call is another name for that interval. The line on the screen is not a measurement; it is a probability. Two millimetres of projection does not mean the ball struck the stump at two millimetres. It means the model's most likely path puts the ball in that region, with uncertainty too wide to overturn the umpire. Commentary blurs this. The commentator says 'the ball is clipping,' which sounds like a factual claim, and the audience memorises it. When a similar projection overturns a decision in another match, the audience feels cheated — because it was told the ball was clipping, not that the model's likely path was clipping within a stated uncertainty band. The real transparency deficit is not in the data; it is in the translation.

Layer two: private ownership of the data, public consumption of the verdict, and no auditor.

Football has pushed this conversation further. At the 2026 World Cup, semi-automated offside used twelve additional cameras and an inertial sensor in the ball sampling at 500 Hz, and FIFA published a component-level explanation. Even there, opacity survives at the final step: nobody hides the algorithm, but nobody publishes its fine settings either. Cricket's problem is steeper. The tracking company is a commercial entity; its relationship with the ICC and member boards is contractual. Broadcasters get graphics and decisions, not raw data. Chipped-ball trials in franchise tournaments have generated in-ball signals, but where those raw files go, who sees them, how long they are retained — none of it is public. Watching matches from 2026 onward and logging review moments, I noticed a pattern: over two days at the same venue in the same series, the apparent projection margins shift, and nobody says whether the camera setup changed. I cannot prove there is an error inside the technology. Because the information is withheld, I am also denied the chance to try. That is the genuine collision between commercial confidentiality and auditability.

Layer three: the review integrity ledger — what a hash chain actually solves.

The point of ledger technology is not tokens; it is timestamping. Every event generates a cryptographic hash, each hash is chained to the previous one, and altering any entry breaks the chain visibly. Applied to cricket, this needs no disclosure of proprietary source code. Suppose each match produced a Review Integrity Ledger recording four things: the hash of the venue calibration certificate; the sensor frame count with timestamps; the operator intervention log showing who manually adjusted which boundary point; and the final decision with its reason code. What stays out of the ledger is the internal formula of the projection model. After the match, anyone could verify that the raw inputs were not altered later — while the projection method remains company property. The split matters: here the ledger is used not to break confidentiality but to place a verifiable seal outside it. Technically, zero-knowledge proofs could let a provider demonstrate data integrity without exposing the data. The question is why nobody has proposed it.

Layer four: beyond reviews — NOCs, age verification and corruption inquiries need the same book.

Cricket's least-discussed crisis sits outside the review system. In Asian franchise cricket, the windows of the Bangladesh Premier League, Lanka Premier League, ILT20 and Pakistan Super League overlap. Which board issued which clearance, for how long, and whose claim wins when a central contract collides with a franchise deal, currently lives inside emails and PDFs. There is no central, timestamped, mutually visible NOC registry.

— Root: The Silence Dataset | Scenario: when the 2026 league shutdown emptied stadiums, the absence of timestamps and documents became the loudest witness of all.

Age verification is the clearest case. In Asian age-group cricket, the reliability of birth records has been questioned for years, and remedies have been sought in bone-scan testing — a probability generator, not proof. The most effective age verification is administrative, not technological: a cumulative, centrally verifiable record from birth registration onward, with a timestamped responsibility at each step. What no single party can alter is what becomes credible.

Anti-corruption inquiries are messier. In the 2026 Bangladesh Premier League spot-fixing affair, Mohammad Ashraful admitted wrongdoing and served a long ban; much of the evidence was testimony, phone records and investigator-collected material — the kind of evidence whose integrity needs a separate framework. A ledger does not stop the offence. It does fix one thing permanently: who obtained which evidence, when, who preserved it, who examined it and who did not. In investigations, transparency is worth no less than deterrence, because it is the only route back to institutional trust.

Core dialogue: the 2026 boundary countback — when the technology was innocent and the lawmaker was not

14 July 2026, Lord's. The World Cup final ended level, the Super Over ended level, and England took the trophy on boundary count. That night the technology made no error. Ball-tracking, third umpire, run-out frames — all correct. The fault sat in a rule nobody had argued about before the match, because nobody imagined that rule would decide the biggest game.

This reframes the whole transparency debate. The public anger was not about data integrity; it was about rule authorship — who decided that more boundaries means the better team. No integrity ledger solves that. Only a transparent lawmaking process does: who was consulted, who objected, why. The ICC later replaced the tie-breaker with repeated Super Overs — correction arriving after outrage, not through process.

A referee's eye is less a gift than a burden of proof. Cricket has still not built a method for carrying that burden.

Contrarian — A Ledger Does Not Fix the Input, and Transparency Is Nobody's Business Model

Here is my sharpest hesitation, and it is almost absent from the mainstream discussion.

First objection: a hash chain can be applied to a wrong calibration, and then the wrongness becomes permanent. If a venue's camera setup was faulty in one match, the ledger immortalises the fault rather than correcting it. Integrity and accuracy are different things; blockchain supplies the first, never the second. A permanently archived error is more damaging than a temporary one, because it removes the possibility of arguing about it later.

Second objection: transparency is not itself a business, so nobody hands it over voluntarily. If the body running the review publishes its own hash chain, that is self-attestation — an institution declaring its own honesty while denying anyone else standing to contradict it. Real audit requires an independent party, with the power to write and the power to read held in separate hands. Cricket's power architecture, where member boards carry different weights and different commercial interests, resists that split. In smaller tournaments with weaker customers, audit pressure never arrives. The large Asian boards will not press either, because their broadcast commerce is entangled with the tracking providers.

Third objection: cricket's problem is not transfer investigations or age inquiries; it is calendar rhythm. In Asia, the collision between bilateral series, franchise tournaments and NOC calendars produces chronic instability, and its fix is scheduling architecture, not a ledger.

Transfer windows are contracts with feelings, and feelings are rarely admissible — yet in NOC-versus-franchise disputes, emotions aside, the arithmetic is nearly impossible to settle precisely because information scarcity becomes a weapon. A ledger takes that weapon away. So the real question becomes whose interest that serves.

And forgive the bluntness: audiences do not always want truth. They want closure. Whether a two-millimetre projection is 'umpire's call' or a conspiracy depends on which team the viewer supports. The gap between rule and feeling is corrosive, because when two matches involving the same side get two explanations, the mind is not satisfied — it demands fairness. If a timestamped line were published after every match — camera setup, calibration certificate, the single operator intervention — the anger might follow the data and convert into a demand for rule reform. That small displacement is the great civic loss of today's system: every review ends in uncertainty, and uncertainty accumulates across matches.

— Root: a pre-ledger shadow | Scenario: an argument that was never about technology, only about authorship.

I refuse to collapse these three objections into one: incompetence is a factual failure, incentive is commercial, and conspiracy is mostly absent. History shows systems that fear scrutiny shorten decision windows and written reasoning — shifting the burden onto the audience. The audience cannot carry a burden of proof.

Takeaway — Three Steps and One Question

Advocates of ledger technology often say 'blockchain' as a magic word. Cricket's most useful application is not a token but three dull, uncomfortable tasks: publish the calibration certificate for every match at every venue; publish the operator intervention log within twenty-four hours; appoint an independent review auditor, chosen not by the governing body but by an external panel. All three are administratively possible, and all three raise a larger question about collective governance than any technology upgrade.

My request to cricket administration, and the doubt attached to it: if a document followed every contentious review — stating who looked, what was seen, what was altered, and why — the game would not become perfect, but the audience would at least know it was watching the same two millimetres. The question is that simple: in whose interest will this sensor station keep its running timestamp — the spectator's, or those for whom cricket remains a business.