The Blockchain Ledger and the Referee's Pen: Who Really Records Cricket's Decisions?

During the 2026 T20 World Cup, the ICC partnered with an NFT platform to release digital collectibles of the tournament's memorable moments. A six, a diving catch, a last-over yorker — each one landed on a chain where nobody could later reach in and edit the data. In the same weeks, the match referee's over-rate report, the notes from a Code of Conduct hearing, the third umpire's review log — much of that went unpublished. Cricket made its most entertaining material immutable and left its most consequential paperwork sitting on a password-protected drive.

I have kept a review ledger since 2026. It began with football's VAR — twenty-seven trial incidents mapped to Laws 11 and 12 — and later shifted toward cricket: DRS reviews, match referee rulings, the appendices of the ICC playing conditions, Anti-Corruption Unit reports. Eight years of that habit has produced one recurring observation. Cricket's administrators are not afraid to deploy new technology. They are afraid to publish what that technology records.

Cricket's decision architecture is a sandwich of paper and code. On the field, the umpire decides under MCC Laws — LBW means Law 36, and that is written down. Player review is a different animal. DRS is not law at all; it is an appendix to the ICC playing conditions, and its finer thresholds shift from series to series. Above that sits the tracking data — Hawk-Eye, UltraEdge, Real-Time Snicko — privately owned and locked inside the live broadcast. Then come the match referee's report, the Code of Conduct hearing, the fine, the suspension. And above all of it, usually out of public view, sits the ICC's Anti-Corruption Unit: a running ledger of odd movements in betting markets, agent contacts and suspicious results.

There is an odd gap between those layers. The ICC does not use a chain for its most immutable record; it uses a hard disk in a broadcast truck. Its weakest record — who was sanctioned, why, and for how many matches — lives in scattered PDFs and press releases. Working through the 2026 Qatar tournament, that gap was plainly visible. My tournament log had taught me that a tournament is really a legal document, written over by over, where scheduling, reserve days and DLS are the actual plot.

The question now is simple. If cricket wants its decisions written into an immutable ledger, what exactly goes into that ledger?

Take a single LBW review. The third umpire reads the ball-tracking prediction: the ball is hitting the stumps. The on-field decision can still stand, because the prediction falls inside the umpire's call zone — part of the ball inside the stump line, part of it outside. The ICC keeps that margin deliberately, because ball-tracking carries an error band of roughly two to two and a half centimetres. Cricket's most machine-dependent moment ends in a zone of conscious human discretion. Anyone who wants to move the whole DRS process onto a chain would have to write that margin into the record alongside the tracking frames. The margin is not a natural constant; it is a policy choice, and committees have changed it. In 2026 the ICC extended the LBW wicket zone up to the top of the stumps — a change of one line that reshapes probability across an entire tournament. The ledger can be immutable. The rule inside it cannot.

The integrity layer is where the blockchain pitch sounds most seductive. After the 2026 spot-fixing scandal — Salman Butt, Mohammad Asif and Mohammad Amir, banned by an ICC tribunal and jailed in London in 2026 — the anti-corruption apparatus came to rest largely on trust and intelligence work. The theory is that agent-player communications and tick-by-tick betting data on a public chain would make fixing easier to prove. On paper the argument is clean. In practice the difficulty sits elsewhere. In 2026 Sanath Jayasuriya received a two-year sanction for failing to cooperate with an investigation — not for fixing, but for not engaging with the process. An immutable record does not produce cooperation; it produces evidence, and evidence only matters where somebody holds jurisdiction to seize it. Forensic data scattered across a cross-border chain takes a paper trail to reach a courtroom, and no smart contract encodes that.

Franchise leagues now want to pay match fees and win bonuses through smart contracts, and they like to market fan tokens and NFT drops as engagement. This is where an old suspicion returns. Distance covered and high-intensity sprints get packaged as effort metrics, yet pointless running also produces pretty numbers; on-chain counts behave the same way. A league can mint a hundred thousand tokens and call it a fanbase, while an airdrop and a handful of wash-trading wallets do most of the inflating. An immutable record of a meaningless transaction is still a meaningless transaction. However smart the payment code is, the disciplinary decision stays with a person — doping suspensions, morality clauses and NOC disputes do not resolve through an if-else. The code only moves the discretion one layer up.

The diaspora split is worth watching here too. In Bangladesh's domestic cricket economy, technology arrives through budgets and administrative approval; the board is often a politically steered institution, and ownership of the record stays there. In English county cricket, Hawk-Eye sits at nearly every ground, yet the published outcome of a Code of Conduct matter is rarely more than a line. The technology gap between the two is real. The decisive gap is not technology; it is who owns the record. A board willing to publish its paper can be accountable without a chain. A board unwilling to publish will publish nothing on a chain either.

Blockchain advocates offer a tidy claim: immutability means transparency. In cricket that argument needs reading backwards. Cricket's transparency crisis is not a storage crisis; it is a publication crisis. The records already exist — the referee writes the report, the tribunal writes the finding, the review log is saved. The problem is that they are centralised and closed. Putting a secret on a chain does not make it transparent; it makes it a permanent secret with a hash that everyone can see and nobody can read. Meanwhile a fan's token trade is public forever, and a board's sanction is a PDF. That asymmetry is the real politics.

The larger risk is the freezing of a flawed process. Suppose an over-rate penalty is not applied with equal severity across boards, or a hearing proceeds without counsel beside the player. Record that process exactly on an immutable ledger and the flaw does not disappear — it becomes permanent and auditable. Auditability then stops being accountability and becomes documentation. The question worth asking is who gets to write to the ledger: players, umpires, journalists, or one administrator at the board? A ledger is only as democratic as the people permitted to write to it.

The next real reform will not be a token or an NFT. It will be a publication mandate — a public archive of match referee reports, Code of Conduct outcomes and DRS review logs, with clause numbers and timestamps attached. Until then the chain will record the six, not the decision. The next time a board announces an investment in technology, one question is enough: may I see your ledger? If the answer arrives as a PDF, you already know who the ledger is written for.