The Discipline of Verification: Cricket's Data Gaps, the Notebook's Silence, and the Promise of Blockchain

Rain arrived in the seventh over of the second innings. In the press box, some were working through Duckworth-Lewis-Stern calculations; others had their laptops open, racing to type the word "breaking." I opened my notebook and left a line blank, because nobody yet knew what the target would be. The colleague in the next seat whispered, "You have to file something, the desk is waiting." I said, "If I write what I do not know, that is not reporting, that is guessing." That blank line filled in later, once the match official's sheet reached my hands. But those ninety minutes of silence reminded me again: cricket journalism is not only about ball and run; it is a long chain of verification, and every link carries equal weight.

After nearly nine years standing beside the boundary, I have understood one thing. A reporter's greatest enemy is not the lie; it is the blank space. People fill blank spaces on their own, because the mind dislikes a gap. And yet cricket's real stories often hide precisely in those gaps: the fact that has not arrived, the innings not yet written, the injury nobody wants to name.

A Flood of Data, a Drought of Verification

In today's cricket, the volume of information resembles an explosion. Every ball's pace, spin revolutions, bat swing, fielding maps, wagon wheels, all of it surfaces on screen in real time. Hawk-Eye, Snicko, UltraEdge, ball-tracking: these technologies have transformed umpiring and, alongside it, the pressure on a reporter's work. Once a journalist trusted their own eyes and the coach's spoken word; now they watch a live data feed where numbers shift second by second.

But there is a reverse side to this abundance. The more information there is, the greater the risk of false information, and false information travels several times faster than fact-checking does. One screenshot, one tweet, one "sources say," and within moments it becomes the belief of thousands. In my experience, the correction post never travels like the first post. The correction sits quietly in a corner; the error keeps dancing in the middle of the field.

This reality has turned cricket into an economy where information itself is a product. Broadcast rights, streaming deals, live graphics: data sits at the centre of all of it. Big leagues sell a separate data point for every ball, and the fan buys it as food for thought. Yet the question remains: how much of this vast information is verified, and how much is merely circulated?

The lesson became sharper inside the 2026-21 ISL bio-bubble. In that Goa bubble, information was tightly controlled: who could meet whom, who could say what, all bound by rules. A senior player's injury was steadily worsening, but the team wanted it kept quiet, because their tactics before the final depended on it. For a young journalist sitting there with a camera and a keyboard, that was a hard test. I did not put that specific detail on social media, because it was still unverified, and if word of an uncertain injury spread, someone's career could be damaged. Later, in that final, Mumbai City FC beat ATK Mohun Bagan 2-1, and the 18th-minute goal was scored by Bipin Singh (jersey number 29). But the biggest lesson of that match for me was something else: publishing information is a decision, and withholding information is also a decision; both carry equal responsibility.

Empty stadiums taught me that silence still has a beat. During the pandemic, when the stands were bare, every sound could be heard distinctly: the tap of spikes on the pitch, the knock of ball on stump, a laugh drifting out of the dressing room. In that silence I learned that what is not heard is also information. That habit taught me that verification means not only seeing what is present, but also noticing what is absent.

Blockchain and Cricket's Immutable Ledger

Blockchain's core promise is simple: once a record is written to the ledger, no one can quietly alter it. Information that has once been verified and entered into the chain carries an irreversible history. Cricket's problem sits exactly here, since our game's history is still written across countless separate books, by separate hands, for separate interests.

Imagine if even a single under-16 scorecard were written to an immutable ledger. Years later, when that boy is called up to the national team, his childhood performance would also remain verifiable. For scouts this matters enormously, because today's talent-hunting often depends on word-of-mouth stories, and stories change.

My first big break was exactly this kind of small match. In the Mumbai Youth League, the Mumbai City FC under-18 side beat Pune City under-18 3-2, and the 89th-minute winner was scored by defender Nikhil Kadam (jersey number 5). After the match I waited forty minutes in the tunnel and got one single sentence, about his father's daily train commute. That one sentence, that one wait, turned the direction of my career. I learned the rhythm in the under-18 tunnel long before I ever heard the crowd. And I learned that the most valuable fragment of information often sits in the least noise.

If the records of those under-16 and under-18 matches were stored on a blockchain today, the stories would not be lost. Rural cricket in Bangladesh, tape-ball tournaments in India's smaller towns, Morocco's fledgling cricket movement: their records are not properly written anywhere. They move by word of mouth, and then they vanish.

This problem is even more acute in women's cricket. Since my field of work is women's sport and national-team tournaments, I have seen it up close: where men's cricket has ball-by-ball data going back a decade, many women's matches still have incomplete scorecards online. The result of an under-19 girls' tournament is often confined to a small box in a local newspaper. When a future star rises, the data of her childhood cannot be found. Without data, the story of a career journey itself disappears, and without a story, a star is not made.

Change is arriving on the fan side too. Fan tokens and digital collectibles have stepped into cricket's world. A historic six or a memorable catch now becomes a digital asset, and a fan can own it. Outside cricket, fan tokens have run in football for a long while: fans buy tokens to vote on small club decisions, weigh in on jersey design, and access special experiences. In cricket the model has arrived slowly, but it is arriving. In my eyes its value is larger than money: it gives the relationship between fan and team a verifiable, clear structure.

