Ball-Tracking, UltraEdge and an Immutable Ledger: The Grey Clause of DRS and Cricket's Blockchain Question

July 14, 2026, Lord's. The last over of the World Cup final. The ball deflects off Ben Stokes' bat and runs to the boundary; the umpires award six runs — two run, four for the boundary. I was in a flat in Liverpool with the scorecard and the ICC Playing Conditions open side by side. Those six runs bent the match, the Super Over tied, and New Zealand lost on boundary countback.

The clause that decided the final was not in the MCC Laws. It sat in the ICC Playing Conditions — a different page, approved by a different committee. Since then one question has followed me: if every review, every ball-track coordinate, every audio spike and every final call were written into a ledger nobody could quietly edit, where would the argument land?

DRS was first used in July 2026, in the India–Sri Lanka Test at Colombo. It was framed as the player's appeal — the right to challenge a decision belonged to the player, not the umpire. Sixteen years on, the architecture is nearly unchanged, but its internal layers are far more complicated.

A DRS decision is built in three layers. The on-field umpire: his eyes, his position, his angle. The third umpire: framing the replays, matching audio spikes, reading the ball-tracking projection. And the software: proprietary systems such as Hawk-Eye, Virtual Eye and UltraEdge, whose mathematical models appear in no published law book.

The rule hierarchy has three layers too. The MCC writes the Laws of the game. The ICC writes the Playing Conditions — the number of reviews, the limits of Umpire's Call, the boundary-countback clause. The third layer is vendor code, which is never public.

Each side gets two unsuccessful reviews per innings; lose one and it does not return. Umpire's Call survives precisely when less than half the ball is projected to hit the stumps — the evidence is not conclusive, so the on-field decision stands. In 2026 the ICC removed the soft signal for catches: a doubtful catch is no longer decided inside the shadow of the on-field umpire's prior judgement.

Referee's Eye | Scenario: deep analysis of the cricket DRS protocol.

I opened the protocol again. This time it was not a page that stopped me, but the absence of the review log itself. The core problem with DRS is not the technology; it is that a complete, verifiable, timestamped record of each decision is stored nowhere. We see only the output: "ball tracking: umpire's call." We do not see how much uncertainty sat inside that frame, what the audio spike timeline was, or which frames were discarded.

This is where blockchain becomes relevant — and where the biggest misunderstanding sits.

Start with what blockchain cannot do. It cannot change the umpire's eye, perfect the flight of the ball, or answer the political question of Umpire's Call. What it can do is write every review event into a hash chain: timestamp, frame ID, ball-track coordinates, audio spike, final decision. If someone later claims the log was altered, the chain answers for itself. That is not a technological victory; it is accountability infrastructure.

My years in this work tell me controversy is never born from a shortage of data; it is born from asymmetric access to data. In football's VAR I have seen the same design flaw — a 110-page protocol, and at the moment of decision nobody knows which frame was used. The Carabao Cup trial did not invent VAR; it revealed who could read the rule. Cricket's DRS is at least adversarial: the player initiates the challenge, so the responsibility is shared. Football's review is umpire-led, so the responsibility is one-sided. Compare processes, not just machines — cricket granted the player the right to doubt, football did not. That process difference explains why the same technology breeds two different kinds of distrust.

The same question returns in franchise contracts. The headline of an IPL deal is the fee; the investigation is the ledger entry — who was paid, when, under which condition. Here my second doubt enters: auction data models overprice young potential and barely price dressing-room chemistry. A model that measures one night's strike rate does not measure who stops an argument in the dressing room. An immutable ledger can preserve the number in a contract; it cannot preserve the chemistry.

Broadcast and betting markets connect here too. Ball-tracking and review data carry enormous commercial value, and the duty to verify that data is still vague. If review-log hashes were published, broadcasters, regulators and betting integrity units could all verify from a single source instead of making unilateral claims. That accountability link is cricket's next real test — not another camera.

Now the uncomfortable part. Suppose the ICC published every review hash from tomorrow. Would the argument shrink? My suspicion is it would grow.

The argument was never about raw data. It was about the threshold — who drew the "less than half the ball" line, and why exactly there. An immutable ledger does not answer that; it cements it. The larger problem: writing the output of a proprietary algorithm into an immutable ledger immortalises a black box. Transparency means publishing how the record was made, not only that the record cannot be changed.

This is the neutrality trap in process. The rule we treat as neutral is usually written by someone, approved by someone, and profitable for someone. —— Root: Birth of the Referee. Vendor code is secret, committee minutes are secret, but the decision is public — that asymmetry is the real fuel of resentment. In the fight between emotion and rule, emotion usually loses; but it loses not to the rule's authority, it loses to the rule's opacity.

In the next cycle, cricket's real examination is not screen resolution but log disclosure. The question is plain: if the ICC publishes an immutable hash for every review, will the crowd accept Umpire's Call — or will it ask for the source code next? Accepting an umpire's decision means accepting the rule. And to accept the rule, you first have to be able to see it.