From VAR to Blockchain: Who Writes Cricket's Decision Audit Trail?

On an August evening in 2026, in a 10-by-12-foot room in Mymensingh, I ran a video file of the 2026 Europa League final at 50 frames per second. Ajax versus Manchester United, referee Damir Skomina, 34 fouls, 5 yellow cards. I was writing down timestamps, frame numbers, matching them against IFAB law clauses. The purpose was singular: to measure the gap between what the eye sees and what the book says. That night the first 'Referee's Eye' post drew 3,200 reads. Some called it madness. But I knew I was drawing a decision tree — where every branch ended in a question and every question sat atop a law.

Today, in the 2026 regular season, I feel that work in that room was incomplete. Because I was looking for the problem in the wrong place. I had assumed a referee's error is a referee's problem. After building the Russia ledger, and especially after assembling the 2026 empty-stadium database, I understood the error isn't the referee's — the error belongs to a system where no decision carries behind it a permanent, verifiable, tamper-resistant record. In cricket this gap is widest. And right now the answer to the most discussed question in the game may be hidden in blockchain — though nobody is yet fully ready to admit it.

First, the landscape. In football we have VAR. VAR is not perfect, but it at least produces an audit trail — which camera, which angle, which frame, which referee, which decision, why. From the 64 matches I watched at the 2026 Russia World Cup, the ledger I built surfaced 455 VAR checks, 20 on-field reviews, 17 overturned decisions and a record 29 penalties. I watched the Griezmann penalty at minute 58 of France versus Australia eight times. In the Croatia versus France final, 14 fouls and 4 yellow cards — after matching each incident against the Laws, a pattern became clear: VAR changes decisions, but the reasoning behind a decision disappears into the referee's mouth.

In cricket the problem is sharper, because cricket's decisions are more numerous, more frequent and more rule-dependent than football's. In one over, which line the bowler bowled, where the ball landed, where the batsman's foot was, when the umpire called out, when the third umpire gave the soft signal, what ball-tracking showed on DRS, what UltraEdge showed — each of these layers is decided by a different person, yet the final outcome arrives as a single number: out or not out. And the reasoning behind that number is stored nowhere permanently.

I used the same structure I built for the Russia ledger in 2026 when I assembled the empty-stadium database in 2026. I coded 306 post-lockdown matches — Bundesliga, Premier League, La Liga — logging 1,842 fouls, 73 penalties and 1,106 yellow cards. The result hit me like a shock. In empty stadiums referee behaviour shifted — average fouls per match fell from 26.3 to 22.8, home-win rate dropped from 43.2 percent to 38.1 percent. When the stadiums emptied, the numbers began speaking without the crowd.

But in cricket, empty-stadium experimentation has not really happened in that sense. We got some matches during Covid, but nobody systematically organised their decision data. This gap is now the biggest opportunity and the biggest risk.

Now the core decision question. Take a controversial out decision in cricket. Layer one: the on-field umpire. He reacts in 0.28 seconds — I measured that figure on 50fps video, it was my first metric. Layer two: the third umpire. He watches the replay, but the replay carries no precise frame-number tag, no ball-tracking software confidence score, no uncertainty range on the ball-pitching projection. Layer three: the match referee. He reads the report, but the report carries no direct camera timestamp.

So two referees, two analysts, two fans arrive at different conclusions about the same incident, because the data set in each hand is different. Looking at the NBA's seconds-by-seconds report model, one thing becomes clear: transparency of a decision does not mean the decision is correct — it means the path to the decision is publicly verifiable.

This is where blockchain becomes relevant, but not in the sense usually claimed. I want to separate three things — missing data, inaccessible data, and active concealment. Blockchain serves people for the first two. Blockchain is an immutable audit ledger. If every DRS check's outcome, ball-tracking confidence score, third umpire's video frame reference and match referee's final reasoning were appended to a cryptographically sealed chain, then nobody could later claim the decision was otherwise. Saturday's decision cannot be altered on Sunday.

A real question arises here: who takes this decision? The ICC? Each board? Or an independent technical committee? In 2026 my ledger was cited by four Bangladeshi outlets, but I was sitting in Mymensingh analysing a system I had no access to. I understood then — however good a ledger is, if not everyone at the other end has all the data, the ledger is a claim, not evidence.

And here comes the comparative-governance question, currently cricket's biggest gap. In football, European leagues share a centralised camera system. In cricket, every series, every board, every broadcaster has a separate production setup. IPL's DRS configuration and T20 World Cup's DRS configuration are not the same place, configurations differ, camera counts differ, ball-tracking software versions differ. So the same kind of decision yields different outcomes in two tournaments, and nobody can explain it, because the explanatory data is centrally stored nowhere.

This inconsistency is not a mere technical problem. It is a fairness problem. A player's career can turn on one decision, and if the reasoning behind that decision cannot be verified sixty days later, the erosion of trust in the system does not show up on any table. But it compounds after every match.

There is a counter-argument here too, and it cannot be dismissed. If blockchain is a public ledger, then the batsman's ball-tracking data, the bowler's action biomechanical data, the umpire's performance score — should all of that be public? Player privacy versus universal verifiability — blockchain does not itself provide a durable answer to this tension. Merely inserting technology does not make a system transparent; a system becomes transparent only when a clear link between decision and accountability is created.

And here is my biggest warning. I no longer want to write another sentence about the eye's failure — I want to write about a structure where every decision carries a timestamp, a law clause, and the signature of a responsible authority. And building that structure is not the work of any umpire, nor the work of any technology company alone. It is the work of a governance system where cricket's three core parts — ICC, the boards, and player representatives — must all sit at the table.

My biggest lesson has been this: in 2026 I thought decision quality meant how correct the referee's decision was. The 2026 Russia ledger taught me decision quality means how reconstructable the path to the decision is. The 2026 empty-stadium database broke that too — decision quality means how environment-dependent the decision is. The ledger's arithmetic taught me that memory is a spreadsheet with redactions.

So today's question is no longer whether the referee was right. The question is — where did that decision go afterwards, who preserved it, and if someone raises a question tomorrow, who holds the answer? If cricket cannot answer this question, then blockchain and VAR will not actually change decisions. Decisions will not change — only the language of debate will.

I want to end with a prediction, cautiously, at a limited confidence level. Over the next two years, if a major board announces a pilot programme storing DRS decisions centrally with timestamps and camera references, do not think referee errors will decrease. Think instead that we will then be able to measure referee errors — and that is not a moral victory, it is a structural one. And if no such announcement comes in two years, then understand that the table still does not exist inside the governance structure, where the real question is not blockchain but accountability.