The most important possibility is probably in anti-corruption. Suspicious betting reports, abnormal market movement, signs of match-fixing: if these were stored on a tamper-proof, time-stamped ledger, the room for a quiet arrangement or a deleted record would shrink considerably. Cricket's anti-corruption units have fought this battle for years, often against old emails and lost documents. A transparent, immutable record could strengthen their hand, especially in Asian cricket, where the relationship between betting and the game is complex and old.

Another dimension is contracts and money. Cricket's talent is produced at the under-16 and under-19 levels, but players at those levels often do not receive proper payment. If smart contracts paid a local tournament's prize money or a coach's salary automatically and transparently, many grassroots injustices would shrink. I once saw, at a small-town tournament, a boy's winning prize money held up for months, with nobody knowing whose hands it sat in. With a transparent ledger, at least that boy would have had proof.

The Gap Between the Dressing Room and the Page

Here lies a fine line, equally relevant to blockchain and to cricket journalism. Blockchain says everything will be transparent, every record open to all. But in real life there is information that, published in the name of transparency, harms people: injury details, family grief, private struggle. My biggest lesson in cricket journalism is this: verification and publication are not the same thing. The first is a professional duty; the second is a moral decision.

This is why I want to offer a caution to blockchain's enthusiasts. Technology can make information immutable, but how that information is used is not decided by technology; it is decided by people. If an injury's data sits on-chain, the team, the opponent, the bettor, all of them can see it. Then what becomes of the player's medical privacy? The answer to that question is not in blockchain's code; the answer lives in our policy, our rules, our conscience.

I entered Morocco's dressing room by an odd route. At the Qatar World Cup, I helped a Moroccan journalist translate for a Mumbai fan, and that courtesy opened the dressing-room door for me after the Round of 16. That night Morocco beat Spain 3-0 on penalties, and goalkeeper Bono (jersey number 1) saved two spot-kicks. Across ten days I filed fourteen dispatches, on how Morocco's family travel and defensive tactics served their fans. My editor called it "the most human Morocco coverage from India." But every fact across those fourteen dispatches had to be verified, because not everything heard inside the dressing-room door is fit to publish.

The Rush to Fill Blank Spaces

Now I come to the part I object to most. Today's news environment exerts a terrible pressure: write fast, write first, write before everyone. Under that pressure, many fill blank spaces with their own imagination. "Sources say" gets written, but who that source is, how reliable, goes unsaid. A player's injury is declared "serious," though no one has seen a scan report.

I think a professional misconception is at work here. Many believe that saying "there is not enough information" amounts to weakness, a failure. The opposite is true. "There is not enough information, so no conclusion can be reached now" is a complete professional answer, and often the most honest one. A reporter who knows what they do not know actually knows the most.

Let me speak of an analysis sitting on my desk right now. Every field in it is empty: which match, which team, which player, which date, none of it. The temptation is to quickly invent something: an imaginary score, a manufactured quote. But a beat keeper does not do that. He waits, because the beat keeper listens for the pause after the crowd exhales. Within that exhalation the story is still catching its breath, and I write exactly from the mixed zone, where some information arrives and some does not.

There is a blockchain lesson hidden here too, if we think carefully. A blockchain never counterfeits a transaction. It writes what it knows, and leaves out what it does not. Blockchain does not invent non-existent information; it leaves the gap of non-existent information openly blank, so everyone can see it is not yet verified. A journalist should do exactly the same: where information is unknown, write "verification pending," not imagination.

I know this sounds like laziness. Some will say, "Then there is no news at all." But consider: if a betting-related suspicion turns out false, an innocent player's lifetime reputation is ground into dust. If false injury news spreads, a team's plans are wrecked and a player's morale breaks. The cost of that damage is not repaid by any "fast scoop." The slowness of verification is in fact a protective ring, not a weakness.

There is another trap here that I have learned to avoid: excessive emotion. When writing about empty stadiums, tunnels, silence, the poetic person inside wakes up. I stay careful. I anchor every quiet scene to a concrete observation: the sound of spikes, the rhythm of raindrops, the dimming bulb of the scoreboard. Because silence itself is not a story; the specific sound inside the silence is the story.

Empathy, and the Courage of the Hard Question

One part of my nature wants to protect players. When someone is injured, when someone is sunk in grief, I naturally step back. But over time I have learned that empathy and accountability run together. Protecting a player means challenging false news spread in their name, sometimes by standing against their own team or board. Empathy does not mean staying silent; empathy means protecting them with accurate information.

This is why I want a verifiable chain of information to grow in cricket, whether through blockchain or another technology. Because verifiability is not only technology; verifiability means an under-16 match score of a small boy, the unpaid salary of a small-town coach, the honour of an innocent player, all of it protected.

Waiting for the Next Ball

On that rainy day, when the match official's sheet finally reached my hands, my notebook's blank line filled in. But the fact that I had left it blank was the real work. Blockchain arriving in cricket data will not end the problem; as long as the rush to spread false information persists, the temptation to fill blank spaces persists too. The question is not technology's; it is ours. Do we have the courage to wait? Can we say, "I do not know yet"?

Just as a goalkeeper pauses a moment before releasing the next ball, a journalist needs a moment too: to verify, to breathe, to avoid error. That single moment of silence may be our greatest contribution. Because the game ends on the scoreboard, but the truth survives in the notebook, and the notebook never blinks.