Ball-by-Ball Ledger: Why Cricket's Disciplinary Record Belongs on a Blockchain

Last season in Dubai I got hold of a match referee's report from a DP World ILT20 fixture. One page, three sentences: the fielding side failed to complete its overs in the scheduled time, therefore a fine. Which over ran late by how many seconds, which injury stoppage or DRS delay was excused, and who made that excusal — none of it appeared on the page.

I spent fifteen years covering Asian football for one reason: there is at least a replay. On 15 July 2026, from the Luzhniki press box, I pulled the frames of the 38th-minute handball review in the France-Croatia final, measuring how far Ivan Perisic's arm travelled from his body. Amid the noise, my notebook held only a geometry problem.

Cricket's problem sits one step earlier. The replays exist, but the arithmetic beneath the verdict has no permanent, publicly checkable record. I pulled the final once. Now I want to pull the ledger.

Cricket's authority runs through four stages: the two on-field umpires decide; the TV umpire reviews ball-tracking and audio; the match referee weighs over rates, the code of conduct and pitch reports; the report travels to the ICC or the host board. Every stage moves information through email, PDF and oral account — channels nobody outside can independently verify.

Place Luzhniki beside Villa Park and the distinction clarifies. In the 2026 final the data was sound and the law was sound; the argument was about interpretation. On 17 June 2026, Aston Villa versus Sheffield United, it was the reverse: Orjan Nyland carried the ball fully over the line, goal-line technology missed it, the match finished 0-0. The data was wrong, not the reading.

The ghost goal taught me that empty stadiums still have witnesses. The cameras were there. Cricket simply does not preserve them in a form an independent party can later audit.

Blockchain is not magic here; it is a bookkeeping method. Each entry is timestamped, chained to the hash of the previous one, and copied across many holders, so a quiet edit will not match the rest. A smart contract releases payment or notice the moment a condition is met, without depending on anyone's diligence or goodwill.

In cricket today, the technology lives in ticketing, fan tokens and digital collectibles. It is absent from governance, sanctions and referees' reports. That gap is the subject.

Frame one: the over rate. In 2026 the ICC amended playing conditions to punish slow over rates inside the match — an extra fielder inside the circle in T20Is, run penalties and match-fee deductions in ODIs and Tests. The calculation is arithmetic: when each over began and ended, which stoppage qualified. Arithmetic suits a ledger, and every excusal the referee grants would itself become a visible entry.

Frame two: DRS. A review is a small document — ball-tracking coordinates, UltraEdge audio, the TV umpire's identity, the time of decision, the exact playing condition applied. The Hawk-Eye Smart Replay System introduced in IPL 2026 moved this forward, giving the TV umpire and operator a split screen. But the system stays inside the broadcast room, unauditable from outside.

One number deserves more attention than it gets: umpire's call. It is an admission that tracking carries an error margin. If that margin were a fixed, published figure, the argument would shrink by itself.

Frame three: money and integrity. A franchise contract involves at least five parties — league, franchise, board, player, agent. Match fees, appearance fees, NOC deadlines and injury releases are written on paper but executed through memory. Smart contracts trigger on condition and timestamp every trigger. Corruption cases usually turn on chronology: who reported what, and when. I do not chase villains. I chase the sequence that made the breach inevitable. A hash-chained sequence does not depend on an investigator's recollection.

The ledger does not fix everything. If the sensor never saw Nyland's ball, the chain will immutably preserve a falsehood. My old technology-failure checklist still applies: two independent verification sources before publication, and a separate line noting where the human erred and where the machine did.

The real obstacle is not engineering but appetite. An immutable record ends discretion, and discretion is useful to referees, boards and broadcasters alike.

August 2026 offered the same question in different clothes. Barcelona said La Liga's financial rules would not allow Lionel Messi to stay; I spent 72 hours inside the league's 247-page rulebook and found how a debt above 1.3 billion euros and Article 41 made the exit inevitable. The rule was public, the arithmetic nearly so, and millions still read the outcome as caprice.

One precise comparison, with its limit stated: the 2026 final VAR handball showed that footage plus law can build a decision. But football's VAR is an in-match instrument; cricket's ledger question is post-match record-keeping. Different problems, one shared appetite for accountability.

Within three years, I expect at least one franchise league to publish a timestamped, independently verifiable ball-by-ball officiating log. The pressure will come from betting-integrity investigations and player-payment disputes, not from referees. Which raises the simpler question: if the arithmetic is public, who volunteers to open the record first?