The Honesty of the Null Block: Cricket Ledgers, Data Integrity and the Lesson of Blockchain

Hook

It was 2:40 in the morning. The ceiling fan in my Khulna home turned slowly, and on the table lay my old spiral notebook, open — the notebook in which every Bangladesh Premier League match since 2026 has been hand-coded. Beside it, a blank box glowed on my laptop's cracked screen.

Inside that box, the analysis of the work sent to me had come back effectively empty-handed. No title, no source, no information points, no names, no assessed time sensitivity. Every cell carried the same sentence — not applicable, insufficient information, cannot assess.

This is the moment that tests a ledger-keeper, when the temptation to fill the blank box is strongest. Guessing can add colour, imagination can fill it in, and the reader can be won over. I did not do that. Because that small decision determines whether a ledger becomes a document of truth or a collection of beautiful stories.

Context

The cricket data market today is a flood. Twenty numbers are born every over, hundreds of data points pile up on servers every match, and every week someone invents a new index and claims a headline. Numbers are not scarce. Evidence is.

In 2026, at sixty, I left a thirty-one-year sub-editor's desk at a Khulna daily. I had come to feel there was a gap between the first draft of news and the final truth, and no one had built an instrument to measure that gap. Since then I have kept a hand-coded ledger — one column for the ball in a spiral notebook, another column for the person behind the ball.

That ledger accumulated twelve teams, sixty-six matches, four thousand one hundred eighty passes. At two in the morning I rewound the stream and coded PPDA and shot quality. When new-media outlets wanted numbers, I emailed my ledger free to three websites and two clubs and asked for nothing in return. Within a year, four of them were quoting "the Khulna numbers," and none knew whose they were.

That is how I understand blockchain. A distributed ledger is valuable precisely when every entry can be verified and no single party can rewrite history. My hand-coded notebook is such a ledger — only made of paper.

Core Analysis

I began with a hand-coded ledger, and the numbers learned to confess. The first lesson of that education was not what to add, but what not to add.

The way this task reached me was a perfect mirror of today's data culture. The first stage of an analytical process came back empty-handed. No title, no source, no information points. If someone wants to grow in the world of numbers, there is no greater opportunity — to plant one's own story in the blank space. No one will catch it. No source means no liability.

My old habit said otherwise. An entry sits in the ledger only when there is a verifiable piece of evidence behind it. Without evidence, the cell must stay empty, and a date must sit beside the empty cell — so that anyone later can see that on that day I did not know.

A Null Result Is Itself a Result

In the language of science this is called a null result. When an experiment finds nothing, the not-finding is also knowledge. The crisis of suppressed null results in drug research is more acute in cricket analysis. No one wants to write "we found nothing," because editors want headlines, readers want drama, sponsors want numbers.

But what does an empty box actually say? It says that what is here is not measurable. In the world of blockchain this idea is familiar — an empty or null block is a valid block. The chain does not break because a block contains no transaction. The integrity of the chain depends on sequence and verification, not on the fullness of content.

That parallel is the most precious thing to me. A ledger need not look full; it must look honest.

The Hand-Coded Ledger: Paper's Forerunner of the Blockchain

At sixty-nine, I trust slow numbers more than loud ones. Every page of my notebook carries a date. Beside every coding, in small letters, I note where the information came from — a stream, a scorecard, or my own eyes at the ground.

This habit looks ordinary, but its internal logic resembles the blockchain. In a blockchain, every block carries the hash of the previous block, so if anyone alters an entry in the middle, the whole chain fails to reconcile. In my notebook, dates and sources do the same work — to alter an old entry, one would have to reconcile every adjacent date and piece of evidence. No one can do that alone.

I am a data monk; I sweep the same columns until they become prayer. Integrity is built in that sweeping. In blockchain it is called immutability, but the name is nothing grand. The real point is that no one should be able to write history quietly.

Distributed Ledgers and 'the Khulna Numbers'

That decision in 2026 still amazes me. I sent my ledger free to three websites and two clubs. I did not think then that I was creating a distributed ledger.

A centralised ledger has one owner. If they wish, they can delete an entry or change the accounts unnoticed. In a distributed ledger that is hard, because the same information lives in many hands. When my numbers reached four separate organisations, they were no longer mine alone. If one changed something, the others would catch it.

So when someone quoted "the Khulna numbers," I was not annoyed. Even without my name, the numbers were verifiable. The ledger's job is not to claim ownership but to keep the evidence alive.

Consensus, and the Limit of Speaking Truth Alone

The most discussed word in blockchain is consensus. For a transaction to be valid, many nodes must agree. Cricket analysis needs a version of this too, and it is often missing.

When one analyst states a number alone, that is not consensus; it is an announcement. This is my old familiar crisis. Alone I may be right or wrong, and how will the reader tell the two apart? The only way is to leave the evidence behind the number, so that someone else can come and check.

That is why I keep a receipt behind every claim. Without a receipt, a number is a beautiful word to me, not a truth. And in cricket's data market, beautiful words are never in short supply.

The Croatia Block and the Self-Filed Correction

Think of the 2026 World Cup final. Croatia came to Moscow having played three consecutive extra-time knockout ties — Denmark, Russia, England — past three hundred sixty minutes. From distance and sprint counts I drew a fatigue curve and said France would take the midfield after the sixtieth minute.

France won 4-2, with goals in the 59th, 65th and 81st minutes. The sixtieth-minute line is not a stat; it is where matches change their minds. I had the window right and the sequence wrong.

