The Blank Scorebook: Cricket's Data Ledger, Blockchain and the Reading of an Incomplete Record

It is six in the morning in Sydney. Cold air off Port Jackson is knocking against the window glass, and I have opened a file on my desk. The header reads: Stage Two, deep professional analysis. I had assumed there would be a match inside. An innings, a spell, at least a scorecard. What came out was an empty grid. Title: Not Applicable. Information points: zero. Entities involved: a single instruction, "identify from the information points above". One phrase keeps returning through the document: insufficient information.

I went looking for the match and found a manuscript instead; but this manuscript has blank pages. Only one mark survives in the whole file, a geographic tag, cricket_asia. No team, no player, no date. Yet those two words will not let me go. Because in cricket a blank page has never been innocent.

1. The Dhaka league, Udity Club. I opened the batting and kept wicket. Our scorer was an old man whose name I have forgotten and whose handwriting I remember: slanted, pressed down with care. In one match the rain came, play stopped at noon, then resumed. On that page one box stayed empty to the end. Nobody knew exactly how many runs came in that over. The scorer would not write it. Later I heard the team's accountant had put down a number of his own. That single empty box has stayed with me for fifty years, because I know that what actually happened there has no document behind it, only a plausible guess.

Today's cricket has moved from that scorer's hand into a server. Before the ball lands on the pitch a camera is tracing its path, an algorithm is checking its validity, a database is attaching it to a season average. Cricket is the only sport where the average, the strike rate and the catches start being recorded beside the name of an eleven-year-old child. This obsession with bookkeeping is part of our culture; on the pages of Wisden it has been granted the status of scripture.

But there is one place in that supply chain nobody has looked at properly: the space between the scorer and the database, where information is translated from one language into another. That translation is where the worst damage happens, and the damage has a name, silence.

In the last few years a new word has entered cricket's data industry: blockchain. Franchise leagues, fan tokens, even some boards' ticketing systems now speak of distributed ledgers. The argument is simple: if every ball's record is written into an immutable ledger, no one can change it later. Corruption falls, fraud falls, transparency rises.

That argument has a clear limit, and the limit is written in cricket's own history: a blockchain proves a record was not altered, it does not prove the record was true.

A hash is a seal, not a judge. Put bad data on the chain and you get immutable error, except now nobody can delete it. Cricket's archive is full of bad data, and it survived precisely because nobody questioned it. At Old Trafford in 2026 Jim Laker took ten wickets in an innings; in 2026 Brian Lara was 501 not out for Warwickshire against Durham. Those two numbers survive because there is a chain behind them: the ground scorebook, the next morning's newspaper, then Wisden, then the database. Break the chain and the number does not become false, but it stops being provable.

The gap between a missing record and a zero record is the most expensive bug in the game's data systems, and almost nobody sees it. If a batter is out for nought, that is information. If he does not take the field, that is also information. In a database both land in the same cell: zero. The next step computes an average, and an innings never played becomes an innings failed. Fantasy selection, salary setting, transfer value, even a young player's future, all grow out of that one wrong cell.

Fifty years of watching has taught me one thing: the most important information in cricket is often the information nobody remembered to write down. Some bowlers do not shout; they leave footnotes in the grass. Some innings never reach the scorebook, only the memory of someone standing behind the stumps. A pipeline that collects only visible numbers will never see half the game.

This is where the real blockchain question sits: technology can prove where data came from, it cannot prove what data is missing. And the biggest risk in cricket's data chain is not fraud, it is omission. A ball that was never recorded will never reach the ledger, and an immutable ledger makes that omission permanent.

When a report says "insufficient information", the obvious reading is clear: the job was not done, run it again. My reading is different. That empty document is probably the most honest paper in the system. Cricket's archives are stuffed with confident numbers produced by men who preferred a number to a blank box. Estimates born of guesswork have sat inside averages for decades, and nobody asked where they came from.

Admitting a blank box is hard, but it is the only box in which lying is impossible. Blockchain can institutionalise that honesty, if we first admit that the gaps are in our collection methods. Technology does not change culture; culture uses technology to keep its own habits alive.

I have learned to read the pitch in the pauses between noise, and there I have seen it: the game is not played only across those five days; it stays in the echo of empty stands, in the scorer's dried pen, and inside an incomplete file.

The next decade of cricket data will not be won by whoever holds the most numbers. It will be won by whoever can prove where a number came from, and which box is still empty. The question is no longer the scorer's. It is ours: when every ball is recorded, who will remember the small blank where nothing was written at all?