Empty Cells, Broken Chains: Cricket's Provenance Crisis and What Blockchain Can Actually Do

Three in the morning in a Singapore flat. A data pipeline hands a file back to me, and almost every cell in it is empty — no headline, no source, no innings, no economy rate, no format, not even a name. One label hangs over the whole thing: cricket world.

Meanwhile, somewhere on earth, a ball is landing on a pitch. Someone at the boundary rope writes in a scorebook. A number is born from that ink, and within five seconds it has travelled into a broadcaster's graphics, a fantasy league's points table, a betting market, a sponsor's ticker, and an ICC ranking algorithm.

Between an empty spreadsheet and a live match sits the least examined problem in modern cricket: where did that number come from, and who verified it?

I keep returning to the final ball, because that is where the story begins. In 2026 I called a final at Rio Tinto Stadium with zero spectators. Cameras moved, commentary flowed, and the stands made no sound at all. The empty stadium taught me to hear the game differently — you cannot see where a fielder is standing a fraction early, which ball was a gratuity, which run was really a drop, unless you count it. And the moment you start counting, the first question is always: whose book are we counting from?

I am a person who trusts paper. Fifty years around scorebooks and scoreboards have taught me that my own memory is catastrophically unreliable. In 2026, at the women's Euro final in Enschede, I was recording a podcast as the Netherlands beat Denmark 4-2, with Vivianne Miedema wearing number 9 and scoring twice — and I still failed to note the exact minute of her second goal. That one blank cell taught me that what I hold in my head is never evidence.

Cricket delivers that lesson more brutally than any other sport, because cricket is the most number-saturated game on earth. A T20 match is 240 legal deliveries, and each delivery carries a dozen data points: release point, line, length, seam position, contact point, wagon wheel, run rate, pressure index. An ODI tournament accumulates from four to five hundred deliveries. A Test bleeds numbers across five days, session by session, over by over.

That mountain of numbers has an economy. The Women's Premier League's media rights for the 2026–2027 cycle sold for 951 crore rupees; the men's IPL's rights for the same period sold for 48,390 crore rupees. What exactly does all that money sit on — affection, or the belief that the number on the scoreboard is true? Franchises, broadcasters, sponsors and bookmakers all build different businesses on the same raw feed. Almost none of them can show you the feed's birth certificate.

The chain nobody sees

Before a number reaches a scorebook it passes through at least six hands. A scorer at the ground, often a volunteer, often busy with something else. A data operator pressing buttons. A tracking system, if the venue has one. A data provider with its own input format. A broadcast graphics team. Finally an aggregator, who rewrites the figure into its own dashboard — occasionally turning four off eleven into something else entirely, occasionally by accident.

Nowhere along those six steps is there a single, public, persistent ledger. Where there is none, a correction usually means a quiet deletion, and a quiet deletion means an erasure from history.

On 14 July 2026, at Lord's, England and New Zealand tied the World Cup final, then tied the Super Over, and the trophy was decided by a count of boundaries — 26 against 17. A world title turned on a set of figures that had to be hand-counted at the boundary edge against the tournament playing conditions. One miscounted row and history changes, and nobody ever knows.

This is where blockchain first becomes meaningful, and not in the cheap way it is usually sold. The mechanism is simple. When an entry is written, it carries who wrote it and when. That entry, combined with the previous entry's cryptographic hash, produces the next hash. Change any middle entry and every subsequent hash fails to match — the chain breaks audibly. That is a tamper-evident ledger.

It does not prove truth. It proves the entry was never altered. That distinction is enormous, and cricket administrators keep stepping around it.

Publicly reported uses of blockchain in cricket have largely avoided the distinction altogether. In 2026 the ICC announced an official partnership with an NFT platform; in 2026 Cricket Australia signed a cricket-themed digital collectible deal. Ticketing, fan tokens, moment collectibles — the names sound excellent. Not one of them has made a single cell of a scorebook verifiable. They made cricket's memory scarce rather than provable.

The women's game carries the heaviest cost

A provenance crisis does not hit every player equally. Where the archive is already thin, the damage multiplies.

