Empty Spreadsheets, Full Stadiums: Cricket's Data Void and the Blockchain Promise

Hook

There is a file open on my laptop. I called it stage_two_final_v7.xlsx. Inside are eleven columns, eight sections, and in every cell the same single sentence — N/A, insufficient information. This is not a scorecard. This is an analysis that, in the act of analysing, discovered it had nothing to analyse.

I laughed at the spreadsheet first, then went quiet. On May 22, 2026, Vietnam's Under-20s drew 0-0 with New Zealand in Cheonan, and the whole country wrote the word historic that day. I wrote the opposite — a fourteen-hundred-word note arguing the 0-0 was not a triumph but a trap, a 5-4-1 mould that would hold Vietnam hostage for a decade. Sixty-one shares on day one, four thousand by Sunday. A score that started at zero gave me the busiest piece of writing of my life.

Now another zero sits in front of me. But this one is not on a pitch, it is in a database. And this is where cricket's least-discussed crisis hides — the game is played, the highlights glow, but the evidence of the game disappears.

Context: The Data We Do Not Keep

Asian cricket stands in a strange double state. On one side the grounds fill up — a franchise league in Dubai, a domestic tournament in Colombo, a league in Dhaka — and on the other there is no single, reliable system for preserving that cricket's data. The ICC has its own match-data system for internationals. Franchise leagues have their own scoring partners. But local, age-group, and women's tournaments are left with… an online sheet, or a messaging group, or simply a scorer's memory.

I have watched this ecosystem for nine years. One scorer, one notebook, one phone — an entire Under-19 tournament's future is decided on the strength of these three things. A bowler's career is built on his economy rate, yet that number is never written down permanently. On trial day the coach looks at a torn piece of paper. When the notebook gets wet in the rain, history gets wet.

The Gulf's labour economy is tied directly to this data crisis. The players who come to Dubai or Sharjah on contracts — many of them from South Asian grassroots — often have no proof of their performance in the very place where their next contract is decided. Their runs, their wickets, their hardship — scattered across fragments of files, never becoming a full picture anywhere.

This place is familiar. In 2026, when the Under-23 final played out on a snow-covered pitch in Changzhou, the scoreboard was the only witness. The snow in Changzhou did not bury the knee; it archived it for every argument since. And in 2026, when the game returned to empty stadiums, I built a spreadsheet and found home wins had fallen by roughly a quarter. The Empty Stadium Experiment proved that crowd noise is a character, not a backdrop. But that experiment survived only because someone kept the data. In a tournament where nobody keeps it, the difference between an empty stadium and a full one is never known at all.

Core: Three Erasures

That empty file in front of me is itself news. It shows that erasure happens at three levels in cricket's data system.

The first erasure happens at the moment of the event. Something happens in every small tournament that nobody records — a strange catch, a slow over-rate fine, a disputed umpiring call. This information never comes into existence. In blockchain language, it is lost before it can ever be on-chain.

The second erasure happens at the storage level. The data is recorded, but on a central server, under one institution's control, with a limited lifespan. When the league folds, the server folds. When the sponsor changes, the data changes. If someone wants to delete the information, they can — with no trail.

The third erasure happens at the interpretation level. The data exists, but nobody reads it, nobody cross-checks it. A statistic is true, but if it is not verifiable anywhere, it is effectively absent.

Together these three levels create the void that sits in the file in front of me.

This is where blockchain's real proposition arrives — and note, I am not selling hype here. I am only stating what is technically true. A blockchain is a distributed ledger where each entry, once written, is cryptographically linked to the entries that follow. Nobody can go back and quietly change a number — if they do, every subsequent block falls apart.

What does that mean in cricket? It means a ball-by-ball record, if it is on-chain, is permanent and verifiable. A scout in a Dhaka ground, a selector in Karachi, and a coach in Dubai all see the same data — data nobody could alter.

Go deeper and two possibilities appear. One: players owning their own data. Today a cricketer's performance data is controlled by the league or the broadcaster. On-chain, that data can live in a personal wallet, and anyone who wants to use it pays through a smart contract. Two: anti-corruption. The greatest weapon of fixing is opacity. An immutable ledger can cut much of that opacity — which over saw which wide, who wagered where, it is all written down.

Notice, these propositions are not a story of glittering revolution. They answer one ordinary question: whose hands hold the proof of the game? Today the answer is — whoever owns the server. Blockchain says — whoever plays the game.

Contrarian: How I Could Be Wrong

Now let me write the strongest opposing version of my own claim, because firing off a hot take is easy, taking responsibility is hard.

First objection: a blockchain is a ledger, not a memory. Data that was never recorded at all — that first erasure — no ledger can bring back. Whatever a Gulf club does not write down at the ground is already gone before it can be on-chain. Technology can only protect data that someone agrees to hand over. And agreeing to hand over data is a political decision, not a technological one.

Second objection: on-chain garbage stays garbage. If wrong information is written, the blockchain keeps it permanently wrong — it cannot be deleted. A single bad entry could become eternal, which is more dangerous than today's server system.

Third objection: cost and centralisation. A public blockchain charges a fee for every transaction. Paying a fee for every ball would push an entire tournament's budget into data. And if a private or permissioned chain is used, power once again gathers into a few hands — exactly what we wanted to avoid.

The biggest point: the problem is not technological, it is human. Who decides which data matters? Who pays the scorer? Who has the courage to ask the question? Blockchain answers none of these. Sometimes it even lets a weak administration dress itself in a new technological fog so the old problems disappear from view.

So my position is not without doubt. I am not saying blockchain will save cricket. I am saying the data void is a real loss, and blockchain is one possible solution — conditional, limited, and only once people first decide what they want to record.

Takeaway: A Date, A Number, A Question

So my prediction? Let me end with a date and a number, because whatever the edition, it is numbers that keep an argument alive.

I predict: by 2030, at least two major Asian franchise leagues will migrate the complete ball-by-ball data of their age-group and women's tournaments onto an on-chain or permissioned-ledger system, and they will do it under the excuse of labour transparency and anti-corruption, not out of genuine player welfare. If I am wrong, then in 2030 I will have an empty file — and I will write about it again, because the 0-0 that started an argument is still my favourite match, because nobody won the narrative.

And if I am right, then in place of a torn notebook, one long catch from every small ground will live as a permanent block — forever, with no one's permission.

The question is not mine, it is cricket's: do we want to keep the proof of the game, or only the highlights?