Empty Fields, Unbroken Chain: Who Keeps Cricket's Ledger of Evidence

Two in the morning. The fan turns slowly on the veranda. The rain has just stopped, but the street still smells wet. Under the blue light of the laptop I opened a file — a 'deep report' on cricket. Fifteen pages. Six major sections. Table after table, checklist after checklist. And in every cell, every row, the same sentence: insufficient information.

Forty-eight hours earlier, the piece I had finished was something else — wet grass, a drum in the north stand, a ball boy crying. Twenty-six years in this trade. For the first time, a report told me nothing at all. Empty cells do not describe an event, but the existence of empty cells is itself an event.

This is not a story about cricket. It is a story about the ledger. Who writes, who verifies, and how fast an unverified number puts on the mask of truth and walks into the feed.

The pipeline that never sees its own empty hands

The biggest change in cricket journalism over five years did not happen on the field but on a server behind the newsroom. A match report used to mean one person, one notebook, one smell of grass. Now it is an assembly line: a score feed arrives, ball-by-ball data arrives, a language model sits on top of it, and on top of that sits an editor who never watched the match.

There are two distinct stages in that chain — what I call Stage One and Stage Two at my desk. Stage One fragments: events, quotes, numbers, time sensitivity, entities. Stage Two builds analysis on those fragments. The chain is only as strong as its weakest link. And tonight what landed on my desk was a Stage Two whose Stage One was entirely blank.

Nobody tells you what happens when you write analysis from an empty input. Two things do. One: you admit, with some courage, that there is no data, so there is no conclusion. Two: you fill the empty cells with invention, and within eight hours that invention is on three hundred websites. The second path is easier. The second path is the real crisis of this profession.

What blockchain actually solves, and what it does not

Here blockchain enters. For several years now, the word has been used in sport as if it were a magic touch — as if everything false dissolves on contact. It is not like that, and the fact that it is not is the most interesting thing about it.

Blockchain's core achievement is not vast; it is precise. It is a ledger that can only be appended, never torn. Each new entry carries the hash of the previous one, so changing a number in the past means changing every block after it — and that change shows up in every copy on the network. There is a timestamp, and there are countless independent copies.

The most famous timestamp in the world right now is not a cricket one. On 3 January 2026, the first block of the chain carried a London newspaper headline — 'Chancellor on brink of second bailout for banks'. That is not merely a sentence; it is proof that nobody could have written it before that date. In sport, that technique is the most useful part.

Imagine the 2026 T20 World Cup, hosted by India and Sri Lanka from February into March per the ICC's announcement. If every ball's data, every scorecard correction, every match-officer decision were pinned to an immutable, timestamped ledger, then five years later nobody could claim they had said something else. Memory can change. A timestamp cannot.

Blockchain in sport remains largely confined to three areas. One, fan tokens, where supporters get small votes on club decisions and pay for the privilege. Two, ticketing and collectibles, where counterfeiting a ticket or a memento becomes hard. Three, contracts and payments, where international transfers, image rights and third-party commissions sit in one transparent ledger.

None of the three changes the game. They change the paperwork behind the game. And much of cricket's trouble is, in fact, paperwork trouble.

Not corruption — the absence of evidence

When we talk about corruption in cricket we usually talk about spot-fixing, betting, racketeering. The real foundation is quieter: the absence of evidence. A suspicious over happens, an inquiry follows six months later, and by then everything rests on someone's memory, a WhatsApp screenshot, a voice note saved on a phone.

The ICC's Anti-Corruption Unit has worked this gap for years, and its biggest obstacle is not evidence but the credibility of evidence. An immutable, timestamped, multi-party ledger can cut a large part of that obstacle. If the record of who submitted what, and when, cannot be altered, then altering a witness becomes hard.

But — and this 'but' is the centre of everything I am writing tonight — blockchain does not manufacture truth; it only makes truth hard to alter. Without grasping that distinction, the whole technology is nothing but an expensive illusion.

