Ledger Testimony: Empty Data, Full Imagination and Cricket's Forty-Point Eye

Eleven forty-five at night, a room in Chattogram. On the screen, a rain-hit match; beside me, an open spreadsheet. In the 78th over, the replay of a no-ball — three angles, two different readings, and everything stopped before it ever reached the third umpire. I reached to fill the cells of my ledger and found them empty. Zero. At sixty-eight, this is the most uncomfortable discovery I have made: when information is absent, people fill the space with imagination, and imagination is never testimony. For more than fifty years I have watched matches, kept the book, counted the clips; yet today the first page is blank. For a referee there is no larger crisis — when there is no evidence, restraint is the only profession. So the question is not simple: is cricket's system for preserving decisions truly unbreakable, or does it, too, tear like paper?

In the past decade the language of cricket decisions has changed. Once the umpire raised a hand, the match referee wrote in a book, and that writing was final. Now behind every ball runs a frame-by-frame trial — Hawk-Eye, UltraEdge, Snicko, ball-tracking. There is so much data that the question has become: is the decision being written by the data, or is the decision being hidden inside the data? In 2026, after a disputed penalty in a Chattogram final, three match officials logged the same incident three different ways. That day I understood the problem was not the verdict — the problem was the log. Over eleven weeks I rewrote that assessment sheet into a forty-point checklist: positioning, sightline, whistle delay, advantage signal. After piloting it across 62 matches in 12 districts, formal appeals against referees fell from 31 to 9 within a single season. The lesson is clear: when a decision is verifiable, complaints fall. By the same logic, cricket today needs a ledger in which every entry is timestamped, angle-marked and immutable — as a blockchain ledger cannot let a written entry be edited later for convenience.

I have a simple standard for what a cricket decision log should be. Every entry must carry four things — the clock time, the camera angle, the number of the applicable law, and the verdict. Without those four, what is written is not a decision; it is memory. And memory is the place where two supporters tell two different stories about the same ball, and both stay honest. Let the rule speak — let the rule speak, not the emotion.

In 2026, at fifty-nine, I was hired as the first dedicated rules explainer for the Confederations Cup in Russia. In fifteen days I made forty-seven clips; one of them was the Chile–Cameroon call — the first goal overturned by VAR at a FIFA tournament — which drew 2.1 million views. At the rules desk, forty-seven clips are not noise; they are testimony. But the number is not the real story. The real story is that I imposed a fixed ninety-second format — rule, replay, verdict. From then on my sentences shortened and my paragraphs were held to three lines. I stopped writing match reports and wrote only decision breakdowns.

The following year, at sixty, I watched a record 29 penalties at the Russia World Cup. From home in Chattogram I watched all 64 matches live, logged 214 reviewable incidents in a single spreadsheet, and filed a verdict within ninety seconds of each replay. Russia gave us twenty-nine penalties, and each one left a precedent. That handball against Croatia, against Perišić, in the final — it was a verdict, but bigger than the verdict was a precedent. A precedent means that tomorrow another umpire, on another ground, need not fear even if he does not move his hand.

Now let me say why cricket needs this ledger idea. The decision ecosystem of cricket already has three layers. The on-field umpire, who decides in an instant. The third umpire and DRS, where ball-tracking, umpire's call and the margin operate. The match referee, who watches discipline and conduct. Decisions are made at all three layers, but the logs of the three are not gathered in one place. That is the gap.

Picture a DRS review. The ball hits the pad; ball-tracking says the pitch was inside the stump line, impact in line with the stumps, and the wicket reading says 'umpire's call'. If those three pieces of information dissolve into a single instant's decision, no one will know on what basis anyone ruled. If someone raises that ball five years later, there will be no testimony — only memory. And memory is not the referee's friend; it is the referee's enemy.

Here I propose a clear principle. The value of a decision ledger lies not in the verdict but in preserving the conditions under which the decision was made — from which angle, under what uncertainty, under which law number. By an immutable ledger I am not asking for any hype technology; I am asking that every decision be timestamped, angle-marked and cross-verifiable. That is the lesson of blockchain — once an entry is written, it cannot later be changed for convenience. Cricket lacks that immutability today.

From the 2026 experience I drew one more lesson. I paired every one of the 214 incidents with a ninety-second verdict — not just the verdict, but a clip reference. The time was written: '34th minute, second replay.' I never published a verdict without a clip reference. From then on my writing turned from narration into annotation, and younger writers began copying my timestamp habit. In cricket that habit is missing today — who saw it, on which frame, at what speed, is not written down.

Now to the real crisis that forces me to write this. When I sit down to analyse a decision, a stream of information comes to me. Suppose that stream arrives empty. Zero. Then what is an analyst's professional duty? The easy path — fill the empty cells with imagination, write a verdict as if the information had been there. The hard path — write in the book, 'evidence insufficient.' The second path is honest, yet the second path does not satisfy the reader. Here lies the greatest risk in modern cricket journalism: an empty entry is more honest than a filled guess — because a wrong verdict is correctable, but a fabricated verdict becomes permanent in the ledger.

The forty-point eye does not blink at contact; it counts it. But to count, one needs something that can be counted. Without information, even the forty-point eye is blind. And hiding that blindness is the real enemy of my profession.

And this ledger idea is not confined to on-field decisions. The transfer market has rules too, even when the ink is still wet — release clauses, the wage bill, the agent's paperwork. The question there is the same: is the claim verifiable?

Now the other side, because I want to stand against my own argument. Blockchain or any immutable ledger cannot teach cricket how to umpire. Technology records; people judge. A ledger can say where the ball pitched; but whether the ball 'travelled enough' is a question of law and judgement. Those who think technology will make decisions bloodless forget that technology, too, is code written by human hands.

The public usually wants a villain; the ledger gives a number. On a disputed no-ball the crowd wants a guilty umpire; the ledger gives 'umpire's call' — the decision is valid inside the margin. A number does not satisfy the demand for a villain, so the debate does not stop. Here one must understand: transparency does not mean everyone's satisfaction; transparency means accountability.

The question of data quality matters just as much. Bad input, immutable output — if a ledger is filled with empty information, it is immutably empty. Technology can set a false verdict in stone; it cannot make it true. So before the ledger comes the purity of the input.

And one subtle distinction I always hold — 'not proven' and 'no' are not the same place. If a review finds no Snicko spike, that does not mean the bat did not touch; it means we have no evidence. The law draws a line between the two, and the journalist's duty is not to erase that line but to make it clear. At sixty-eight, I have been wrong before, so I built a checklist that argues back. I have been wrong, so I built a checklist that argues with me.

So what is the way? My proposal is simple, and it is no techno-luxury. Let every cricket decision — on-field, DRS, referee — be deposited in an open, verifiable ledger; with clip reference, angle and law number. Where there is no evidence, let it read 'evidence insufficient' — not a shame, but honesty itself. What blockchain can teach us is not the verdict but accountability: what is written once cannot be erased. Pull the clip, mark the angle, then let the rule speak. And the question remains — cricket, the game that loves rules most, will it learn to keep the account of its own decisions, or in the next controversy will it again trust only memory?

— Root: 40-Point Eye / Referee