The DRS Ledger: Who Keeps the Account When Cricket Puts Its Decisions On-Chain

Hook

On 25 August 2026, at Headingley, Nathan Lyon bowled to Jack Leach. The ball hit the pad. Umpire Joel Wilson said not out. Australia reviewed. Ball tracking arrived on the screen and showed the ball would have struck the stumps. The decision did not change, because the tracking result sat inside umpire's call. England won by one wicket and the Ashes series stayed alive.

Where was Joel Wilson standing? At the bowler's end, behind the stumps, twenty-two yards from the batter. Whether the ball pitched in line against a left-arm bowler, he judged from twenty-two yards away, through a narrow angle on the leg side. His sightline and the tracking cameras' sightline were never the same sightline.

That night I opened my notebook and wrote an uncomfortable question: what had I actually watched on screen, data or an animated drawing of data? Every review since has returned me to it. Cricket's most contested dataset is its least audited dataset. That gap is where the blockchain conversation actually belongs, and it is exactly where most technology marketing stops.

Over seven years I have logged 214 reviews by hand: which end appealed, how many seconds the third umpire took, how many angles were shown, which angles were not, and what the final signal was. After 214 reviews I understood that the problem is not the decision; it is how the decision is manufactured.

Context

The DRS paperwork begins on 23 July 2026, with the Sri Lanka against India Test in Colombo. In seventeen years the system has settled into three layers: ball tracking, stump microphones, and the third umpire's console where the feeds are stitched together.

The player review arithmetic is simple. Tests carry two reviews per team per innings; one-day internationals and T20 internationals carry one. A successful review is retained, a failed one burns. In 2026 the ICC narrowed the umpire's call zone so that fewer reviews ended in that grey band. In May 2026 the ICC Cricket Committee removed the soft signal for catches and run-outs. Every amendment pushes the same way: less guesswork, more data.

But whose data? Nobody asks. The host board installs the cameras, the supplier runs the tracking model, the broadcaster builds the feed, and the match referee's office supplies the final interpretation. Four hands on one incident, and none of them in the spectator's hands. Whether the graphic we watch is a faithful rendering of the raw file or a curated edit for broadcast is not a question we can currently answer.

To be clear about what a blockchain does and does not do: a distributed ledger is an append-only accounting record, where each entry carries a hash and a timestamp and cannot be quietly rewritten. A smart contract is code that executes when conditions are met. Cricket has already tasted this, on the revenue side rather than the decision side. The ICC struck a digital collectibles partnership with FanCraze in 2026; Cricket Australia tied up with Rario in 2026. Both are fan-engagement projects. Neither is a transparency project.

The irony is sharp. Cricket keeps its most obsessive records where the public cannot see them, in the ball-tracking engine, and has bolted the chain on where records matter least, in fan tokens.

Core Analysis

My notebook shows four gaps. A chain can partly fill each, and each has a boundary the chain cannot cross.

Gap one: the distance between animation and data. We never see the raw tracking file, only the rendered visual. This is not merely technical. Rendering straightens trajectories, alters frame rates, shifts camera origin. Across a bilateral series in 2026 I noted four reviews where the rendered trajectory and the following frame's ball position did not agree on the bounce point. I am not claiming error. I am claiming there was no route to check. The simplest real blockchain use sits here: the tracking engine hashes the raw file the instant the ball is released and writes that hash on-chain. Anyone can then verify whether the broadcast animation matches. It does not make the decision right, but it makes the claim honest.

Gap two: the audio chain. Caught-behind reviews often rest on a spike in the audio waveform. The height of that spike depends on stump mic gain, wind, crowd noise, and sync offset. Across thirty-two consecutive caught-behind reviews in a 2026 T20 series I logged sync quality, and roughly a third of them were not frame-perfect between sound and vision. I am not saying those decisions were wrong. I am saying a process that rests on a sync offset should itself be auditable. Hash the raw stump mic file with its timecode, and at least we know what was heard and when.

