Witness to Zero Data: Cricket's Coming Age of Verified Truth

The clock in the Delhi studio was brushing half past eleven. On the big screen, ball-tracking was running—the speed, bounce and swing of every delivery painted in green and red dots. The producer's voice was in my headphones, a technician's keyboard clattering behind me. Then the screen went white. The last frame of the tracking froze mid-air, then dissolved. The producer said, feed's down. I thought it would take a minute. One minute became five, five became ten. A strange silence settled inside the studio—the kind that only falls when nobody knows what the next sentence should be.

I have heard a lot of silence in my life. In May 2026, in an empty German stadium, I heard a referee's whistle echo off concrete. In Russia in 2026, I heard the whispers of the VAR review room. But the silence in that Delhi studio was different. It was the silence of data. We are used to information always being there, the screen always answering, the machine never standing with empty hands. And in that exact moment, when the machine went quiet, I understood that the biggest risk in modern cricket is not strike rate or economy—it is the integrity of the data itself.

After that night I lay awake over one question. If ball-tracking drops for a second, if a graphic freezes at the wrong timestamp on the third umpire's screen, if a single number lands in the wrong cell of a scorebook—then whose decision is it? The machine's, or the human's? And the larger question still: how do we know the data we are standing on is actually correct?

Cricket was never only a game; it has always been a game of record-keeping. In nineteenth-century England the scorebook was written by hand, in ink, counting runs one by one. That book was the blockchain of its age—an immutable record where every ball was accounted for and no one could erase a line. Today that book is digital. Hawk-Eye, UltraEdge, ball-tracking, Snicko—each technology is doing the same job: turning a decision into a document, so that when someone asks later, the answer holds.

I grew up inside this age of record-keeping, but I saw the age before it too. In 2026, covering the Wills Cup in Dhaka, I first learned how sturdy a scorecard is. There was no social media, no review, just a notebook and a pen. If that book was wrong, nobody could catch it—and that was the scariest part. The absence of evidence was so normal that nobody even thought of it as a problem.

Then came 2026. The Under-17 World Cup was in Delhi. I started a programme called Digital Whistle for a streaming platform and covered all 52 matches. England 5-2 Spain in Kolkata—Rhian Brewster's goals, Phil Foden's magic. My live referee breakdown of Sergio Gomez's 10th-minute goal and Brewster's 44th-minute equaliser drew 1.1 million views. That was my first lesson in writing in real time, timestamp by timestamp, explaining the law. From that experience I began every piece with a positioning note, a minute marker and a clear verdict.

In 2026, VAR at the Russia World Cup opened my eyes. I charted 29 penalties and 455 VAR checks. Explaining Antoine Griezmann's first VAR penalty in the 58th minute of France versus Australia, I understood that technology does not make the decision—technology supplies the evidence, and the human makes the call. In the final, France 4-2 Croatia, I watched referee Nestor Pitana manage two penalty-area reviews. It taught me that VAR is not a decision machine; it is an evidence machine.

And in 2026, when the world stopped, I called Borussia Dortmund 4-0 Schalke from Delhi. Zero fans in Signal Iduna Park. Referee Deniz Aytekin's whistle echoed through the empty stands. I logged 22 fouls, four yellow cards, and the players' shouts. That empty stadium taught me that silence itself can be testimony. And it led me to today's question—when the data is gone, what remains?

Let us go back to that blank screen. When the ball-tracking feed died, a decision was hanging in front of me: out or not out? I had three things—the live picture, one blurry replay angle, and my own eyes. But the thing I did not have was the most important: neutral, machine-independent proof of whether the ball pitched in line with the stumps.

This is where modern cricket's hidden error lives: we mistake the presence of data for the integrity of data. If a graphic is on screen, we assume the information is correct. A dot, a line, a percentage—the eye trusts what it sees. But if that dot is one frame early, if that line was never calibrated, the whole decision stands on a falsehood and nobody notices.

Think about it. The fate of an LBW review rests on three things: where the ball pitched, where it hit, and where it would have gone. All three are measured by machines today. But who measures the machine? Who verifies that the camera was mounted correctly, that the frame rate was right, that the tracking software was calibrated? The answer: almost nobody. We trust the machine because the machine never hesitates. But never hesitating and being correct are not the same thing.

DRS was first used in 2026, in a Test between India and Sri Lanka. Nobody then imagined that sixteen years later it would become cricket's most discussed—and most disputed—instrument. To my eye, DRS is really chasing three answers: where the ball pitched, where it struck, where it would go. But each of those answers is a sum of a camera, a piece of software and an estimate. The machine makes the estimate, and we accept that estimate as truth.

I am not saying technology is bad. I am saying technology produces a document, and the integrity of that document is the real question. The data cricket now generates—ball by ball, field placement, sprint speed, spin revolutions—is so vast that no human can hold it in memory. So we store it on servers, in clouds, in databases. And a database is a relationship of trust: we trust that whoever runs it will not change it.

But how firm is that trust? Suppose someone altered a match's ball-tracking data after the game. Suppose a fitness reading was changed to keep a player out of selection. Suppose that in a spot-fixing investigation, nobody could prove the data used as evidence was truly untouched. These three possibilities are not separate—they are three faces of the same weakness.

