From DRS to Blockchain: The Limits of Cricket's Technology and the Real Question of Trust

19 March 2026, Melbourne Cricket Ground. India versus Bangladesh, quarter-final, mid-innings. Rubel Hossain bowled, the fielders appealed, the big screen rolled the replay, and then came the waiting — minutes of it. I was in a small studio in London, staring at the ball-tracking graphic, asking the only question that mattered to me: there are many angles, but which one is telling the truth? Rohit Sharma survived that night, made 137, India won by 109 runs, and Bangladesh went home. Ten years on, open the replay and the same question surfaces in comments from fans on both sides of the border: why did the doubt survive the technology?

In 2026, the ICC removed the soft signal for catches that had to go upstairs. Some called it a win for transparency, others a quiet retreat from responsibility. Now a new word keeps appearing — blockchain. The pitch is almost advertising-simple: if ball-by-ball data, ball-tracking logs, even tickets and fan tokens sit on an immutable ledger, nobody can quietly change anything later, and fan distrust will drain away. Roll the tape back to the moment before the flashpoint, though, and a different picture emerges. The problem was never a shortage of technology; it is ownership and explanation.

Context: who owns the data, who owns the call

DRS entered international cricket in July 2026, during India's tour of Sri Lanka in Colombo. Layer by layer it has grown — UltraEdge, Snicko, HotSpot, ball tracking. Each layer belongs to a different company, a different contract, a different software version. On the field, an umpire makes a decision. On screen, the graphic a fan sees is assembled in a broadcaster's vendor room. Ball tracking, UltraEdge and Snicko do not belong to any cricket board. So where the decision is, the data is not; and where the data is, the decision is not.

On top of that sits the umpire's call. Ball tracking projects whether the ball would hit the stumps, and that projection carries an error margin. When the ball grazes the outer edge of the stumps, the model cannot give a certain answer, so the on-field call survives. The 3.5-metre rule is blunter still: when the point of impact is more than 3.5 metres from the stumps, the on-field decision stands unless the ball is shown to be hitting the stumps outright. Together, these rules reveal something obvious once you say it aloud. DRS never searches for truth; it searches for an acceptable threshold of proof. That is not cricket's weakness. It is cricket's reality.

On top of that reality sits the data economy. The same ball-by-ball feed powers broadcast graphics, fantasy leagues, betting markets and team analytics. Data is generated in one place, sold in many, and audited nowhere. It is exactly this gap that blockchain proposals point at. In 2026 the ICC announced a partnership around official digital collectibles, and several T20 franchise leagues have begun experimenting with NFT ticketing and fan tokens. Cricket's product is no longer only the match; it is also the feeling of watching the match.

Core: frame by frame, where the technology stops

Let the tape play slowly. An LBW review contains four separate questions, and they have different natures.

First: where did the ball pitch? This is a measurement. Multiple cameras, a tracking system, frame-by-frame position — an error here should be detectable. Second: where was the impact? Also a measurement. What these two stages need is not more technology but a chain of custody. Who generated the position data, when, and was any of it altered afterwards — none of that has a written answer today. This is the narrow ground where an immutable ledger genuinely helps. If both sides of a fan-clip-versus-official-feed argument had a single shared record, at least the allegation of tampering would die.

Third: would the ball have hit the stumps? This is a forecast, not a measurement. The system computes a future, and that computation carries an error band — one a fan never sees on screen. Two millimetres decide the outcome, yet the graphic renders as a single confident line. Fourth: did the ball touch the bat's edge or the pad? UltraEdge has to separate a spike from stadium noise, from the sound of ball on pad, from bat and pad happening together. Here technology supplies evidence and a human supplies interpretation.

Blockchain can help with the custody problem in the first two stages. It cannot touch the third and fourth. A ledger can prove the data was not changed; it cannot prove the data was right. Fairness comes from the limits of data, not from its integrity. The removal of the soft signal in 2026 was effectively an admission of this: where reliable evidence does not exist, stop performing technology and let the umpire decide.

So the realistic uses of blockchain in cricket are far smaller than the pitch suggests. Ticketing — tokenised access is a sensible fix for counterfeits and touts. Franchise leagues — smart contracts can automate contract payments, match fees and prize money. Integrity — preserving a tamper-proof timeline of player movements and suspicious betting patterns. All of it administrative, all of it outside the moment of decision. Anyone expecting a ledger to settle the umpire's call has not done the arithmetic on the tracking error band.

Contrarian: a ledger does not end the argument, it adds a market

My deepest hesitation is the fan token. A fan token is a tradable asset whose price rises when the team plays well and falls when it does not. Its value therefore rests on fan emotion rather than on cricket. For franchises, tokens and NFT tickets are a new revenue line, and that line becomes urgent precisely when costs rise and dependable income does not. The technology that arrives to soothe suspicion ends up packaging the feeling of being a fan and selling it. The question worth asking is simple: who is the ledger written for — the sceptic, or the resale royalty?

Second hesitation: transparency theatre. The whole magic of a blockchain happens at the moment of writing. Hash the file and whatever existed when the file was created stays intact. But who creates the file, who granted access, who audits — the chain has no answers. This is where I draw my line. Proof and belief are different territories. Proof needs a ledger, and there the case is clean. Belief needs explanation — direct, on microphone, in twenty seconds. What generated the most anger in 2026 was not the eventual verdict but the wait. Ninety seconds of silence breeds more suspicion than half the error margin on a modern tracking system.

I will defend umpires, but not behind a shield labelled blockchain. Under umpire's call, accountability lands on one person's shoulders — 'he got it wrong'. The system that produced the protocol disappears behind a neat black-and-white answer. In my inbox, barely one comment in eight is about an umpire; all eight are about timing and communication. I would rather concede that umpires get things wrong — the Confederations Cup produced two consecutive days of it — because the incidents hurt less when they are not hidden.

Takeaway

My decision threshold is this: while the protocol stays unpublished, the data stays privately owned and the third umpire stays inaudible, putting a blockchain on cricket is locking a heavy bolt on a door that has no frame. Reverse the order. Publish the tracking error bands, publish the logging process, let the third umpire explain the call — then anchoring that record with a hash becomes the easy part. Without it, a leaked replay clip will do more damage than any NFT can repair.

So I leave the question with the fans: which would you trust more — a verifiable glowing hash on a screen, or one sentence from the third umpire: 'The ball would have hit the stumps, and I am not asking you to be certain'? Put your answers in the comments. The next review starts there.