Who Writes Cricket's Ledger: NOCs, DRS Logs and the Blockchain Arithmetic

The habit dates to 2026. At the end of every round of the Dhaka Premier League I write down two times — the last ball, and the moment the match referee's report was filed. In the 2026–18 season I filed copy on all 22 of Abahani Limited Dhaka's league matches within 90 minutes of the final whistle, shorthand notebook in one hand, laptop in the other, in a press box where I was the only woman. Abahani won the title; my copy ran first in 19 of 22 rounds. At the close of the season one gap became obvious. There was no public, timestamped version anywhere of that season's referee reports, points deductions or player registration approvals. What existed sat in somebody's private diary — mine, or the club secretary's desk drawer.

I have been in this trade for more than four decades. What I have learned is that cricket's hottest arguments are not about information. They are about the absence of it. Who approved what, and when? On what date was the letter issued? At which deadline did somebody intervene? Those answers usually live in a notebook, not in a system. What happens when there is no system was settled in 2026.

The Bangladesh Premier League was suspended in March 2026 and never finished. By mid-May I understood there would be no champion, no complete points table, no final. Administratively it is called an unfinished season — it exists on paper and nowhere in the record. For 118 days I worked the phone with 23 players and staff, asking each of them the same four questions so the answers could be compared. The result was a 9,000-word oral history of a season with no winner. Two players lost contracts midway; I printed the exact dates the club's letters were issued, because the club had not released them.

Stop there and ask: who held the most complete document of that season? A league? A board? Or a journalist making calls for 118 consecutive nights? The answer says something uncomfortable about cricket's institutional memory.

Cricket's ledger is spread across four layers, most of them off the field. At ground level sits the scorecard, the DRS log and the match referee's report. At player level sit registration, age verification, central contracts and the No Objection Certificate required to play a foreign league. At administrative level sit points deductions, appeals, hearings and the timestamp on a ruling. At money level sit match fees, prize money and sponsorship instalments, which are frequently released after the deadline they were promised for.

All four layers are ledgers. And ledgers bring up one technology built for precisely this purpose. A blockchain makes a single promise: once an entry is added it cannot be deleted, and anyone can check who wrote it and when. Ethereum moved to proof of stake on 15 September 2026, dropping network energy use close to nothing, which is part of why the subject has returned to cricket and football boardrooms. The International Cricket Council launched a digital cricket collectibles platform with FanCraze in 2026; Socios and Chiliz fan tokens are older and far bigger in football. Shirts, tickets, tokens — all of it now goes on chain.

But those are products, not ledgers. The question cricket administration actually faces is documentary, not commercial.

The clearest example is the NOC. A Bangladesh player wanting a foreign franchise league needs board approval, and there is a deadline attached. A player like Shakib Al Hasan plays several leagues, and each season two or three of those calendars collide. Who approved what, on which date, against which international fixture — that decision usually surfaces as a two-line release, if it surfaces at all. When approval was refused, what was the reason? Was there an appeal? What was the appeal date? Usually nowhere. The deadline is not a wall; it is a pulse I reset every season — and a pulse needs a record nobody can edit.

Inside those 118 days of 2026, two players lost contracts. I printed the dates of both notices because nobody else did. That is a reporter's duty, but it should never have been the storage architecture. Put those notices on a ledger where no entry can be quietly removed, no letter can go missing, and no club can plead that it forgot an appeal deadline. In an employment dispute this is not merely technical, it is about power: whoever holds the information holds the bargaining.

Match-day logs work the same way. Kazan, 30 June 2026, France 4-3 Argentina, a World Cup round of 16. Four accreditation applications had been refused since 2026 before that one came through. In the tribune colleagues argued about VAR decisions; I did not, because I had logged all 29 penalties of the tournament by hand and checked each against the Laws of the Game. The argument stopped, because my notebook carried timestamps. I filed 41 pieces in 32 days, none of them speculative. That notebook taught me that justice arrives with a timestamp. Cricket's DRS log and match referee's report are the same kind of ledger, currently held in closed systems and then buried in an archive at season's end.

So where does the technology genuinely pay? Ticketing first. At Mirpur, black-market tickets, forgeries and gate chaos are annual events; if every ticket exists as a unique, transferable on-chain asset, one ticket cannot be sold twice. Then payments: smart contracts for match fees, prize money and sponsor instalments, where a missed date triggers release automatically and the delay itself becomes the record. And most importantly, registration and ruling logs, where the inability to edit is the whole point.

Bangladesh's reality deserves saying plainly. Bangladesh Bank has warned repeatedly that virtual assets are not legal tender here, and the legal position of ordinary crypto trading is unclear. But there is a distinction that gets lost: blockchain does not mean public cryptocurrency. A board or league can run a permissioned ledger with nodes held by the board, the players' association, selected media and an independent auditor. No token sale required — only a book whose every entry is time-stamped and immutable, and which a rival newsroom can verify.

Here is the insight the blockchain conversation usually gets backwards: in cricket the value is not more transparency but an unalterable memory — because cricket's central problem is not a shortage of transparency, it is a shortage of institutional memory.

The unwelcome truth follows. Immutability only works if there is more than one author and the validators are independent. If the same three board officials write the block, if the same people who run the paper files run the nodes, then only the technology changes, not the decision. Worse, the error becomes permanent. On paper a mistake can be struck out; on chain it becomes history.

A ledger records rulings, it does not produce justice. My Kazan notebook settled arguments among colleagues and never once changed a result. Paper does not change results; paper only proves who announced what, and when. Transparency only helps an organisation that is willing to carry the consequences of its decisions. Technology cannot manufacture that willingness.

The largest gap is silence, which no chain can hold. Silence is not empty; it is 118 days of unmoving match tape. A blockchain can timestamp a ruling. It cannot timestamp a match that was never scheduled. Cancelled tours, empty calendar slots, cancellations never announced — these are evidence of absence, and absence does not go on a ledger. No smart contract has yet been written for a season that never ended.

So the signals I will watch for next are not on the stage but in the file. When a domestic league next publishes a full season of registration, NOC and referee records with timestamps, my first question will be who writes the block, who validates it, and how long an old entry takes to retrieve. My second: where will the file that has not been written, the one nobody will sign, be kept?

The deadline is not a wall; it is a pulse I reset every season. The question now is who counts the pulse — and who keeps the record.