The Scorecard Ledger: Who Verifies Cricket's Truth

Even after the rain stops, a number on the scoreboard can still change. On 14 July 2026, at Lord's, the World Cup final finished with both sides level after the Super Over — Ben Stokes's side and Kane Williamson's side — yet the trophy went to one team, by a boundary-count rule. I watched that match from a small café in Delhi, and a man at the next table kept saying, "That isn't truth, that's a rule." His words still circle in my head. I have spent my whole career chasing the scorecard, but that evening I felt for the first time: if the scorecard is the truth, then who writes it? Who keeps it unchangeable? And if someone does change it, how would we ever know? I filed my first World Cup story from the stands, with rain on the page. In October 2026 I watched India vs USA at the FIFA U-17 World Cup in Delhi's Jawaharlal Nehru Stadium, before 46,598 fans; India lost 0-3. Soon after, Jeakson Singh scored India's first FIFA-tournament goal against Colombia in a 1-2 defeat. I dropped the scoreline and wrote the roar of the stands instead. The first file I sent was less report than prayer. Back then I did not understand where the real record of a game actually lives — not on paper, but on a server, in a database, and in the memory of thousands. Cricket's history is really one vast account book — a ledger. Every ball, every run, every wicket is an entry. Who keeps this ledger? First the scorer, then the umpire, then the broadcaster, and finally the statistics body. At every layer there is a person, an institution, a decision. And this is exactly where the idea of the blockchain becomes interesting to me. A blockchain wants a ledger that everyone can verify together, without a central authority, and that no one can secretly rewrite once written. Cricket's ledger is almost the opposite — deeply centralised, deeply human, and therefore deeply fragile. In the DRS era we easily assume technology has made the truth final. It is the reverse. DRS does not create truth; it moves truth off the pitch into the review room, into the grey zones of the rulebook. Ball-tracking shows where the ball pitched, but the rule that 'the on-field umpire's call stands' — who wrote that? A human. Where two centimetres separate out from not-out, technology does not ask the question; the rule does. And rules change in human hands, with time. Just as VAR did not reduce football's controversies but only shifted them from the pitch to the screen and the grey zones, DRS has done the same. Rostov-on-Don taught me that fourteen seconds can erase a printing press. In July 2026, Belgium trailed Japan 2-0 and won 3-2, through a fourteen-second counter from Courtois to De Bruyne to Lukaku's dummy. At 94:00 my print editor called — the edition was closing. I filed 800 words digitally in 22 minutes. That night my print-first habit died. In cricket it is the same: a single ball, a no-ball, a dropped catch, a DRS frame — fourteen seconds overturn an innings' story, and a new line enters the ledger. But if the ledger were truly immutable, why so many revisions in history? At The Oval in 2026, Pakistan became the first team to forfeit a Test — ball-tampering allegations, an umpiring decision, a team confined to its dressing room. That result, that record, remains contested even now. The boundary-count rule from the 2026 final was later changed — meaning the very rule that decided a World Cup was itself retired afterwards. The record stayed; the rule moved. Which is the real truth — the moment, or its interpretation? And rain? Rain is cricket's most honest writer, because it takes no side. The Duckworth-Lewis-Stern method is a mathematical ledger, setting a target from wickets and balls remaining. But even this mathematical truth is human-made, and those humans can err. We have seen DLS controversies again and again — sometimes the villain was a number, sometimes a formula. In cricket's ledger, then, every entry has a decision behind it, and every decision has a person behind it. In my experience, cricket's data comes in two kinds. One is formal — official scorecards of the ICC and the boards. The other is informal — media and fan-run databases, where statistics accrete slowly. Between these two there is always a gap. Somewhere an old match's ball-count is wrong, somewhere a run tally is disputed, somewhere a player's debut date reads differently in two places. These gaps are the honest part, because they show that the ledger is no divine truth — it is a human process. The central promise of a blockchain is transparency — every entry public, every change visible, every change signed. In cricket's ledger, this absence of transparency is the biggest problem. We see the scorecard, but not the history of its corrections. Who changed it, why, with whose approval — all of that disappears. So to the fan the record is sacred, while to the institution it is editable. From this collision of two truths come conspiracy, anger, and finally a question: if we cannot verify the record, how can we believe it? As a journalist I keep one personal rule: no emotion without a number, no claim without a source. In my notebook I keep two separate sections — one for tactics, one for the sounds of the crowd. But before a piece goes to press I put a footer beneath it: who said it, when they said it, how much was verified. That footer is the bridge between cricket's ledger and the blockchain. A blockchain puts a hash behind every block; journalism should put a source behind every claim. Both say the same thing — without evidence, truth is incomplete. Our collective memory believes the record is truth carved in stone. In reality the record is a manuscript open to editing. Until someone looks a second time, it stays immutable. Statistics bodies routinely revise old scorecards — runs fall and rise, ball-counts are corrected, a match's status changes. Does anyone notice? Very few. Because we read the scorecard, not its foundation. This is the blind spot of collective memory: we take history as fixed, when history is being edited every day. Here lies both the lesson and the limit of the blockchain. A blockchain says that if information sits in a centralised ledger, anyone can rewrite its history. Cricket is exactly that — centralised, hence editable. But cricket cannot be fully decentralised, because cricket is not only numbers; cricket is a social contract. The DRS frame, the umpire's finger, the scorer's pen — all rest on human trust. Technology does not secure the truth; it merely moves the burden of truth from one place to another. In recent years cricket's commercial world has reached toward the blockchain too — fan tokens, digital collectibles, commemorative NFTs. The idea is elegant: a fan can own a moment, a ticket, a memory. But can a memory ever be anyone's property? A day washed out by rain, a roar in the stands, fourteen seconds of silence — are these things to be bought and sold? The blockchain keeps the moment immutable, but cannot hold the moment's meaning. The number is fixed; the meaning flows. Working with data, I have learned one hard lesson: empty data and wrong data are the same thing. If an analysis contains no information, the most honest answer is 'I don't know', never a guess. Cricket analysis now has a real flow of information, but too little verification. Once a wrong number spreads, correcting it is almost impossible — just as one wrong DRS frame can change a match's fate. The real lesson of the blockchain is this: verify information before adding it, and keep proof of the verification. We are now in a tournament season. Every week brings new matches, new records, new controversies. In such a time numbers and emotion flow together — and that is precisely when error is most likely. When fans are swept up by flag and story, who will remind them where a score, a debut, a record actually came from? I believe this season we need not only more information — we need more verification. Because one wrong record can poison a generation's memory. An empty stadium is not empty; it is full of everyone who left. In the same way, a scorecard is not just numbers; it holds every decision, every correction, every deleted line. In the ghost derby, silence had a scoreline, and memory kept the crowd. Cricket's ledger is the same — not frozen, but alive. I filed my first World Cup story from the stands, with rain on the page, and that is when I understood: truth is not writing carved on a wall; truth is a running account book that must be verified anew every day. The question remains: when the next disputed final arrives, will we look only at the scorecard, or at the decisions behind it? Because for a game that never truly ends, the record is never truly final. And if the record is never final, then every fan should remember not only the result — but how the result was written.