What the Scorecard Won't Say: Cricket's Chain of Record, the Gaps in Memory, and the Lesson of the Blockchain

In the Mirpur press box my seat sits flush against the scorers' cabin, number seven. If I stretch my right hand I can touch the corner of their ledger. For seventeen years that short distance has taught me one thing: a single cricket ball is first written by a human hand, then it travels to the broadcast graphics, then it enters the official record. One ball, written three times in three places, and all three times slightly different.

Last season, in a domestic match in Dhaka, exactly that happened. The match ended in the evening, and the printed scorecard reached me forty minutes later. It said: one wide in the fifteenth over. But the tally in my own notepad said the opposite — it was not a wide, it was a leg bye. I asked the scorer. He turned his ledger back and forth, then said the TV graphics had shown a wide, so he wrote a wide. I told him he does not make the graphics. He laughed. That laugh is the centre of this piece.

One wide or one leg bye does not change the result of a match. But it is the first link of a chain. The truth of cricket does not live in any single document; it lives in the relationship between the documents. The technology called blockchain takes precisely that relationship seriously — every record is bound to the one before it, and if anyone alters something in the middle, the whole chain comes apart. Cricket's information world has been running a crude version of that idea for years. Nobody just gave it a name.

In cricket the chain of information begins at the edge of the field. When the ball touches the boundary, the first person to see it is the man sitting beside square leg, then the side-on scorer, then the statistician in the press box, then the broadcast, and finally the match referee's report. At every layer the information changes hands, and at every handover a little is lost or added. Nobody knows which layer changed what, because nobody ever sees the whole chain at once.

It was in 2026, hunting for that gap, that I stopped filing the nine-hundred-word match report and started sending hundred-and-fifty-word dispatches from the team bus. Because sitting on the bus I understood that there is a gap between what happens on the field and what reaches the ledger — and that gap is the real story. There is no whistle after the last ball, but the real match report begins long before it.

In June 2026 I went to Russia to hunt for that gap. I watched twenty-two matches in eleven cities and wrote almost nothing about the football. I sat in the tribune with a stopwatch and logged all twenty-nine penalties of the tournament, with the story behind each review. In Kazan, in France–Argentina, the longest check ran past two minutes. My four-thousand-word piece 'The Twenty-Nine Reviews' was almost spiked — because it contained no goals. Twenty-two matches, twenty-nine penalties, and a tournament that refused to be summarised.

Since that day I attach a sixty-word mechanics box to every match report — the law, the technology and the protocol that the crowd is actually arguing about. The result of a match is really the sum of a set of administrative decisions that nobody watches; the crowd only sees the final number. My outlet now prints it as a standard footer under my byline, and readers argue with the box more than with the report.

The most visible layer of this chain in cricket is DRS. Ball-tracking, UltraEdge, the third umpire — each a separate technology, a separate company, a separate version. The software that determines the trajectory of the ball in an LBW review carries a fixed margin of error in its prediction. But that never reaches the scorecard. The scorecard writes only 'out'. A two-word decision, with a pile of assumptions behind it.

Umpires know this well. That is why some of them want to preserve the idea of umpire's call — that the benefit of the doubt should stay with the on-field umpire. The reason is not technological but philosophical. Technology answers a narrow question, but cricket asks a large one every time. Whether the ball would have hit the stumps is a narrow question. Whether the batter moved his foot first, or whether the ball was swinging, is a large question, and it has no sensor.

In April 2026 the difference between the narrow and the broad question hit me. That month the league was cancelled, the squad scattered to their villages, and I could not travel. So I sat at home and rewatched sixty-three matches from 2026 to 2026, tagging 2,140 set-pieces into a spreadsheet. By June it emerged that seventy-one percent of the goals the team conceded in that window came from the second phase after a cleared corner — a pattern nobody at the club had ever logged. I rewatched sixty-three matches until the spreadsheet started arguing with my memory.

The place where the spreadsheet argued with my memory was the real discovery. I remembered a few dramatic goals. But the tally said the team was dying a slow, repetitive death — nobody tracked who was picking up the second ball after a corner was cleared. Drama stays in memory; repetition slides out of it. And the same thing happens in cricket.

Where is the second phase in cricket? In the ball after a dropped catch. In the over after losing a review. In the three balls after a new batter arrives at the crease. The moments that never make a highlights package are exactly where a match is really decided. The broadcast cuts them, because they are not 'moments'. But they are the pattern.

Chasing that pattern, I arrived at a basic problem of the scorecard. Whether a delivery is a wide, a bye or a leg bye depends on the eye of a man sitting seventy yards away, with a ledger in front of him and a doubtful TV monitor beside him. Technology does not make the decision; it only gives a second opinion — and often a misleading one.

The reason is simple. Television graphics are not an independent source. They are a copy of the scorer's ledger, only faster. If the ledger is wrong, the graphics show it wrong, and if the graphics show it wrong, the scorer corrects his own ledger to match the graphics. In this way one error sits down as truth in two places. When the copy of a copy becomes the original, there is no longer any path to correction.

This is where a core lesson of blockchain technology lies. What is written in one block leaves a mathematical fingerprint on the next. If someone tries to alter an old block, all the fingerprints after it fail to match, and the whole network can detect it. It does not verify truth — it can only detect change. Cricket's chain lacks exactly that power of detection. The scorer's ledger, the broadcast graphics and the referee's report have no mathematical binding between them. Three separate islands, no bridges.

