The Lesson of a Blank Scorebook: Cricket, Data Trust, and the Blockchain Ledger

A single page in the scorebook lay blank. Where the runs per over, the bowler's over-count, and the time of every catch should have been inked, there was no mark at all. In cricket a blank page is never good news: either rain washed the match away, or someone forgot to keep the count, or someone erased it. Last night a blank page landed in front of me in exactly that way — an analysis document where line after line said only 'no information', 'insufficient', 'not applicable'. The scorebook at the ground and the file on the server are two different things, but both whispered the same truth: where there is no information, there is no analysis. I have kept cricket's books for fifty years. As a boy I opened the batting and kept wicket for Udity Club in the Dhaka league, and from there I learned that the truth of a game lives in the scorebook, not in a television replay. In 2026, at fifty-seven, I spent ninety-four days on the Bengaluru FC team bus and filled eleven notebooks: sixty-eight training sessions, eighteen league matches. In 2026 I lived eighty-seven days inside the Goa bio-bubble and watched too many empty, crowdless evenings. Those notebooks were never a hobby of nostalgia; they are a ledger in which cricket's daily cost is written down, day after day. Cricket survives on its records. Don Bradman's 99.94 Test average is more than a number — it is a promise that every innings will be counted, on the page of the record book. Sachin Tendulkar's hundred international centuries are bound in paper, not in hearsay. In the game's earliest days the scorebook was written by hand, a scorer sitting at the boundary edge, noting every ball. That scorer was cricket's first neutral witness, and not an easy man to buy into silence. Today that same job is split: one part stays at the ground, the other sits on a distant server where nobody watches what gets written. The blank document that reached me last night was the product of a two-stage process. The first stage was supposed to pull facts out of a source article — match, player, team, rule, date, quote. The second stage was supposed to analyse those facts across eight dimensions. But when the first-stage file arrived, it held nothing at all: every field either empty or stamped 'not applicable'. And it was passed downstream without a single question being asked. In cricket, a scorer who did that would be walked off the ground. This episode raises a question bigger than cricket analysis: the question of trust in information. In cricket a claim becomes true only when a scorecard sits behind it. 'The player is out of form' is worth believing only when the numbers from the last ten innings are laid out behind it. Where there are no numbers, a writer who invents something on the spot is not analysing; he is guessing, and reporting built on guesswork collapses fastest. This is where blockchain enters, less through a fan's love of the game than through the safety of information. A blockchain is a kind of digital ledger in which a page, once written, cannot quietly be changed. Each entry is chained to the previous one by a hash; change a single character and the whole chain stops adding up. The old hand-written scorebook could be altered with correction fluid, and nobody would notice. In a blockchain ledger that gap is almost closed. Imagine if the murkiest corners of cricket kept their accounts in such a ledger. Player transfers — how large the fee really was, how much the agent's commission, how much genuine and how much inflated — currently sleep in closed club files. The market for fan tokens and digital collectibles has already arrived in cricket, yet its pricing, ownership and trades remain largely unaudited. Put ticketing on a blockchain and black-market tickets become easy to spot. Put transfer escrow into a smart contract and the money is released only when the player actually joins the new club; nobody can take the cash and vanish. Integrity matters even more. Match-fixing is hard to prove because suspicious betting patterns usually hide behind closed doors, and once time passes the trail fades. If legal wagers and the events on the field were recorded in one ledger with a shared timestamp, anomalies would surface far more easily. Blockchain here is no magic; it is chiefly a secure wall of timestamps. What cricket's anti-corruption units have asked for across the years — evidence that cannot be altered after the fact — is exactly what such a ledger offers. There is another dimension I have seen with my own eyes. Inside the 2026 bio-bubble, a player's mental state was not as easy to count as the number of PCR tests. We quietly held a well-being session with the team doctor, and I never wrote that record down, because protecting the player's name mattered. Blockchain offers a striking use here: pseudonymous entries. The session can be logged without a name, yet nobody can later erase it. Privacy and accountability, held together at once. But here is my objection. Blockchain is no cure for cricket's problem of trust. However immutable the ledger, what goes into it is decided by people, not by code. If someone inserts a false entry, the blockchain makes that falsehood permanent, not true. Computer science has an old saying: garbage in, garbage out. The blank document in my hands last night is the proof. The fault was not below, in the ledger; it was above, in the stage that gathers the facts. So if cricket's administrators do not want to keep accounts at all, the finest blockchain on earth will do nothing. Who sets the India-Pakistan schedule, how ICC revenue is split, who holds up an NOC — technology does not answer these questions; institutional will does. Treating technology as the measure of truth weakens journalism, because we then stop asking questions and merely tally the system's output. In all my years with a notebook beside the boundary, I have learned one thing: a ledger does not hold people accountable; people hold the ledger accountable. Here I carry an old grievance. These days any young player with perhaps fewer than fifty top-flight games can command tens of millions, and the price is dressed up as reasoning when it is really gambling. Before flying to the 2026 Qatar World Cup, I broke the story of a twenty-one-year-old Bengaluru FC midfielder's surprising loan move, having spent eighteen days at the club's Bellary pre-season to earn the agent's trust. That experience taught me that a transfer's real accounting lives not on paper but in people. An auditable ledger would show which price stands on performance and which is merely the froth of hype. That is why I keep the diary. Some ask what use such old notebooks are. My answer: a notebook does not merely pull the past back; it testifies against the future. What the boards promised, which decision pushed which player aside, whose spirit broke in which bio-bubble — these small notes accumulate into a moral ledger that no board circular can hold. The idea of blockchain says the same thing, only with code instead of paper and hashes instead of ink. I kept the diary; the diary kept me. It taught me patience and the value of waiting over shouting. In Russia I went and sat where the ordinary fan sits, and I understood that what VAR cannot see does not live in a camera angle; it lives in the gallery's wait and in the sound of people's voices. A blank ledger and a blank scorebook teach the same lesson: what is not written leaves no witness in history, and without a witness there is no justice either. My eye will stay on two things ahead. One: when cricket's big boards will agree to put transfer and ticketing accounts into an auditable ledger. Two: when our analysis pipelines will learn that, given empty input, saying honestly 'I do not know' is more professional than manufacturing an analysis. A blank book is not defeat; a blank book is a chance to begin again with correct information. So the question is large: as cricket sprints toward technology, is it learning to keep its own accounts any faster?