The oracle problem: cricket's real crisis

Technology has a term for this — the oracle problem. Blockchain cannot see the field. It does not know whether the ball went leg side, whether the stumps fell, whether the catch touched grass. Someone supplies the outside world's data to it. If that supplier errs, if it sends an empty input, if it omits something, the chain stays flawless, unbroken, timestamped — and entirely wrong.

The fifteen-page report in my hands was exactly that picture. The framework was perfect. The sections were reasonable. The checklists were professional. Inside, there was nothing. Had that report been written on-chain, it would have been the most trustworthy empty ledger in the world.

An empty block is still a block. Immutability is not a virtue unless the input is verified. The real weakness of cricket's data infrastructure is not technology but process — the moment we start believing the feed, verification stops.

The field seen from a Dhaka window

Based on my years of watching matches, one odd thing has become clear: cricket's least reliable facts are often its most quoted, because they are the most beautiful. The story of a spectacular catch buries the story of a mis-set fielding position. The story of a century erases a slow, tired, meaningless third session.

Sitting in Dhaka I have seen the same match produce two scorecards telling two different stories. Who is to blame? Nobody. Nobody knows who wrote first. The source is lost; only the number survives. This is precisely where blockchain matters most — the number has no value, the source has value.

The problem is that Bangladesh's cricket infrastructure is not yet ready to ask that question. Before putting domestic league scorecards, age verification or age-group team data on a chain, what is needed is a simpler habit: beside every number, note who wrote it, when, and how it was verified. That habit comes before the technology, not after it.

Esports taught me that a keyboard can roar. And much of that roar is fake — screenshots can be edited, rankings can be built from empty files, trophies can be invented. In a game that is entirely digital, verification is hardest. Cricket is walking slowly in that direction.

What the pitch remembers, what the scoreboard forgets

I have a line I write again and again: the pitch remembers what the scoreboard forgets. Tonight I want to turn it slightly — the ledger remembers what the feed forgets.

But here is the counter-intuitive part. We assume blockchain means transparency, and transparency means truth. In practice the opposite is very likely. An organisation that already controls the data gains a new advantage from an immutable ledger — once written, its version becomes permanent. Alternative versions do not vanish, but they become unbelievable.

So blockchain does not break power; it makes power permanent. Whoever writes owns the history. The question, then, is not technological but administrative: who runs the nodes? The ICC? The franchises? The broadcasters? Or the fans?

Transfers are not transactions; they are migrations with agents. And every migration has a document, a fee, a middleman. As cricket's market pours vast sums into young players — across the world's leagues, where a teenager with fewer than fifty first-class matches can command crores — every step of that migration deserves an unbreakable record. Without it, fraud surfaces late, usually when the player is already exhausted.

And something I hesitate to say. Fans do not actually want a ledger. They want a story. They want to sit at two in the morning and cry with a match. Silence, I learned, is also a stadium — if you learn to listen. But blockchain's silence is different: it has no smell, no drum, no crying ball boy.

That is my second doubt. If, in the name of verification, we turn cricket entirely into a ledger, we will gain truth and lose story. And if the story goes, the game does not survive. The game survives on its unverifiable moments — rain that stops suddenly, a botched run-out, a person a thousand miles away whose hands shake.

So what is the path? I think making blockchain cricket's judge is a mistake. Make it the notary. It keeps the evidence; it does not pass the verdict. There is an immutable record of who claimed what and when, but whether the claim is true is verified by people — the umpire, the reporter's notebook, and time.

And the first step of verification is not technology but humility. The ability to say, on seeing empty cells: I do not know. The fifteen-page report in my hands did exactly that. It was journalism in its most honest form — returning questions instead of answers.

Dawn arrived. The fan is still turning. Looking out the window toward the ground, I wonder: when the tournament begins in February, and a catch sparks a controversy, who will say which version was true? The scorecard will say one thing, memory another, the feed a third.

The chain will remain unbroken. The only question is whether the game will.