That has a real cost. When a match's statistics reach the cricket data vendors, nobody asks who is correct. Whichever company supplies the fastest data, its numbers become official. Speed overruns truth. The information that arrives first becomes history — whether it is right or wrong.

I see this problem every season, and every season I think the answer is not more data but the relationships between data. Who changed which number and when, who approved it, on what evidence — if those answers were written in a chain, errors could be corrected. This is the meeting point of the blockchain idea and cricket journalism.

But this is where my deepest doubt rises. Verification and truth are not the same thing. A blockchain can prove that a record was not altered. It cannot prove that the record was correct. Cricket's biggest problems — the umpire's interpretation, the behaviour of the pitch, the state of mind of a batter — never enter any ledger. They stay outside verification, because they are not a number, they are an interpretation.

The danger is exactly here. If we write every cricket decision into an immutable chain, we will make the error permanent too. Where a record never changes, there is also no room for correction. Much of sport's beauty depends on the capacity to forget — anger fades, memory softens, a new match begins fresh. Immutability takes away that capacity.

On 12 June 2026 that tension caught me from another direction. One in the morning, at a desk in Barishal, the Denmark–Finland feed. In the forty-third minute Christian Eriksen fell to the ground. My desk wanted eight hundred words of emotion. I sent three thousand words on the response instead — the CPR on the pitch, the thirteen minutes before he was carried off, and UEFA's pre-tournament cardiac screening rules.

After that night I began keeping a protocol file — medical, safety and operations documents, read before the team sheet. It changed what I ask press officers. And it is now my strongest habit — I break more administrative stories and fewer tactical ones, which still leaves me dissatisfied with myself.

The protocol file taught me that the real unit of verification is the rule, not the event. An event happens once. But the rule is written in advance, amended slowly, and is the same for everyone. Blockchain's chain is really a chain of rules — what counts as a valid transaction is decided by code, and changing that code requires everyone's consent. Cricket's rules are the same. A match's result is born inside the rules, and the rules outlast the event.

Transfer-window rumours suffer from exactly the same problem. Every transfer window is a chess clock with no board and too many hands. A name gets linked, spreads, and within two days it sits as truth in many minds — even though there is no document behind it. Its credibility depends on who released the information first, while its truth is never checked. Here too what is needed is not data but a chain of relationships.

The real story usually sits in the structure of the contract, the terms of the release clause and the weight of the wage bill — not in the noise of the rumour. A club that has already drawn up its wage structure sees a name linked or unlinked as a small movement in the accounts. A club that has not sees every rumour as a crisis. In cricket and football alike, this rule holds.

My real interest is inside the game, not in power. I want to know where the true story of a match lives. My suspicion is that it does not live in any scorecard, but in the gap between three documents — the scorer's ledger, the broadcast graphics and the spectator's eye, in the disagreement between these three. The blockchain can shrink that gap. But if the gap is erased entirely, the game will lose something too.

Because cricket is an uncertain game. Its beauty is in its errors, its guesses, its interpretations. Technology can reduce that uncertainty, but driving it to zero would turn the game into a machine's accounting. So my demand is limited — let the chain be strong, but let it be probability, not truth.

There is a practical form of this that can begin without any software. Keep a box of uncertainty beside every decision — a number, an asterisk, a short note. If the result of an LBW review sits within five percent doubt, why should the scorecard hide it? Let the history of corrections be preserved — who changed what, and when. Let memory-based accounts and measurement-based accounts be separately marked. The rest is the work of time.

The peripheral witnesses are the most neglected in this chain. The spectator at the boundary edge, the security guard at the gate, the team bus driver — they see the starting state of a match first. Whose knee is swollen, who arrived late, whose face is heavy — this information never gets recorded, yet it is the biggest predictor of the next day's performance. I spend the first hour of every training session standing at the kit-room door, because the real scorecard starts being written there.

My whole profession survives on the gaps in this chain. The ball on the field, the ball in the ledger and the ball on the screen — if these three ever matched exactly, cricket journalism would not need to exist. We live on the discrepancy. The only question is whether we use that discrepancy to correct errors or to understand something new.

Cricket boards, of course, want to keep this chain in their own hands, and that is understandable. If every decision becomes verifiable, power shifts from the centre to the edge — to the scorer, the statistician, even the spectator. The political lesson of the blockchain is the same — verification decentralises power. For those who control information, this is not comfortable.

I return to my bus routine. Even today, before every match, I take out a blank page on the bus, write the date and place at the top, and leave the bottom empty for witnesses. The ledger is ready before the game begins. Because there is no whistle after the last ball, but the real match report begins long before it — on exactly that blank page, where nothing has been written yet.

Next season I have a plan for cricket's chain of information. I want to make a simple little grid for scorers — a box of uncertainty beside every decision. No software needed, only a pen and a habit. If it works for one season, then perhaps that will be the first honest block of cricket's blockchain — small, handwritten, and admitting doubt.

One last thing must be kept in mind. A chain of verification brings us closer to truth, but it can never take truth's place. If cricket's record one day becomes perfect, immutable and verifiable, a question will still remain — the boy who played this match, what was really going on inside him, who will write that down? Documents cannot answer. Only a journalist can answer, a ledger in hand, sitting in a bus seat, long before the game begins."