Here was born the most important habit of my life. You can place a new entry in the ledger without verification, but you cannot hide a wrong entry. Before anyone asked, I printed the correction. Filing one's own error does not reduce the ledger's weight; it increases it. Because then the reader knows this hand has not learned to hide.

In blockchain language, this is a new block — not erasing the old one, but placing a correction on top. History remains immutable, and a further layer of truth is added above it.

The Oracle Problem: Garbage In, Garbage Out

Blockchain has a notorious weakness called the oracle problem. However secure the chain, if the information entering from the outside world is wrong, the chain immortalises that error. The old computer-science saying is the same — garbage in, garbage out.

In the world of cricket numbers this appears almost weekly. Someone presents distance covered as proof of effort. But a player who chases back and loses the ball adds distance, and the ledger records effort, while the team gains nothing. The number is beautiful; the meaning is hollow.

So I never trust a single metric alone. Behind every claim I want a context — who ran, why they ran, what the team's outcome was. This layer of verification is the cricket version of the oracle problem. If the input is not verified, however fine the ledger, its interior is hollow.

The Chain of Evidence: From Scorecard to Field Map

I do not claim my eyes see everything. But I have a chain of evidence. The first layer is the scorecard — balls, runs, wickets. The second is over-by-over notation, where I record line, length and player positions. The third is the field map, where I see which fielder moved where.

Together these three layers form a picture the broadcast screen never shows. Television shows the final result; the ledger shows the path to it. If the reader can see the path, they too can verify, rather than trusting my word blindly.

Silence has a grammar, and empty stadiums taught me to parse it. Rain breaks, the DRS pause, the abandoned chase — these gaps deserve entries in the ledger too, because these gaps tell where the match changed its pace.

The Validity of the Null Block, Again

Now back to that empty box. Every cell of the analysis sent to me was empty. The temptation was to invent a story — an artist, a venue, a thrilling comeback. No one would catch it, because there was no source.

But a truth without a source is no truth. A ledger is valuable when every entry has evidence behind it. Without evidence, the best entry is the unwritten one. In blockchain an empty block does not break the chain; it is part of the chain. Likewise, an honest "I don't know" is not a failure; it is the natural result of a verification process.

I never forget that an error can be corrected, but once invented information spreads, it cannot be recalled. In a distributed ledger, false information spreads fast, because many nodes carry it. Cricket news is now distributed in exactly that way — once a falsehood is released, the correction sits later in a small corner.

The Data Economy of Cricket and the Temptation

Now every franchise has its own analyst, every broadcast a storm of graphics, every venue a GPS tag. There is so much information that readers no longer have the patience to verify. That impatience is what breeds temptation.

A club releases information convenient to its share price and suppresses the inconvenient. In injury news this is almost the rule. Behind the shield of medical confidentiality, fans and media stay blind, and empty spaces accumulate in the ledger. Yet those empty spaces are the real clue to tactics. Knowing who is absent, and for how long, makes a pre-match forecast far more honest.

My old habit serves here too. Where there is no information, I do not place a guess; I place a date beside the empty space. Later anyone can see that on that day the information was withheld, and the withholding was itself information.

An Old Byline, an Old Lesson

In 2026 I interviewed the young Soumya Sarkar for The Daily Star. It was printed in Prothom Alo, and it was my first verifiable byline. I did not understand then that the piece was teaching me a lifelong habit — standing behind one's name.

A byline means responsibility. If someone states a number wrongly, an answer is owed. If someone misinterprets, a correction is owed. Numbers without a name have an advantage — no one can demand accountability. But numbers without a name carry zero weight.

From that belief, every page of my ledger carries my handwriting, my date, my evidence. Anyone who wishes can verify the whole chain, link by link.

The Contrarian Angle

The obvious question will come: what is the need for so much verification? The reader wants numbers, not philosophy. Give a quick answer and you get a headline, and you pull ahead of rivals. This argument is the most dangerous of all.

Because where competition is about speed, honesty is slow. Those who fill empty spaces with guesses may win first, but once the market's trust breaks, it does not return. A single invented fact, caught once, can reduce the weight of a twenty-year hand-coded ledger to zero.

My sixty-nine years tell me the real arena of competition is not the quantity of numbers but the credibility of numbers. An outlet that proceeds slowly but verifies endures, because readers know too that falsehood is fast and truth is slow.

There is another confusion, the one we call mistaking correlation for causation. When two things rise together, many assume one causes the other. Cricket is full of this error. A team scored more runs, or ran more sprints — these numbers are beautiful, but whether they caused the result must be verified separately. Here the ledger behaves like a gentleman; it shows relationships, and demands proof before claiming cause.

Takeaway

I did not fill that blank box that night. Instead I placed a date beside it and wrote — on this day the information was so incomplete that the honest answer was "I don't know." Next week, when the real information arrives, I will place a new block; I will not erase the empty one, I will add on top.

What blockchain teaches me, the cricket ledger says too — honesty is not a one-time event; it must be proven again in every block, in every entry. And to do that, one must walk behind the numbers, not lean on them.

Reader, the next time someone shows you a beautiful number, ask one question — where is its source? If there is no answer, know that you are hearing a story, not a ledger.

What I Missed

I could not touch one thing in this piece — the financial logic of why franchise clubs suppress injury information. That account demands a separate ledger, and that writing I will keep for next week.