From the Umpire's Room to the Blockchain Ledger: Why Cricket's Decision Book Needs an Audit Trail

On the night of 14 July 2026, at three in the morning, I sat in a ten-by-twelve-foot room in Mymensingh watching the Lord's scoreboard. England 241, New Zealand 241, the Super Over 15–15. The decision that then settled the World Cup came not from bat or ball but from a paragraph in the tournament's playing conditions governing boundary countback. The side that hit more fours and sixes was champion. I opened my notebook and wrote down the date, the match number, the clause number, the outcome. Months later that clause was erased from the playbook. There were press conferences, there were explanations, but nobody could show which wording had stood in which version, who changed it, and on what date. Cricket has no public, tamper-proof ledger of its rule changes. That is where today's question begins. I began with one bedroom, one rulebook, and a suspicion the table was lying. In 2026 I logged 214 officiating decisions across the 2026–17 Champions League and the Europa League final, measuring referee reaction time from 50-frames-per-second video at 0.28 seconds. The habit taught me one thing: a decision is a branching tree — incident, camera angle, clause, outcome. Write the tree down and anyone can verify it later. Nobody has to remember it. Cricket's governance is laid out in three layers. The slowest is the MCC's Laws of Cricket, which change on the scale of decades. The middle layer is the ICC's playing conditions — revised before every tournament, and usually published without a version number. The fastest layer is match-day decision-making: the third umpire's room, the ball-tracking software, the match referee's report, the anti-corruption unit's files. The upper two layers can be read by anyone. The bottom layer can be read by almost no one. A match referee's disciplinary findings are not published for the general public, and investigation files stay sealed. Blockchain here is a plain technical structure: an append-only ledger, in which each new entry carries the hash of the previous one. You cannot tear out an old page and slot a new one in, because the chain of hashes breaks. Cricket's problem is precisely the absence of such a ledger — proof of who touched which cell, and when. Take one DRS review. The incident: the on-field umpire has given it out, and the third umpire is hunting for an edge on screen. Branch one — did the review arrive inside the time limit? Branch two — is the UltraEdge spike the bat's edge, or the rustle of a pocket? Branch three — does the ball-tracking projection strike the stumps, and if less than half the ball does, the decision returns to the on-field umpire, which we call 'umpire's call'. Branch four — did the third umpire speak to the match official, and what was said? At every junction of this tree sits a human being, and beside every junction sits a document the public never sees. Ball-tracking and UltraEdge calibration certificates are produced session by session — frame rate, margin of error, where the cameras were placed in that stadium, how the light was. Where is that certificate filed? Not in my hands. That is the first hole in my ledger. The second hole is in rule versions. If a playing condition is reinterpreted mid-tournament, today's system cannot prove what the previous version actually said. In 2026 I watched all 64 Russia World Cup matches and logged 455 VAR checks, 20 on-field reviews, 17 overturned decisions and a record 29 penalties, checking every call against the 2026–19 IFAB Laws. — Root: Referee That ledger was cited by four Bangladeshi outlets because every cell was verifiable. In cricket, where is that version trail kept? The third hole is in the money ledger. In franchise leagues, a player's contract, his no-objection certificate and his payment schedule usually sit on three separate desks. Whether it is the Bangladesh Premier League or another franchise tournament, a player often does not know which desk his paperwork is stuck on. A smart contract will not stop corruption; but if contract, clearance and payment stages sit on a public, immutable ledger, there is at least proof of whose paperwork has been hanging, and for how long. Here blockchain works as an instrument of hygiene. In the middle of this I want to pull in one of my own datasets, because the method is the point. In 2026, when stadiums emptied, the numbers finally spoke without the crowd — I coded 306 post-lockdown matches, 1,842 fouls, 73 penalties, 1,106 yellow cards. Fouls per match fell from 26.3 to 22.8, and the home-win rate dropped from 43.2 per cent to 38.1 per cent. The official is not a machine of principle but a machine of environment. I do not count the points until I have audited the cells beneath them. This is where I want to argue against my own proposal. The comfortable idea that publishing everything improves officiating is not what my data says. When people sense they are watched, they do not follow the law; they follow the log. If every review's second-by-second timestamp becomes public, umpires will be pushed into faster decisions — and speed will then compete with accuracy. That is audit theatre. The second problem: a ledger does not create truth. Three kinds of gaps must be told apart: missing data, which was never collected; inaccessible data, which exists but is fenced in by proprietary rights; and actively concealed data, which has been deleted. Investigation files should stay sealed — I have no objection, because naming a suspect early destroys his livelihood before the inquiry is finished. But the existence of a sealed inquiry should sit in the log: date, type of allegation, status of resolution, no names. It is not justice for an umpire's or a player's livelihood to dangle from an incomplete, half-published ledger. So what is the path? My proposal is bookkeeping. The ICC and member boards would write the hash of every playing condition into a public ledger the moment it is published — an amendment would add a new version, not erase the old one. Then, each session, the existence and hash of the ball-tracking and UltraEdge calibration certificate would be logged, without breaking technical confidentiality. Finally, franchise contracts, clearances and payment status would move to an audit-accessible desk, where a player can see for himself where his paperwork stands. My confidence level: within three years, at least one Test-playing board begins conditions-hashing — a 60 per cent probability. My ledger closes at the end of the 2026 season; if by that date I cannot find a public conditions ledger from any board, I will record my prediction as wrong. The question will remain anyway: if we can catch a frame in a review's slow-motion replay, why can we not catch who changed a clause of the rulebook, when, and without how many people knowing?