The Ledger of Memory: Cricket, Verification, and the Lesson of Blockchain

That evening the rain came down on Khulna Stadium. It was 2026, and I had only just begun a Facebook Live segment called "The Long Throw." On a rain-soaked night of the Bangladesh Premier League, Sheikh Russell KC and Abahani Limited Dhaka drew 1-1. I set the scoreline aside and called the rain "a third team, playing tiki-taka." The clip was watched 48,000 times in 72 hours, and new-media editors began asking me for weekly voice notes. But that same night a young fan stopped me with a question: "Sir, where is this score written down? Where do I verify it?"

I went quiet. For fifty years I had stood beside the ground memorising scores, spells and sessions — but I had never kept a verifiable ledger. In that moment I understood that cricket's greatest crisis is not bowling or batting; it is the crisis of memory — a memory no one can verify. The long throw from Khulna taught me that distance is a kind of faith. And to keep that faith alive you need an open ledger that no single person can alter.

Every cricket match produces countless numbers. Deliveries, runs, over-rates, DRS reviews, Duckworth-Lewis corrections — all of them sit in a book of accounts. But whose book? The ground scoreboard's? The broadcaster's graphic? Or the morning headline's? Cricket is at once a game and a story, so here numbers and narrative travel side by side, and narrative usually wins. A dropped catch becomes, in five years of memory, "that catch" — while its official record was never written down anywhere.

I made my ODI debut in 2026 and played international cricket until 2026. In that era the main support for preserving a score was the newspaper and human memory. The numbers were mostly right, but they were not verifiable. In 2026, after a club match in Dhaka, two newspapers printed two different economy rates for one of my spells — nobody knew which was true. That uncertainty around numbers is what pulled me towards analysis in the years that followed.

This is where the lesson of blockchain becomes relevant, and it is a lesson about principle, not technology. The core idea of a blockchain is simple: each entry sits in a block, each block is chained to the one before it, and no single person can alter it alone. The ledger belongs to everyone; verification belongs to everyone. Cricket's memory needs exactly this structure — one match, one block; one innings, one entry; and behind every claim, a verifiable source.

To analyse international cricket you first need the context of the format. The second session of the third day of a Test and the last four overs of a T20 are not the same thing; the same player's strike rate tells two different truths in two formats. Reading a number without knowing the format is making a claim that has no block behind it.

Then you need a player's real numbers — average, strike rate or economy, situational splits, recent trend. The biggest trap here is the small sample. We turn two good innings into "the next big star," yet four matches of data can never write a future. In my eyes the most dangerous sentence in cricket is "he's the next Sachin." There is only one Sachin — the rest are separate blocks.

Team analysis demands the same discipline. Ranking, home-away profile, batting depth, bowling combination, bench, age structure — each is a separate piece of information. Home-ground statistics often hide a weakness; an average of 45 at home and 22 away — if those two numbers are not read together, the picture is false. The same applies to league and commerce: broadcast rights, franchise valuation, player salaries — without verification these are topics of conversation, not information.

In 2026 England toured Bangladesh. I bowled to Kevin Pietersen in the nets as an amateur left-arm spinner. In the press box that story is now a legend — some say I bowled him twice, some say three times. What is the truth? The truth is unclear even to me. A single net session, no ledger of verification, yet the story has lived on for years. This is cricket's beauty, and this is its risk.

Fifty years of experience have taught me one rule: information is often absent, but stories never are. Analysts see a gap and fill it with guesswork. I say the professionalism is not to fill the gap but to admit it. When there is no information, the correct answer is one line: "insufficient information, cannot assess." That line is not easy to write; it disciplines the writer's ego. But that is blockchain's principle too — what cannot be verified does not go on the ledger.

The conventional reading goes like this: cricket is not a game of accounts on a field, it is a game of memory and romance. Any blockchain ledger would kill that romance, because a story lives in its blurriness. I give that argument full weight — I myself call rain "a third team," painting a picture instead of a number. Without romance, cricket is just a corporate spreadsheet.

Yet this reading misses one thing: unverified memory does not last, and what does last is usually the strong man's version. We take memory to be neutral truth, yet memory is edited constantly — in the victor's language, on the reporter's deadline, in the sponsor's interest. At the 2026 Russia World Cup I commentated the France-Argentina match from Kazan. France 4-3 Argentina was not a score; it was a generational handover in ninety minutes. But our archive keeps only the goals, not the passes; it keeps the winner's name, not the name of the fielder who threw from the boundary. In the empty stadium, I heard absence loud enough to rewrite the game — and the account of that absence is on no ledger. Here lies the blind spot of our collective memory: we do not want verification, because verification might break our favourite story.

So my proposal is simple. Every cricket match, every spell, every disputed decision — let it go onto an open, time-stamped ledger. Who wrote it, when they wrote it, on what source they wrote it — let it all be public. Then when the next generation asks "where is this score written down?", we will not have to fall silent.

I know no ledger can turn rain into "a third team." But a ledger can save our favourite stories from becoming forgeries. The question now is this — do we love memory, or do we love true memory?