The Scorebook's Blockchain: The Over Nobody Wrote Down

Dusk was settling over the ground. A Dhaka First Division match, an open ledger on the scorer's table, the ink already drying on the pen. Beside the 37th over, the box was blank — no bowler's name, no runs, not even a ball count. And yet the over happened. Six deliveries, one tired seamer, a catch put down at slip. It occurred on the field; it simply never occurred on paper.

I stared at that empty box for a long time. I kept thinking: if an over is written down nowhere, did it really happen? Cricket has its own blockchain — from the scorer's ledger to the board's database, then to the online scorecard archive. Every record is a block, chained to the one before it. When a block goes missing, you don't just lose that over; the credibility of the whole chain is called into question.

A large share of the country's domestic cricket never happens in front of a camera. The National Cricket League, the First Division, the age-group tournaments — most of those matches have no live stream, no ball-by-ball tracking. What they have is one scorer, one ledger, and occasionally a torn score sheet. On 9 February 2026 in Potchefstroom, Bangladesh's Under-19 side beat India by three wickets to win the World Cup; Akbar Ali captained that team. We all watched that final, every ball logged on the scorecard. But when the same players turn out three years later on a domestic ground, their best innings may never reach any database at all.

I remember 2026. I was live-tweeting a World Cup from a tea stall on Sadar Road, four or five men sitting on a mat beside me. Nobody was watching the score; they read the shouting to work out who was winning. I understood then that one part of cricket lives on the field and another part lives in people's memory. But memory is not a record. Memory leaves; a record stays — if someone writes it down. I learned the game from the light behind me, not the applause in front. That coach, that groundsman, that family — none of them ever appears on a scorecard.

For me, cricket's blockchain splits into three layers. The first layer is the ground's scorebook, written by hand. The second is the board's official database, where it is typed up. The third is the public archive, where anyone can see the data. Each layer needs verification, a cross-check. But in our reality there is often no bridge between the first layer and the second. The scorer's ledger is lost before it reaches the board's file, and the match never becomes complete at the third layer.

That is where the real problem sits. We live in the age of data, yet much of our domestic cricket still stands in the age of the handwritten ledger. A leg-spinner takes five wickets in three straight matches, but the score sheets for two of them are soaked through by rain — and the proof of his form disappears with them. What does a selector look at? Who sets the value of a contract? Whose ledger records the stipend?

Losing an over means losing the count of six deliveries — and with it, the evidence of a possibility. Inside Bangladesh's domestic structure there is an invisible gap between performance and recognition, and that gap lives precisely inside those empty boxes. The boy scoring day after day on a matting wicket in a district town never reaches a major database, because no data-entry operator was at that match. Selection still runs largely on a mix of score sheets and memory. A selector watches video of three games and decides — but who decides the fate of the boy for whom no video exists?

In English county cricket, every ball is logged as data; in Australia's Sheffield Shield, every innings is captured on video. Our domestic structure has not yet fully acquired that capacity. It is a shortfall, but it is not an excuse. Because information that does not exist cannot be filled in with guesswork — it can only be admitted.

Think about 2026. Five weeks after the Under-19 World Cup win, the BPL was suspended, and 14 women's national-team players went five months without stipends. I gathered testimonies from eleven of them, took written consent from each, and published their names. That period taught me one thing: without a record, a grievance does not hold, and without a grievance that holds, there is no reckoning. A stipend date is a record too, and losing it means losing the account of someone's existence. Unpaid stipends taught me that passion is not a payment plan.

I spent six weeks with Bashundhara Kings, counting pressing triggers from the touchline, riding the team bus, eating in the same canteen. In that time I learned that a record belongs not only to the match but to the training session. Who stayed back for extra fielding today, who kept running after the lights went out — none of that reaches a scorecard, yet the team's inner truth lives exactly there. In January 2026, at the trophy press conference, a veteran editor told me in front of thirty colleagues, "Ask a simple question — tactics aren't your area." The next morning I filed a 4,200-word breakdown of the Kings' rest defence, and it was shared 6,000 times.

There is nothing romantic about this gap, and I am not looking to assign blame. The problem is structural. If a country plays thousands of domestic matches a year and its digital-recording capacity is not even a quarter of that, empty boxes are inevitable. The question is how we handle those gaps.

And that is where the most common mistake occurs. We assume that no data means nothing happened. The opposite is true — no data means it happened, and no one kept a witness. In cricket analysis this is the most dangerous assumption of all. Treating an empty box as a zero erases a player's very existence.

There is one more thing we forget. The pressure to record everything forces us to fill in templates. When a box sits empty in an analysis, the urge to fill it becomes overwhelming — and from there come assumptions, and from assumptions, narrative. But a washed-out day having no lesson is its own truth. If an analysis cannot accept an empty box, it stops being analysis and slips into story.

And yet this is also true: not every over needs to be recorded. A bowler's action graph, a word from the dressing room — these have limits. Verify where it matters; stay quiet where it does not. A league-table point tolerates no true-or-false, and neither does a stipend date. After nine years of watching from the ground, this much I can say — when the stands emptied, I heard which players still ran for the badge.

The light faded and the scorer closed the ledger. That empty box stayed empty. Who knows — the man who bowled that over may return in another match, or he may not. But one question stays with me: how many players in our cricket have been lost today only because no one kept a record of their finest day?