On 8 March 2026, at the Melbourne Cricket Ground, Australia beat India by 85 runs in the Women's T20 World Cup final before 86,174 people — still the largest crowd in the history of women's cricket. On 23 July 2026 at Lord's, England beat India by nine runs. Those matches are history; they are written down.

But ask why a national team's number four declined the pull shot, what her line and length was across the last three series, what share of her domestic wickets were yorkers, and I am still groping in the dark. Large parts of the women's domestic fixture list, ball-by-ball logs and fielding maps were written on paper, not captured on camera — and paper is not bound to a hash. Does that make them untrue? No. It makes them unverifiable, which in this era is worse.

My master's degree is in kinesiology. That training taught me one hard thing: if a fast bowler's workload data is wrong, it is not merely a data error — it is an exploded knee. The series of workload records we hold for women fast bowlers is small, and there is only one remedy for a small sample: keep the source auditable, so the next researcher at least knows which numbers were real.

My own textbook

Let me be coldly honest. My recall is poor. I get confused when I am tired. I am not ashamed of this, because the problem is not catastrophic and the fix is mundane. There is a notebook in my bag, a process on my phone, and since 2026 a part-time fact-checker who independently re-checks every figure before I file.

Based on my years of watching matches, the most dangerous analyst is the one who believes their memory can absorb the work of verification. The same error is being committed at institutional scale across cricket every day. The broadcaster does not have it, the fantasy app does not have it, the ICC ranking algorithm certainly does not have it — nobody holds the number's birth certificate.

Where blockchain genuinely helps, and where it does not

If someone asked me to design the architecture, I would build three pillars.

First, the scorer's hand. The app must be offline-first; a ground with no network is not a problem. The scorer enters the runs, the phone stores them, and each entry is signed with a personal key. Every entry therefore stands behind a named, moral person rather than a hidden server.

Second, an append-only public log. Each entry joins immutably, and every correction is made by adding a new entry — the old figure is never deleted, it simply acquires a 'revised' layer beside it. Here is the crucial rule: corrections should be printed, not hidden. Today's practice is usually the reverse — the correction happens and the history vanishes.

Third, an open access point. A twelve-year-old in Sylhet, a club scorer in Singapore, a coach in a small Indian town — all three should be able to ask: who wrote this number, when, and has it changed since?

This is also where I hesitate. It is easier to say than to do, and the path holds a large hazard that administrators routinely skip past.

The immutability of error

Suppose someone records that a bowler conceded eight in his first over when the truth is six. The figure is locked into a hash, stamped with a time, placed in a block. It is now permanent.

The distinction matters. Blockchain promises to make information unchangeable, not correct. In the past a bad number was quietly revised two months later and nobody noticed. If the bad number is chained to a ledger, the bad number becomes permanent truth, and to change it you must change it in front of everyone. For me that is progress — but only when it is paired with strong human verification. Without that, it is a hazard.

Then comes the economics. Every time the word blockchain has been uttered in cricket, its near-constant companions have been 'token', 'NFT' and 'royalty' — almost never 'verification'. That is not an accident. Because cricket's numerical history can be commodified, the industry commodified it first. My objection is not to people earning money; it is to a trade in which verification is kept outside the conversation.

And there is unequal access. When a Grade 2 domestic scorer's phone battery is dying, hash functions and distributed ledgers sound like nothing at all. A system only works for those who can carry it — otherwise it becomes a ledger of the privileged, kept for one another.

What remains at the end

The real question is not about blockchain. It is about belief. Cricket has run for a century and a half on the faith that the ink in the scorebook does not lie. How strong that faith really is became clear after Lord's in 2026 and Ahmedabad in 2026 — a match's fate hangs on a specific figure, and that figure is made by people.

I do not trust artificial chains. I trust the idea that if every number carries a name, a timestamp and a revision history, my unreliable memory will stop damaging history. That empty spreadsheet was not actually empty — it was honest, because it admitted it knew nothing. The rest of our world rarely gets the chance to admit the same.

Over the next decade, cricket's data infrastructure will not be judged on how many crores of NFTs were sold. It will be judged on whether a school-ground scorer in Sylhet, a Sunday club statistician in Singapore, and a third-party verifier at a final played before 86,000 people in Melbourne can read each other's books.