Who Writes the First Block: Cricket's Immutable Ledger, DRS and the Ledger of Rajshahi Tea Stalls

On Wednesday evening I stood near the edge of a small ground beside the Rajshahi District Stadium, watching an age-group match finish. Under a tin shed the scorer was filling a torn khata, and in the twelfth over an argument about a run-out spilled right up to the boundary rope. The scorer struck a line through one entry with his pen, then wrote a different name two lines below. Babul Sheikh, a groundskeeper standing behind me, turned and said: “Sir, a khata you can strike through and rewrite is not a khata. It is a claim.”

That sentence travelled with me for three days. Three days later I opened a slide deck about cricket's data future: on-chain records, immutable ledgers, tamper-proof history. The question missing from the deck was Babul's question — who writes the khata, and who is allowed to read it?

I work out of Rajshahi. In 2026, at forty-eight, when Dhaka sports desks were moving from print to digital, I chose the north over the capital and rebuilt my beat around a 340-member WhatsApp network — club coaches, groundstaff, bus drivers, two scorers. That October, when Sheikh Russel KC beat Saif SC 2-0 at Rajshahi District Stadium, I filed the dressing-room reaction forty minutes before any national outlet. Years of walking that beat have taught me one habit: when a new technology makes a promise, I take it to the ground first, then to the tea stalls. What does not survive the tea stalls does not survive the ground either.

Cricket's decision technology is older than people remember. In July 2026, the Decision Review System made its Test debut at the SSC in Colombo during the Sri Lanka–India series. Ball-tracking draws the pitch, impact and stump lines; UltraEdge catches the sound off the bat; a third umpire sits before a screen and gives the verdict. Note what actually happens: the machine does not give a verdict. The machine gives numbers. A human gives the verdict. And under the 'umpire's call' provision, when the tracking estimate is uncertain, the on-field decision stands. Cricket already admitted, years ago, that the machine can be wrong — and handed that uncertainty back to a person.

In 2026 I watched the Russia World Cup from a Rajshahi editing room, one replay behind the world. Across sixty-four matches I kept a spreadsheet open, logging VAR's overturned decisions. The spreadsheet held twenty-two overturned calls; the tea stalls held sixty arguments. I carried the numbers to the tea stalls and asked who they trusted. What I found: most trusted the machine — not the men operating it. That is why, since then, every tournament dispatch of mine carries a one-page explainer translating the technical call into the language fans actually use. Editors resisted at first. Readers shared those sidebars four times more than the match reports.

Now a further layer is being proposed on top of the machine. Several big European football clubs have experimented with fan tokens and memorabilia NFTs; in cricket the talk is about player registration, contract records and audit trails for decisions. The pitch sounds simple: what is written once to the ledger cannot be erased. The exact inverse of Babul's khata.

But a ledger stores three different things, and the three need different answers.

At the decision layer, the question is not fraud but judgement. No board or the ICC has ever been accused of quietly reversing an umpire's call; the accusations are about inconsistent standards and faulty interpretation. An on-chain decision does not fix interpretation. Which frame counts as impact, where the umpire's-call margin sits, how tightly the stump line is matched — all of that stays outside the ledger, in human hands. And even an immutably recorded decision does not end the argument, because the argument was never about the record being altered. It was about whether the call was fair.

At the contract layer, the blockchain case is strongest. Franchise transfer windows, player registration, agent commissions, age verification — these run on paper and PDFs that get passed hand to hand, and every copy is a chance to edit. An on-chain registry could close that door, at least in theory. My beat suggests a caveat. A district coach once told me the same boy's age had been changed twice in official records. On a ledger that stops. But whoever first typed the birth date is the same person who later changed it. Power here is not the writing; it is deciding what gets written.

And at this layer the real cost is not money, it is noise. The rumours and estimated fees agents generate distort the market more than any fee itself. One invented valuation moves three club budgets, and that movement is eventually paid for out of groundstaff wages and bus fares. A ledger does not silence rumours. Putting the source of a rumour on a ledger at least leaves a trail — a small gain for a reporter, but a real one.

The grassroots layer is where my worry sits. Every delivery Shakib Al Hasan faces is archived; so is every review Mushfiqur Rahim has taken. But there is not a single ball of data for a left-arm spinner in the Rajshahi First Division, because nobody televised that match and nobody uploaded the scorecard. A ledger only records what someone chooses to record. A match nobody logs has no block.

That is the trap. Blockchain does not dissolve inequality; it stamps it permanently. Matches whose data already exists become immutable; matches whose data does not exist stay absent forever — and now the absence itself looks like proof, because the ledger has nothing on them. Years of watching matches from the boundary have taught me that lack of evidence is not the same as absence. In the ledger era, conflating the two will fall hardest on district cricket in the north.

Then there is the practical reality. District grounds still run on hand-turned scoreboards. Power cuts at night. One person has data on his phone, the next does not. The two scorers in my WhatsApp group still send photographs of the scoreboard — readable, but not verifiable. Running a chain needs devices, training, connectivity and a rule for who validates each entry. Who pays first? Usually the party with the most to gain — the people already selling match data. Cricket already runs centralised anti-corruption work, with an anti-corruption unit. That is not a broken thing. But if the central store becomes more central still, a reporter's basic instrument — the ability to verify independently — shrinks further.

The promotional claim of blockchain rests on one word: trustless. In cricket that word is a lie. My 2026 spreadsheet argued with me about this. Readers may trust the machine; they do not trust the man operating it. A chain sits in exactly the same place. Whoever holds the keys, runs the node and ships the software update is, in the end, the one writing the khata. There is no trustless system; you only move where the trust sits. You do not move the accountability.

There is a second, blunter problem. Babul can strike through an entry — but he can also write again. A permanent ledger takes that away. Suppose a teenage cricketer's date of birth was entered wrongly; on a ledger it is wrong forever. Suppose a district player's name was struck off after an unproven allegation; he will spend his life trying to prove it, and a ledger that never carried his name will never concede anything. Cricket's fairness still relies partly on an open window — someone looks back, someone hears the appeal.

An immutable ledger and a just ledger are not the same document. Cricket does not need immutability; it needs immutability with an appeal window bolted on. Otherwise the technology protects the truth and locks up the people.

What to watch this season is not a blockchain pilot announcement. It is whether a Rajshahi First Division scorecard appears in written form within twenty-four hours of the match, and whether a club coach can read it himself. If the writing belongs to everyone but the door to reading stays shut, that is not a khata either. That is a claim again. The freedom Babul described — to strike through and write again — will probably disappear. The question is what we hand him in its place.