The Testimony of an Empty Ledger: Cricket's Ledger Is Its Blockchain

A file arrived, and every cell in it was empty. The analytical framework was printed in full — format, match character, player technique, team positioning, league commerce, governance, risk, public sentiment. But where a number should sit, one sentence kept returning: insufficient information, cannot assess. A whole structure stands upright with not a single brick inside it. After twenty-six years of keeping a ledger by hand, I know an empty page does not lie; it is the full page that is given the chance to lie. The first page of the Bangladesh Premier League ledger I began by hand in Khulna in 2026 was exactly this blank. This morning, tea in hand, I understood that empty grid is not a void — it is an accusation, a duty, and cricket's ledger can never dodge that duty.

In 2026 I interviewed the rising batsman Soumya Sarkar for The Daily Star; the piece was later picked up by Prothom Alo, my first verifiable byline. That day I learned that a name, a date, and a number are the foundation of testimony. Without a name an event is vague, without a date an event is untrue, and without a number an event is mere decoration. That lesson became the method of my whole working life.

In 2026, at sixty, I left a thirty-one-year sub-editor's desk at a Khulna daily. The decision was silent, almost secret. Into my hands came a spiral notebook and a laptop with a cracked screen. The Bangladesh Premier League began — twelve teams, sixty-six matches. I counted and logged every pass of every match by hand. Four thousand one hundred and eighty passes accumulated in those spiral pages. At two in the morning I rewatched streams and coded pass-per-defensive-action and shot quality. No one paid me; no one asked.

I began with a hand-coded ledger, and the numbers learned to confess. When new-media outlets needed figures, I emailed my ledger free to three websites and two clubs and asked for nothing back. Within a year, four of them were quoting "the Khulna numbers" without knowing whose they were. That was my first block — anonymous, but verifiable.

Since then I have stopped writing "deserved to win." I write "won the shot battle 2.1 to 0.7." Every claim now carries a figure I can open to. And I date every note, so a reader can trace a trend instead of trusting a mood.

Cricket's Ledger Is Its Blockchain

The link between blockchain and cricket is not a metaphor; it is structural. In a blockchain each block holds the hash of the previous one, and the chain can only be extended, never rewritten. The cricket scorebook is exactly this. An over is a block; beside it sit runs, wickets, the bowler's name, the batsman's name. You cannot erase that over and write it anew. If you err, what you can do is append a correction in the next block — exactly as I printed my error before anyone asked.

I am a data monk; I sweep the same columns until they become prayer. This discipline taught me that a ledger's beauty is not in its completeness but in its verifiability. A number I cannot open to is a rumour to me; a number I can open to is my testimony.

The Hand-Coded Ledger: A Stubborn Witness

Why keep a ledger by hand when cameras and sensors exist? The answer is not simple. Broadcast statistics show the viewer who scored how many; my ledger shows where pressure accumulated. Take an innings strike rate of 130 — television calls it skill. But if my ledger shows that inside that 130 sit four consecutive dot balls followed by a boundary, the story changes. Where were the fielders during those dot balls, who was bowling, how much energy remained — all this detail vanishes into the broadcast number.

In the margin of my spiral ledger there are always small notes — which ball the batsman let go, which over he slowed to a walk, how his first three balls after the drinks break looked. None of this appears in a highlights package. Yet pressure, fatigue, and character hide precisely in those margin notes.

A number does not speak on its own; it must be given context. Runs, wickets, strike rate are raw material. When I read them against time, against field placements, against the bowler's remaining energy, the number becomes a ledger.

The Threshold Line: Where a Match Changes Its Mind

The sixtieth-minute line is not a statistic; it is where a match changes its mind. In football that line is visible; in cricket its equivalents are hidden. Cricket's threshold lines are several — the over immediately after the drinks break, the spell after a wicket, the first two overs with the new ball, and the first ball of the last ten overs. At these points the game's intention shifts, and the ledger must record a new voice.

I have seen many times how, in the over after a wicket, the attacking side suddenly doubles its aggression, because a new batsman's first few balls are the most uncertain. But if statistics show only the match average, this instant transformation is missed. It must be caught through over-by-over notation.

This is why I keep one minute-window prediction in every preview, with a metric behind it. This is not the arrogance of prophecy; it is the discipline of holding my own eye accountable. If the window is wrong, the ledger will record it, and I will admit it.

Croatia, 2026: The Confession of an Error

In 2026, at sixty-one, I built a fatigue curve for Croatia before the World Cup final in Moscow. Croatia had played three consecutive extra-time knockout ties — Denmark, Russia, England — past 360 minutes. From distance covered and sprint counts I predicted France would take the midfield after the sixtieth minute.

France won 4-2, scoring in the 59th, 65th, and 81st minutes. I had the window right and the sequence wrong. I thought fatigue would bite slowly; in reality France broke a collapsing Croatia into pieces. I printed the correction myself before anyone asked.

Here lies the ethics of the ledger. Making an error and burying an error — the difference between these two defines an analyst's honesty. Writing "I had the window right but the sequence wrong" brought me no shame, because the error was written in my ledger with a date. After that, I added a short line at the bottom of every report — "What I missed." That habit later earned a Dhaka club's trust, and the next spring they hired me as their first data consultant.

The Number of Distance: The Counterfeit Coin of Effort

Distance covered and high-intensity sprints are packaged as effort metrics. I do not believe it. Pointless running also produces pretty numbers. A player who sprints to the wrong place and back will be recorded as covering more distance than a disciplined player.

