From DRS to Blockchain: Why Cricket's Referee File Wants an Immutable Record

On July 14, 2026, at Lord's, the final over of the World Cup final sent the ball off Ben Stokes' bat to the boundary, and those six runs — two run plus four overthrows — pushed the match into a Super Over and then a boundary countback. The spectator in the stands and the analyst in a Sydney studio were both stuck on one question: at the moment of the overthrow, had the batsmen crossed, and in which immutable document was that ruling written? The honest answer: nowhere. Beyond broadcast footage, the match referee's report and spoken interpretation, there was no other file from that night. In 2026, when the first VAR penalty in Russia did not settle an argument but opened a file, I had already been watching this gap. Cricket adopted DRS far earlier, yet the audit trail of a decision still lives mostly on paper.

DRS was first used in July 2026, in the India-Sri Lanka Test. Ball-tracking, UltraEdge, Hot Spot — the technology kept growing, but the method of recording a decision never changed. When a review ends, we know what happened, but not why, or which frame of data produced that outcome — that sits on the broadcaster's server, in the match referee's inbox, and in a paragraph of the ICC playing conditions. Three separate places, three separate owners, no single verifiable truth. The Lord's overthrow was a ruling that changed a match's fate, yet its basis — whether the batsmen had crossed — was never written to any independent ledger. And the bigger cricket becomes as a business, the more it needs an immutable record that no one can later alter or delete.

This is where blockchain becomes relevant. A distributed ledger means exactly this: every entry time-stamped, bound by a cryptographic hash, and impossible to erase once written. Is cricket actually moving toward blockchain? No one is putting the whole of DRS on-chain today, but demand for verifiable digital records in sport is rising — fan tokens, NFT tickets and debates over match-data ownership are evidence of it. I suspect cricket's next big technology controversy will not be about VAR-style review, but about the method of storing decisions.

Imagine a system where every review is logged automatically within 15 seconds of beginning. Which over, which ball, which umpire, who asked for the review — all in one ledger. Every ball-tracking coordinate, the UltraEdge audio spike, the stump-hitting margin — all written as hashes. That data stays synced across the ICC, the two boards and the broadcaster. If anyone changes a frame, the hash changes, and everyone catches it instantly. In 2026, when I audited 47 A-League matches, it was exactly this thinking that led me to give Football Australia a plan requiring remote VARs to log every check within 15 seconds. For cricket the same principle matters more, because here three different technologies often decide one call.

And here the question arrives: who would run such a ledger, and who would gain? Today the broadcaster owns the footage, the board owns the report, the ICC owns the rules. A shared ledger shifts that balance of ownership — the broadcaster loses its monopoly, the board must make its ruling public, and the ICC stands for the first time as guardian of a single, verifiable truth. An umpire who errs will have the correction seen by all; a board that applies pressure will leave a mark. They lose; the players and the spectator gain.

The curious thing is that a clear and obvious error is often hiding behind the clearest and most obvious angle. The umpire's call margin, the ball-tracking projection, the gap on snicko — each has its own tolerance, and those tolerances are not public. So if blockchain only writes what happened but never reveals why, the gain is small.

Cricket's rules travel across geographic borders — the way authority and dissent take shape in Bangladesh's cricket culture is almost the reverse of Australia's professional system. The same DRS protocol is read differently in Dhaka and in Brisbane, because the process was never written in a single, verifiable language. A blockchain ledger could supply that language — one for all, visible to all.

But here the reverse side appears. Blockchain does not settle disputes; it creates new ones. An immutable record means a wrong decision also becomes permanent. If an umpire wrongly gives a batsman out and that is written to the chain, where is the room for correction? A match referee can overturn a ruling today; on an immutable ledger that is impossible. This means technology will make decisions accountable, but will also narrow the path of human correction. And the real value of the game lies in people — players, umpires, spectators. If a ledger becomes the last word against their judgment, we may protect the process and lose our sense of justice.

The bigger risk is that the official explanation will carry more weight than the data. Just as a single line from the ICC often outweighs broadcast footage today, a so-called official blockchain record could in future stand as unquestioned truth — even though it was written by human hands. The immutability of a record and the correctness of a decision are not the same thing, and cricket must understand that difference.

My 46 years tell me cricket has always embraced technology — but the accountability of that technology has always lagged. DRS arrived in 2026, yet an auditable record of decisions has still not come. If blockchain remains only a tool for sponsors or fan engagement, it will not solve the real problem. The question instead is this: are cricket's rulers ready to run a decision ledger where every review, every umpire's call, every correction lies open before everyone? Or will the process again stay behind the back door — verifiable, but only for a handful of people?