This is where blockchain becomes relevant, and it is not fashion, it is the answer to a need. What is a blockchain, really? It is a ledger no single party can change, because every page is written across thousands of computers at once, and to change one page you must change them all—effectively impossible. In cricket's language, it is a scorebook where every run is written into every copy in the world the moment it is scored, and no one can later change the number with a pen.

Imagine what this could do in cricket. Every step of an LBW decision—pitch, impact, projection, and the umpire's final call—could sit in an immutable record. After the match, if anyone asked, it would be visible exactly which frame the ball was measured in, from which angle, on which software version. Errors could be proven, not hidden.

Player fitness and medical data could work the same way. Injury records, rehab progress, workload—if all of it sits in an immutable ledger, no one can claim the data was lost. And in spot-fixing investigations, where the chain of evidence is the greatest weapon, blockchain could be that chain, unbreakable. Picture every delivery of a suspicious over preserved so that not a single dot can be erased—how much easier the investigator's job becomes.

Smart contracts are imaginable too. When a player's contract conditions are met, payment releases automatically, and that transaction is recorded in the same ledger. Franchise leagues have already begun using this technology for fan tokens and ticketing. The question is no longer about the technology's usefulness; it is about time.

Here a lesson from 2026 returns to me. Charting VAR checks in Russia, I saw that every check carries a timestamp, a sequence number. If that sequence changes anywhere, the whole explanation becomes meaningless. Cricket is the same. The value of a DRS review lies not only in its outcome but in the accuracy of its documentation. A review whose steps cannot be verified is not credible—however correct the result.

But blockchain solves one problem and creates another. If all data is immutable, then bad data is immutable too. If a sensor misreads, that error is carved in forever. This is why blockchain alone is not enough. You need a layer that verifies before carving—a sensor-level check, a cross-source reconciliation, a human observer. Otherwise we gain data integrity but lose data truth. And integrity without truth is only a perfect lie.

And here cricket's own ancient lesson returns. The nineteenth-century scorebook was handwritten, but it was written by a human who was present, who saw the ball with his own eyes. The book was not a machine; the book was a witness's memory. Blockchain can give us that witness's role—but without a witness, the ledger sees nothing on its own. Data does not become true by itself; data becomes true when someone stands behind it.

Now to the part where I hesitate most, and where my colleagues disagree with me. Many believe that as technology grows, controversy will shrink. My experience says the opposite. I charted 455 VAR checks in Russia, and after each check the argument grew a little, never shrank. Because technology does not make the decision; it places the decision under suspicion. A call that once happened in the blink of an eye must now pass through three angles, two frames and a graphic—and controversy is born in that very passage.

I trust the momentary body more than the machine, and the machine's later arithmetic less. This is not nostalgia; it is method. The machine is right, but the machine is incomplete. The machine can say the ball pitched in line, but it cannot say how tired the batsman's legs were, how much the pitch had broken up, how frustrated the bowler was. Cricket's decisions are never made by numbers alone; they are made between numbers and story. Blockchain can give us the number, not the story.

And there is a danger nobody mentions. While we talk so much about data integrity, we forget that the biggest data breach happens in the quietest places—a scorebook room, a spreadsheet, a selection committee's email. Blockchain can make that room transparent, but who sits in that room, blockchain cannot change. Technology can open the door, but what lies behind the door is not in technology's hands.

So my final position is clear. The greatest enemy of cricket's information system is not technology; it is blind faith in technology. And its greatest friend is not technology; it is the marriage of technology and witness. I do not fear technology, and I do not write without it. But when someone says the machine has spoken, therefore it is true, my referee's mind pauses. Because I have heard how loudly a whistle sounds in an empty stadium, and how it leaves a man alone.

I know this position is uncomfortable. In cricket today, everyone's eyes are on technology as the path to liberation. If DRS is perfect, controversy falls; if ball-tracking improves, decisions become exact—the promise is sweet and partly true. But what I learned at forty-seven, from a whistle in an empty stadium, is this: a perfect process and a just outcome are not the same thing. The process can be flawless while the outcome is unjust—and only humans can catch that.

That night in the Delhi studio, when the feed returned, I made a decision. It was one sentence: I will not speak without data, but I will not stay silent in the name of data either. The blank screen taught me that the absence of proof does not mean denying proof; the absence of proof means admitting we still do not know everything. And every honest analysis begins with that admission.

In the next five years the question of blockchain and data integrity will only grow louder in cricket. Franchise leagues have already begun using the technology for fan tokens and ticketing; only the timing is in question. But the real revolution will come when every step of an on-field decision—the umpire's call, the review's data, the basis of selection—is written into a ledger no one can change alone. That day cricket will not only be more transparent; it will be more honest.

Yet one question remains, and I throw it to you. If every decision is carved in forever, where does forgiveness live? For the umpire who erred, the sensor that misread, the selector who chose wrongly—where will the second chance be kept? Cricket, the game, is less about decisions than about second chances. Blockchain will give us truth, but not mercy—and perhaps that mercy should stay in our own hands.