My question was never "who ran how much" but "why did he run." If a midfielder covers ten extra metres on average because his teammate was out of position, those extra metres are not his credit but evidence of his teammate's shortfall. Yet the broadcast graphic turns it into a number of pride.

This is why I look to metrics like PPDA, which measures the effectiveness of pressing, not mere effort. Low PPDA means a side is winning the ball quickly; high PPDA means a side is sitting back, letting the opponent pass. The same team can show two different PPDA values in two halves of the same match — and that difference matters more to me, because it is a change of tactics, not just of sweat.

The Shadow of Five Substitutions

The five-substitute rule benefits deep squads — this is now almost universally accepted. But my ledger has shown me another, less-discussed side. This rule lets big clubs turn the final twenty minutes into a war of attrition.

Imagine a side that can bring on three fresh substitutes in succession after the seventieth minute and attack a tired defence continuously. The character of the final twenty minutes changes. This is no longer a battle of tactics; it becomes a one-sided test of physical endurance. The side with a deep bench can play against the clock in the last twenty minutes; the side with a shallow bench fights to survive that period.

In my hand-coded ledger I have seen how a team's passing rhythm shifts after the sixtieth minute if their first eleven's average age is high and their bench is light. The numbers say the last twenty minutes are no longer part of the match; they are a separate sub-match with different rules.

Injury: The Price of Confidentiality

I hold a fixed position on injury, built from two decades of observation. Medical confidentiality leaves fans and media blind; clubs disclose only the injuries that suit their stock price.

Consider this. A star player pulls up clutching his hamstring. The club quickly announces it is ordinary fatigue and that he is ready. But who knows he is actually out for three weeks? Fans bought tickets for the big match seven days later on the basis of that information.

I do not call this practice cruel; I call it professional. But as a ledger-keeper, my work is to ask a different question: after how many minutes did his sprint speed begin to fall? If I see a steady decline in his average sprint speed across the last three matches, I have the right to be suspicious, and I will record it in my ledger with a date.

Often the only way to learn the truth about an injury is over-by-over notes: which ball he let go, which fielding effort he hesitated on. The field never lies; the press conference sometimes does.

The Grammar of Silence

Silence has a grammar, and empty stadiums taught me to parse it. When stadiums stood empty during the pandemic, I discovered that crowd noise conceals much of the game's information. In an empty ground you can hear the bowler's footfall, the echo of bat on wood, the snap of the wicketkeeper's gloves. Those sounds are a separate ledger, lost in the roar of the crowd.

A rain delay is also a grammar. When play stops, a blank line sits in the scorebook — how many minutes it paused, how many overs were lost, whom the Duckworth-Lewis rule favoured. These blank lines are not filled, because they are not meant to be filled; they are testimony that time itself is a player.

The silence of a DRS pause is another kind. Appeal, wait, then the result on screen. In those few seconds a match's emotion gathers. I do not write those with numbers; I write them with a dash, because a dash is a pause, and the pause is the event.

The Ethics of the Empty Ledger

Now back to that empty file. The whole structure is printed, but every cell is blank. Someone could have filled those empty cells with imagination — inserted a team's name, invented a player's name, fabricated a number. No one would have noticed. But doing so would stop the ledger from being a ledger; it would become a rumour printed in a beautiful font.

I have never placed an invented number in my ledger. Because a false block makes the entire chain untrustworthy. The core lesson of blockchain is this: if one block is corrupted, every block after it falls under suspicion. So the empty cell is not a shame to me; it is a warning, a duty.

This empty file has a positive side too. It reminds me that an analysis is valuable only when it carries a name, a date, and a verifiable number. What is absent, I will not write. What is present, I will write with a date. Between those two lines stands the entire profession of a ledger-keeper.

The Contrarian Angle: A Full Ledger Also Lies

Let me say something uncomfortable, which works against my own profession. We generally assume more data means more truth. My experience says the opposite. A full ledger is far more dangerous than an empty one, because a full ledger gives you the chance to lie — a lie dressed in statistics.

Correlation is not causation. If a team runs more and wins more, it does not follow that they won because they ran. Perhaps they won because the opponent was weak, because the pitch suited them, because luck was on their side. But the graph draws a straight arrow — more running, more wins — and the reader believes the arrow.

I will criticise myself here too. In 2026 I presented Croatia's fatigue curve with such confidence as if fatigue alone would decide the result. But Croatia scored in the first half; they only collapsed late. My curve pointed in the right direction, but I had simplified the cause. So my caution is this — an analyst who speaks through numbers, if he is not the most careful of all, is no less harmful than a journalist spreading rumour. Numbers do not lead to truth; numbers only give testimony, and testimony without interpretation is meaningless.

What I Missed

In this piece I missed one thing — a specific scene from a specific match where I could place a direct number. Because what I had in hand was that empty file, not the account of any particular match. So I wrote about method, not about claims. That is the right work, because writing a number without verification corrupts the ledger.

Forward Look

At sixty-nine, I trust slow numbers more than loud ones. In the next round my eye will be on three places. First, which team's PPDA changes in the first over after the drinks break — that will tell who is trying to change the match's mind. Second, which team's passing rhythm breaks after the sixtieth minute — that will tell how deep their bench is. Third, which star player's sprint speed is declining across three consecutive matches — that may be an early signal of injury, which a club will never admit.

And one question remains open in my ledger. If I have before me a full file and an empty file, which do I read first? I know: the empty one. Because the full one does not teach me to ask; the empty one does. And the whole work of a ledger is in the asking. My spiral ledger now sits in my assistant's hands; I gave it to her in the belief that she will know how to ask, not how to imagine.