Cricket's Unwritten Ledger: Can Blockchain Become the Audit Trail for Officiating Decisions?

Lord's, 14 July 2026. The final over of England's innings. Martin Guptill threw from the deep, the ball deflected off Ben Stokes' bat and ran to the boundary. Kumar Dharmasena and Marais Erasmus signalled six — two runs completed, plus four for the overthrow. The replay showed Stokes and Adil Rashid had not crossed for the second run when the throw was released. Under Law 19.8, that is five runs, not six. One run carried the final into a Super Over. I was in Kuala Lumpur then, a second-year International Communication student. That night I wrote a single line in a notebook: incident ID, over, law, final call, whether correction was possible. Seven years later that notebook has pushed me to an uncomfortable question. Cricket logs decisions a thousand times, yet they live in at least three separate ledgers that cannot be reconciled — footage with the broadcaster, the report with the match referee, the code with the ICC. Three versions of one incident, and not so much as a shared hash. The history of technology-assisted officiating in cricket is older than most fans assume. The third umpire was first used in November 2026 at Kingsmead, Durban, in India versus South Africa; Sachin Tendulkar was the first batsman dismissed through that system. Hawk-Eye entered English television coverage around 2026, projecting ball paths in three dimensions. In July 2026 the Decision Review System debuted in the India–Sri Lanka Test in Colombo, then an optional player facility. By 2026 the ICC had made DRS mandatory across all men's ODIs and T20Is. The 'Umpire's Call' threshold for LBW flows from that framework: the ICC definition turns on half a ball's width, and anything less leaves the on-field decision intact without costing the review. The problem is not technology. The problem is documentation. The third umpire studies five angles, reaches a decision, the screen flashes, the commentator explains — and the explanation evaporates into the broadcast archive. A week later nobody can answer which law governed that review, who ratified it, and what confidence interval the ball-tracking carried. I have been keeping a refereeing incident log in Kuala Lumpur since 2026. What struck me in the first year was not the absence of patterns but the absence of any means to see them. My 2026 audit across all 64 World Cup matches — the one I labelled the VAR Protocol Audit — rested on four pillars: trigger, review type, final call, law citation. I categorised 20 overturns by law and calculated average review times. The lesson translates directly to cricket: a system that does not record its own errors cannot measure its own improvement. So what would an audit ledger look like? I see blockchain functioning in a narrow but exact role — not as a replacement for the third umpire, but as a hash-anchored log beside him. One record per incident: incident ID, match over, appealing side, technology used, law citation, confidence level, final decision, whether the on-field call survived, and a timestamp. Nobody can alter that record afterwards, yet the governing body, the broadcaster and the press all read certified copies of the same truth. The cricket-to-football comparison has to carry a stated limit: in both sports decisions escalate upward, but cricket caps reviews per innings while football does not. The behaviour samples are not directly comparable; the principle is. The value compounds in the regular season, when the sample finally accumulates. Seven tournament matches reveal nothing about officiating style. Forty to sixty reviews per round across T20 leagues begin to expose an error taxonomy. For my 2026 Silent Pitch study I tracked 1,200 foul calls and found home penalties fell from 0.29 to 0.18 per match behind closed doors. Cricket has no equivalent controlled study, largely because the data is not public — and because it is not public, fewer people feel entitled to ask. The human-factor layer cannot be engineered away. An umpire's angle, fatigue, the wicketkeeper's body obscuring part of the ball, sledging from the opposite side — all of it enters the decision. A ledger does not erase that reality; it makes it visible. If one umpire's record shows his Umpire's Call rate on left-arm spin is twelve percentage points above normal, that is not an accusation. It is a training input. Now the argument I find weakest on my own side. Blockchain's celebrated virtue is that nothing, once written, can be removed. In officiating, that virtue is also a hazard. Had the Lord's overthrow error been immutably chained, correcting it would have required something like a fork. Immutability preserves error securely; it does not repair it. More fundamentally, blockchain builds trust in records, not in interpretation. That six runs were awarded can be recorded permanently. Why they were awarded still depends on human readers of the code. A referee's eye is a frame-by-frame threshold test, not a whistle — and when the threshold shifts, the decision shifts, however immovable the ledger. The practical proposal should stay plain. One: agree a common incident schema across the ICC and member boards so every review is recorded against identical fields. Two: publish a read-only public mirror that journalists and independent analysts can query. Three: retain the right to correct — an append-only ledger, with every correction itself logged and visibly flagged. Four: release an end-of-season pattern memo, one hypothesis and three supporting incidents. Technology entered cricket by majority consent; that is settled history. The architecture for accounting for officiating decisions is still scattered like cuttlebone. If a league publishes its first review ledger in the 2026 season, it will look like a small jolt — and it may quietly define the next decade's meaning of transparency: not simply showing the ball's path on a big screen, but showing the decision's own path.