The Review Ledger: Auditing DRS Decisions in Asian Cricket and the Limits of Blockchain-Style Record-Keeping

The file that stays open longest on my laptop is called review_ledger_asia.csv. Since January 2026 it has logged 142 review events from six Asian tournaments and bilateral series, each with four columns: minute of the incident, playing-condition reference, review type, and final outcome. One evening in February I stopped mid-over over a left-arm spinner's delivery. The ball-tracking graphic showed the ball grazing the inside edge of the stumps; the screen said Umpire's Call. The crowd was screaming out, the protocol said the original decision stands.

That night I added a new column to row 142: audit_path. My frustration was not about the decision but about the route to it. Where the ball pitched, who selected the frame, on which image the line was drawn, what exactly was said between the TV umpire and the on-field umpire - none of it has an independent, tamper-proof record. In Kuala Lumpur I began logging VAR incidents; the pattern was already there.

Technology reviews in cricket are two decades old. DRS was first used in the India-Sri Lanka Test in Colombo in July 2026. Player reviews arrived in November 2026 at the New Zealand-Pakistan Test in Dunedin. Asia took time to shift: India first used DRS in November 2026 against England in Rajkot, under Virat Kohli, with Alastair Cook as the opposing captain. In October 2026 the ICC changed the Test playing conditions, scrapping the 80-over review top-up and keeping two reviews per innings. From October 2026 the soft signal was removed, so an on-field umpire's initial indication on a catch no longer binds the TV umpire.

The Asian Cricket Council is headquartered in Kuala Lumpur. The decision centre for this region's tournaments sits in my city, yet every out-or-not-out dispute is settled inside a closed tracking system. In Russia 2026 I catalogued 29 penalties and every VAR review across 64 matches; that database taught me that controversy does not end, it only gets documented.

A DRS decision path splits into four gates. The first is the trigger: the on-field umpire gives out or not out. The second is the review: did the side signal within 15 seconds, and was it genuine belief or a tactical burn. The third is reconstruction: the TV umpire examines multi-angle footage, UltraEdge and ball tracking. The fourth is the final call: applying law and threshold. Of the four, the third is the most invisible, and that is where the most information is lost.

The ball-tracking threshold is a convention, not a law of nature. If the prediction shows the ball hitting the stumps with less than half the ball's width, the call stays umpire's call, meaning the on-field decision survives. Of the 142 reviews in my log, 127 depended on ball tracking, and 38 ended in umpire's call. In 31 of those 38 the on-field decision stood. Roughly 82 percent of the time, tracking only gathered support for an earlier verdict rather than saying anything beyond it.

Usage patterns also differ by region. Asian teams take about 1.4 reviews per innings, but the success rate in my log sits around 23 percent. Innings from West Indies or Australia show slightly higher numbers. The cause is not technology but decision culture: more speculative reviews are burned on lbw and caught-behind, and under opposition sledging that speculation weakens further.

The fix is not changing decisions but making the path to them immutable. In a blockchain-style ledger, each review event's timestamp, ball-tracking software version number, camera ID and calibration file can be hashed together and chained to the previous block. If anyone alters the data later, the chain breaks, and any independent auditor can detect it. The technology is not new here - it is an immutable evidence book, which is what a forensic auditor like me tries to build in a spreadsheet every day. The only difference: a spreadsheet can be edited; a broken hash chain cannot be hidden.

Version control is almost undiscussed. Sony acquired Hawk-Eye Innovations in 2026, and ball-tracking software updates arrive mid-season. Without publishing version numbers, comparing predictions across two tournaments is effectively impossible - much like the 2026 empty-stadium study, where across 81 behind-closed-doors Bundesliga matches the home win rate fell from 43.3 percent to 33.3 percent and home penalties per match dropped from 0.29 to 0.18, against a control group of 225 pre-shutdown matches.

This is where the contrarian question lands. Blockchain keeps the evidence intact; it does not keep the judgement intact. If the threshold is wrong, an immutably logged error is still an error - it merely starts looking more credible than before. Half the ball's width is not a machine constant; it is a human convention written into law and translated into code.

The second problem is behavioural. That Bundesliga data shows that when the environment changes, referees' verdicts change too. A public ledger means every umpire's every call is permanently pinned; under that pressure many officials will start giving the safe call, and a safe call means more umpire's calls - uncertainty surviving in visible form. The third limit is conceptual: cricket's ball tracking is a binary prediction, football's VAR is continuous adjudication of moving play. The principle is comparable, the method is not, so DRS and VAR do not belong in one formula.

I propose three things. First, publish a public hash of the review ledger after every series so a second party can verify independently. Second, announce the ball-tracking software version number and calibration schedule before the match begins. Third, give the match referee an error taxonomy, splitting every overturned review into categories: trigger error, frame error, threshold error, communication error.

If a seven-second frame gap goes public at the next Asia Cup, the centre of the argument will move. Nobody will say the umpire was biased; they will ask where the ball was in the second camera's frame sequence. A referee's eye is a frame-by-frame threshold test, not a whistle - and in this region it is time to keep that eye open in public.

Method note: all data here comes from the Kuala Lumpur review ledger (review_ledger_asia.csv, 2026-2026); the sample size is small, so confidence levels across conclusions range from medium to low. The 2026 and 2026 ICC playing condition amendments were cross-checked against two independent sources.