Gap three: the interval is the data. How many seconds the third umpire takes, how many angles he views, which ones he returns to, is written nowhere. My ledger shows an average of 62 seconds for LBW reviews, 47 for caught behind, 38 for stumpings. Here a caution matters: this is a hypothesis built on 214 events across seven years, not a claim about the system. The tempo of a decision is a measurable variable, and it currently lives in no ledger at all. The review interval is also a tactical reset for both teams, one that a captain can extend by spending a review.

Gap four: the review economy. Once burned, a review is gone, so reviews become currency. In Tests, top-order batters decline obvious reviews to protect the stock, and captains under pressure burn an impossible review to break a bowler's rhythm. Smart contracts can automate part of this economy: over-rate fines, match fees, sanction accounting. That sounds exciting, and it is the easiest trap in blockchain marketing.

Now the question the conversation avoids. A chain cannot fix its own inputs. Ball tracking is a device. The number the device produces can be hashed on-chain, but whether the sensor was calibrated correctly at the moment of capture is a question outside the chain. The industry calls this the oracle problem. Unless sensor calibration records and stadium geometry live in the same ledger, the DRS problem does not dissolve.

The second boundary is more fundamental. A chain can record the three-dimensional trajectory of a ball. It cannot encode what a clean catch is, what part of the bat means, or when a ball is under control. The third umpire reads shadow and finger gaps, not facial expression. The process can be made auditable. The judgement cannot. And I do not trust a pattern until it survives three angles: the stand, the bowler's end, the square leg appeal. Three records can sit side by side on a chain. Which one is correct, the chain will not say.

What emerges is a five-layer structure. Layer one, sensor input, sits off-chain. Layer two, hashes and timestamps of raw files, is the simplest and most useful application. Layer three, process logging, covers angles viewed, deliberation time, umpire position, one day a public statistic. Layer four, automated playing-condition accounting, covers over rates and code-of-conduct fines. Layer five, the one most often skipped and most important, is player contracts.

Layer five holds an old wound. The franchise leagues, the IPL, SA20, ILT20, BPL, operate as satellite systems. Talent from smaller boards moves to bigger leagues through no-objection certificates, agents, scholarships and third-party deals, and the money path is rarely visible. Quota rules get routed around by moving a player through different paperwork first. On-chain contracts do not remove that complexity, but they make it visible. Who was paid what, and how much stayed in the middle, becomes a record rather than an estimate.

Contrarian Angle

More transparency reduces outrage. In cricket that assumption has repeatedly failed. Had the raw Headingley tracking file been published that night, the argument would not have shrunk; it would have grown new branches about ball width against stump width, about which point of the leg stump the measurement used. People want certainty, not an audit trail.

Boards also have a clear interest in the status quo. Publishing average burned reviews per match, or how often a given umpire's decision is overturned, means writing your own performance audit. Umpire evaluation today lives in confidential reports, not in public view.

There is also chain theatre. Launching fan tokens and digital cards while keeping the decision ledger shut is business wearing transparency's clothes. Several leagues now put tickets, collectibles and session voting on-chain. Fine. But it pulls attention from the real question: who owns the decision data, and on what terms is it public.

Finally, immutability is itself a risk. An error written to a chain cannot be erased. Cricket is not a culture that admits error easily, and freezing one forever closes even the modest correction route. The workable answer is not editability but accretion: keep the error, add the correction beside it, and record who was accountable for the correction. That is an engineering question, not a policy one.

Takeaway

One pattern in my notebook has survived three angles: cricket has adopted technology to make decisions faster, never to make the process visible. Seventeen years of DRS prove it. From Colombo in 2026 to the removal of the soft signal in 2026, error has fallen while public access to the underlying information has barely moved.

Three things I will watch closely in the next cycle: whether any board or supplier opens an API for raw ball-tracking data; whether third umpire deliberation time and angle counts reach the broadcast and the match report; and whether a smaller board pilots a blockchain contract-verification system first, because smaller boards need it most.

Ninety minutes of silence explains more than a thousand replays, and three seconds of sync offset explains more than six camera angles. The question is not whether the decision was right. The question is who keeps the ledger of how it was made, and whether I am allowed to read it.