The Empty Scorecard: What Survives When Cricket's Data Chain Breaks

It was ten past two in the morning in Melbourne. The heater was off, the rain outside had settled into a steady hum, and on my laptop screen a file was open. I was waiting for a scorecard — names, runs, overs, a decision. The file came back. There was nothing in it. No teams, no players, no over-by-over record. Just one sentence, repeated in different phrasings across the document: insufficient information, analysis not possible.

At first it felt like relief. Empty means no risk. No teams, so no ranking argument; no players, so nobody is being praised unfairly. A few seconds later it occurred to me that I was walking in exactly the wrong direction. The absence of information and the absence of risk are not the same thing. A blank page says nothing on its own, but if we mistakenly treat blank as neutral, the blank page becomes the loudest lie in the room.

The match played at the Melbourne Cricket Ground in March 1877 still has a result we can read today — Australia won by 45 runs. We know it because somebody wrote it down. In the same city, in the same decade, the matches where nobody sat down to score are invisible now. The pitch was there, the light was there, the crowd was there. There was just no witness.

I have watched cricket for years — Bangladesh at night, Australia at dawn, a viewer sitting between two time zones. In that time I have learned one thing: cricket is a ledger. Every ball is a transaction, every over is a block, every innings is a chapter. The game happens on the field, but the game survives in the book. And a book does not become true by itself. Somebody has to make it true.

How many hands does one fact pass through

In modern cricket, a single fact crosses six or seven hands before it reaches you. An umpire on the field gives a signal — out, no-ball, wide. The scorer enters it in the book. A broadcast data feed turns it into a digital format within seconds. That feed travels to a stats database, from there to an analyst's model, from the model into a fan's memory. At every step information can shift, disappear, or quietly become wrong.

When the Decision Review System was first used in Test cricket in Colombo in July 2026, we gained something new — ball tracking, Snicko, HotSpot. Suddenly a second decision stood beside the umpire's. But notice what DRS actually does: it verifies information, it does not create it. And you can only verify what already exists.

Donald Bradman's Test average of 99.94 holds as firmly as it does because every innings of his was recorded. Sachin Tendulkar's 100 international centuries survives as a claim because every scorecard exists. The first men's T20 international, played at Eden Park in Auckland on 17 February 2026, entered history for one reason — somebody counted it. Matches nobody counts never enter history. That is the difference between history and memory.

Where the ledger's trust breaks

Of the vast store of cricket data that has accumulated, a large share still cannot answer a simple question: who recorded this fact first, and who checked it? Who owns the ball-by-ball feed, who licenses it, and if someone claims that a particular over in a particular match went for four, who goes and reconciles it? In cricket those answers remain scattered rather than centralised.

This is where the idea of a blockchain becomes relevant, and relevant in a very ordinary sense. A blockchain is essentially a ledger with three properties: every entry carries a timestamp, once written it cannot be quietly altered, and many copies hold the same record instead of one. Cricket's long-standing problem is precisely the absence of those three — a timestamp, immutability, and multiple witnesses.

Picture the final session of the fifth day of a Test. The scorer is tired, a broadcast feed has jammed on a single over, and the stats database issues a correction later. The analyst's model has already built a conclusion on the pre-correction number. In the fan's memory that conclusion is now solid. Nobody lied at any single step, and yet the result is false. That is the weakest joint in cricket's data chain — and it is less a technology problem than a process one.

Around 2026 and 2026, cricket caught the wave of digital collectibles: fan tokens, NFTs, limited-edition digital cards. A lot of money, a lot of announcements, a lot of promises. Within a few years most of it went quiet. The reason is simple. Those were collectibles, not infrastructure. Buying a rare card and keeping a trustworthy record of every ball in a match are different jobs. Nobody saw a profit in the second, because the second has few buyers — and those who exist stay silent.

A blockchain does not make information true; it makes the record of who wrote what, and when, impossible to alter. If the ledger is filled with errors, an immutable ledger means permanent errors. Technology preserves testimony. It does not produce it.

The contrarian angle: does every match deserve a witness?

Now to the part least said in this conversation. When we talk about cricket data, we almost always mean men's international matches — where there are cameras, feeds, sponsors. But the majority of cricket is never recorded anywhere. Women's domestic cricket, four-day matches in associate nations, club cricket, tape-ball tournaments in villages — no scorer sits down, no feed is generated, nothing exists to hash.

So the entire discussion about strengthening the data chain revolves inside a fixed perimeter, while the rest of cricket sits in the dark outside it. Hash a blank page and you get a blank hash. Technology preserves absence as absence. It does not convert absence into presence.

And this is where my deepest suspicion begins — do we actually want to protect the record, or only the part of the record that already makes us comfortable?

Looking forward

So back to that rain-soaked Melbourne night. The empty file was open in front of me, and I understood that an empty result is not a neutral result. Where there is no information, analysis does not stop — it goes blind. The biggest question of cricket's next decade may not be the name of a new star. It may be this: which matches never make it into our book, and why?

The scoreboard ends the game. The story refuses to log off. The only question left is whether we will sit down to write the stories nobody has sat down to write.