The Empty Cell Notebook: On the Verifiability of Cricket Data and the Search for Immutable Records

A file arrived at two in the morning last week. The sender claimed it held ball-by-ball data from an entire match — every delivery's line, length, speed, bounce, the batter's footwork, the bowler's release point. I sat down with coffee. Twenty years of habit: before I open a file, I keep a notebook beside me, so I can watch the pattern unfold with my own eyes. I opened it. Empty. Not a row, not a column — just a blank sheet.

My first reaction was irritation; I assumed the file had corrupted, or something had gone wrong during download. Then a strange calm arrived. Because I know that this blank sheet is asking me the most honest question of all: when there is no data, what does an analyst actually do? Fill the notebook with invented stories, or admit that the empty cell is empty?

I chose the second. Today I write about why — and why this empty cell exposes something large about cricket's future.

In cricket, data is no longer a luxury; it is infrastructure. DRS arrived, Hawk-Eye ball-tracking arrived, a spinner's revolutions are measured, a swing bowler's seam position is recorded, a fielder's first step is mapped. The IPL, the BBL, The Hundred — every franchise pours enormous sums into data providers. In 2026, while I was building pressing-trigger spreadsheets for Sheikh Russel from Rangpur, I noticed something even then — as the volume of data grows, the question of trust in that data grows louder.

Because nobody says one thing out loud: data is not neutral in itself. The hand that types it, the server that stores it, the company that sells it — each is a gatekeeper. And a gatekeeper holds the power to err, to omit, even to alter.

I think of my Russia notebook. The 2026 World Cup, 64 matches, 1,200 attacking sequences. From Rangpur I watched every match with a stopwatch. On the night Croatia beat Argentina 3-0, Modric's line-breaking passes, the kilometres Rakitic covered — I cross-checked those numbers myself, because the television graphics and my notebook rarely agreed. A pass many at home call ordinary revealed itself in my notebook as a crack in midfield.

Russia taught me that weather is a midfielder — and the same holds for data. Data is a player on the pitch, not a neutral spectator. It must be rated, doubted, sometimes benched.

And this is where DRS becomes instructive. DRS is not merely technology; DRS is a covenant of belief — that ball-tracking, UltraEdge, Snickometer are telling the truth. But that technology's reckoning is also produced in one central room, and there the question stands: if someone altered a frame of ball-tracking, who would catch it? Not the spectator in the stands, not the player, and certainly not you or I in front of a television. We simply believe. And that word, belief, is today's real variable.

Consider how many hands a data feed passes through. The same ball-by-ball feed goes to the broadcaster's graphics, to fantasy platforms, to betting markets, to the coach's tablet, to newsroom headlines. Once an error enters, it spreads everywhere at once, and later nobody knows what the real delivery was.

Here I will discuss three variables. My rule — no more than three per piece, or the reader loses the match behind the model.

First variable: verifiability.

Cricket's real problem is not that data is scarce; it is that the source is usually single — one central institution. You do not know whether the 142.3 km/h on the screen was truly 142.3, or a radar glitch. The core idea of a blockchain is relevant here: a record that, once written, no one can quietly change, and that stands open to all.

Imagine every delivery as a small record — bowler, batter, runs, speed, out-or-not-out. If these link one after another in a chain, each new block carrying a mathematical fingerprint or hash of the previous block, then no one can secretly alter a delivery's outcome midway — because moving a single cell cracks the whole chain visibly. Against match-fixing this is a real weapon. The 2026 Lord's scandal — the spot-fixing involving Mohammad Amir, Mohammad Asif and Salman Butt — showed that such crimes are possible only when something stays in the dark.

The pattern was already there before the first whistle. The pattern of fraud is also set before the first ball; we simply cannot see it because the record is not transparent. A tamper-proof ledger removes that screen.

In practice a simpler route exists. Let several independent providers record the same match separately, and treat the result as final only when all three agree. No one can change it alone, because the other two will not match. This too is a form of verification, only its name is not blockchain.

Second variable: cost and latency.

There is a real trade-off here, and I will not hide it. A blockchain-style ledger is slow, expensive, and burns energy per transaction. But cricket's latency is not critical — ball-by-ball data written a few times a second is plenty. The danger arrives when live betting markets must reprice in an instant; that demands thousands of transactions, and a slow ledger will not cope. So the realistic answer is layered: a fast layer for live scoring and market reckoning, and a slow but immutable layer for the settled, final record. Verification and speed — kept in separate layers, both survive.

Third variable: privacy.

A player's biometrics, injury history, contract figures — if all sat on an open ledger, the player's rights would be violated, and no union would accept it. So not the whole dataset; only a digital fingerprint, a hash, can go on-chain. The underlying information stays private, yet its immutable proof survives. If someone later makes a claim, you can prove the information never changed — without showing it to anyone. That is the balance, and that is where my Rangpur notebook and modern cryptography speak the same language.

With these three variables together, I make one claim, with clear confidence. Unless verifiable records replace the central gatekeeper, over the next decade cricket's sponsorship audits and budget analyses will both deepen into a credibility crisis. My confidence is medium-to-high; the technology is proven, the question is only will and cost.

One more point, which I understood more sharply while working as a BCB advisor in 2026. A cricket digital infrastructure means not merely apps or streaming; it means a foundation on which trust rests. A match whose score someone can later alter is not an asset to a sponsor — it is a risk. A franchise's value is set by its viewership, attendance and match data. If that data is not verifiable, then club ownership, share sales, investment — every calculation stands on sand. Look at football's club IPOs; however clean the numbers in the filing, if the truth on the pitch is not verifiable, the market will one day ask.

I never treat weather as background. Dhaka's dew, Chattogram's sea breeze, foreign winters — each is a selected player. But that player's performance is also measured by data — dew point, humidity, wind speed. And if that measurement depends on one central instrument, then the explanation for why the ball skidded in the evening's second spell is also locked in one person's hands. Think of DLS — rain decides a match's fate through a formula whose inputs are overs lost, wickets fallen, runs scored. One wrong input makes the result wrong, and that result becomes immutable. Without verifiable records, these inputs too sit in the same dark.

But here I want to stand against myself. Because my notebook has a crooked line I never erase.

I keep a notebook for the games that never happened. Innings washed out by rain, a chase abandoned at 87 for 4, that field-setting one fielder short — these unwritten matches are living research to me. And that notebook tells me something uncomfortable: blockchain will not restore cricket's honesty, because the problem of honesty is human, not technological. At Lord's in 2026 the crime was not born of missing data but of greed. With a transparent ledger, someone could still bowl a staged no-ball; only now it would survive on the ledger as a permanent, immutable fact, and proving guilt would be easier. In other words, blockchain does not tie the thief's hands — it stops the thief's fingerprints being wiped. That is no small difference, but it is no magic either.

And one merciless truth: in journalism and analysis we often mistake quantity for quality. More data does not mean more truth. Many outlets now float dozens of stats after every match, verifying not one. Abundance of information covers a deficit of understanding — just as a side holding sixty percent possession may still never see the goalmouth. Possession is not creation; a stat is not comprehension. I trust the model, then I watch the player — but many today stop at the model and never return to the player.

So I return to that blank sheet. It was not a failure; it was a warning — I will not write anything I have not verified. In the next match I will not hunt a big number; I will hunt whether every number has a verifiable delivery behind it, and who witnessed that delivery.

The question is for you: of the figures you know by heart from your favourite match, how much have you truly verified — and how much have you simply memorised on belief?