From Lord's Overthrow to Blockchain Logs: Who Verifies Cricket's Review Record?

I still watch the last over of the 14 July 2026 Lord's final frame by frame. Ben Stokes' bat deflects the ball towards third man, the fielder's throw returns and strikes the bat again, the ball reaches the boundary, six runs, scores level. Both sides score 15 in the Super Over. Then the boundary countback rule hands England a first World Cup. Sitting at a Dhaka desk that evening, I could not answer one question: in which second did the ball touch the rope, who recorded that, and how would I prove it if the record changed later? The problem was not the law. The problem was the log.

I built the five-point review log in Dhaka because memory is not a review protocol. In 2026, reviewing an LBW call from the 19th over of a Bangladesh Premier League match, I worked through six angles and logged the on-field call, the 48-second check, ball-tracking coordinates, the UltraEdge spike, and the final decision under five headings: law, camera angle, contact, clear-and-obvious threshold, final call. It became my desk's first standardised template. The template stayed on paper. The decisions stayed inside broadcasters' and technology providers' closed servers.

Context

Cricket invited technology in to fill gaps in the law. DRS began as a trial in the 2026 India-Sri Lanka Test series and became mandatory in Test cricket after 2026; its use spread gradually through ODIs and T20Is. Every review now follows a protocol: the on-field umpire gives a call, a review is requested within 15 seconds, the TV umpire examines multiple camera angles, ball-tracking projections and audio spikes, then delivers out, not out, or umpire's call.

There is the snag. Which frame, which angle, which millisecond produced the spike, all of it sits inside proprietary systems. The match ends, the broadcast ends, the review becomes history. Two years later, if someone claims the log was altered, nobody holds neutral proof. At the 2026 World Cup I ran a live VAR tracker across 64 matches from my desk, covering 29 penalties, 22 goals and 20 overturns, updated every 15 minutes. Regional desks cited it, yet the only source was my file: one list, one owner, zero verifiability. Cricket is weaker still, because it has no individually identifiable document for each delivery.

When football returned in 2026, I wrote a 48-hour emergency protocol: isolate referee audio, map silent-stadium echoes, verify offsides from two independent angles. Three South Asian desks adopted it. Cricket cannot replicate that method, because it lacks the per-event paper trail football generated for that single fixture.

Core Analysis

Blockchain's value lies not in crypto excitement but in a plain arithmetic rule called a hash chain: every new record embeds a hash of the previous one. Altering a later entry forces an alteration of the earlier entry, otherwise the chain breaks, and anyone can detect the break.

What that record should contain becomes clear from my five-point log. Each review event would carry match ID, innings, over and ball, a millisecond timestamp, every camera angle and ID used, ball-tracking coordinates at bounce and at the stumps projection, the UltraEdge spike value, the original on-field call, the TV umpire's final ruling, and an umpire's-call flag. Each event hashes into the match record, each match into the series record. Publishing a single Merkle root per session would let anyone confirm, without exposing the raw frames, that the session log has not been altered since.

Cricket has already touched blockchain. In 2026 the ICC announced a digital collectibles partnership with FanCraze, and in the same year Cricket Australia announced an NFT agreement with Rario. These are emotional products, not decision infrastructure. Fan tokens and digital cards sit at the top layer of the cricket economy; the real foundation is the integrity of match data.

Three concrete uses sit on that foundation. Immutable review logging, so an LBW decision can be replayed in full years later. Smart contracts for franchise auctions and player payments, where money is released only when pre-agreed conditions are met and every amendment is recorded. And for integrity work, a comparison between the official log and live market data: when the two drift apart, that gap itself becomes a signal for analysts.

The behavioural gain is measurable over time. Review-retention rules shape captaincy, because losing a review removes a late-innings option, so players grow more conservative with uncertain calls. Decisions are data; decision-making patterns are data too. Neither can be measured reliably unless the underlying record survives intact year after year. Framing the tension between the fear of losing a review and reading the scoreboard requires an untampered log.

The most needed reform, however, is institutional rather than technical. If the threshold calculation file never becomes public, the hash chain will only prove one modest truth: that not everyone was shown the same frames.

Contrarian Angle

The uncomfortable part is this. The Lord's boundary countback was scrapped in October 2026 by rewriting the rule, not by upgrading the technology. Correcting a bad decision sometimes means editing the law, not the code.

Second, umpire's call is not a data problem but a threshold problem. Ball-tracking says the ball is hitting the stumps, yet the on-field call stands, because being inside the margin of error is not the same as being certain. Blockchain will not move that threshold by a single decimal place. It only guarantees the calculation made on the day was never quietly rewritten.

Third, Dhaka's reality differs. A World Cup broadcast offers far more camera angles than a routine BPL fixture. A low-angle immutable log is still possible, but it is an immutable record of an incomplete picture. Where no camera exists, the chain adds nothing.

Fourth, public review data carries a hazard I have watched up close while working remotely. Abuse directed at TV umpires on social media has grown in recent years. When every frame becomes public, explanation gives way to judgement. A referee's eye is not intuition; it is a habit built frame by frame. If everyone gains the right to check those frames, everyone must share the responsibility that comes with it.

Takeaway

The next step is probably this: the ICC and broadcasters publish session-level hashes, a public review index takes shape, and a mandatory 48-hour verification window becomes standard, the way I applied it to restart coverage in 2026. The question is no longer technical. When the language of the scoreboard and the language of the data disagree, which one will cricket believe?