From Ball-Tracking to Blockchain: Who Actually Owns Cricket's Frame?

In the press box at Chattogram's Zahur Ahmed Chowdhury Stadium last season, I watched something that bothered me far more than the result. The on-field umpire said not out. The batting side reviewed. On the giant screen, ball-tracking bloomed — the ball striking leg stump, the graphic almost theatrical. The crowd roared, certain the call would be overturned. The third umpire's monitor was asking a different set of questions. Where exactly was the point of impact relative to the line of the stumps? Was there bat involved before pad? And did the projection fall inside the umpire's-call margin? Three answers combined, and the on-field call survived. The graphic said one thing. The playing conditions said another. And inside those same two minutes, a ball-by-ball data point had left the ground for the broadcast compound, travelled to a data partner's server, and reached a betting market within seconds. The question now is not whether the umpire was right. It is who owns that frame — and who is guarding its signature. International cricket introduced the Decision Review System in 2026, first used in the Sri Lanka versus India Test in Colombo that July. In its early form it existed to settle line calls. Later amendments to the playing conditions added ball-tracking projection, UltraEdge, and the strangely honest concession known as umpire's call. A modern review contains at least three separate checks: where the ball pitched, where it made impact, and what the projection toward the stumps shows. None of the three is a simple yes-or-no question. Each carries a calibration margin. This is why the 2026 Russia World Cup VAR debut remains the most useful precedent I know. That tournament produced 29 reviews, 17 of which overturned the on-field decision — including the Griezmann penalty in the 58th minute of France versus Australia. The controversy did not stop. The reason is obvious: accuracy alone does not build legitimacy; review design does. Who may request a review, at what moment, with how much time, and who answers when a call flips — unless those questions are settled first, even a flawless screen image cannot quiet suspicion. In cricket the suspicion is more complex, because the data flow splits into three layers. First, the technology supplier and implementation partner. Second, the broadcaster and producer. Third, data partners, fantasy platforms and betting markets. An anti-corruption unit sits somewhere in that chain, yet a full institutional framework governing the commercial flow of ball-by-ball data is still at the discussion stage. This is where blockchain enters — and this is where the greatest scope for misunderstanding sits. Slow the tape down, and let the frame speak. The journey from ground to betting market becomes clearer step by step. Step one, capture. Ball-tracking cameras, UltraEdge microphones, occasionally sensors. A single delivery is broken into roughly twenty-five frames, and in each frame the centre of the ball is marked by pixel. A small pixel drift here changes every calculation beneath it. Dirty input never produces clean output. Step two, projection. Calibration data produces the curve of the ball, then a line is drawn to the stumps. Under the laws of the game this is an opinion, not evidence. A dazzling graphic presents it as evidence, while the decisive sentence lives in another clause of the conditions. Step three, distribution. Compound to server, server to third party. Television scores, streaming feeds, fantasy apps, sports books — almost simultaneously. Modern delivery has pushed the average lag down to two to five seconds. Step four, derivatives. The line, the length, the fielding position, which fielder stands where — all of it arrives through a single query. If a scorer mistypes a code, if a sensor drifts, if an umpire's call is tagged wrongly, the graphic will not reveal it. The problem sits directly in the feed. Step five, what blockchain can do. A hash-chained ledger can state precisely which record was written by whom and when, and any later alteration shows up. Consensus makes rewriting old blocks arithmetically hostile. For an audit trail, that is excellent machinery. But blockchain does not generate data by itself. Whether the ball hit the stumps, whether bat touched ball — that must arrive from an outside source, an oracle. Once the oracle must be trusted, the ledger stops being an independent test of truth. It becomes an immutable copy. Step six, the genuinely new part. The most useful application is not ball data but decision-process data. Which camera angle the third umpire examined, at which timestamp, what projection margin was applied, where the UltraEdge spike landed — written into a tamper-evident log, those records answer the argument before it starts. That is the defensible definition of blockchain in cricket: a signature of the process, not a seal on the truth. Fifty-two years of watching the game have taught me one clear thing: what spectators see on the field and what actually grounds match officiating are rarely the same thing. Even seasoned batsmen like Shakib Al Hasan, Mushfiqur Rahim or Tamim Iqbal pause a moment before signalling a review, because the decision is not theirs to make. By the same logic, a record on a ledger does not put the decision in the hands of the node where the sensor is mounted. The crowd's emotion is understandable. Seeing the ball land on leg stump on a giant screen, anyone wants to believe the truth has been revealed. Blockchain optimists feel much the same way: once a hash lands on the chain, reality itself seems notarised. A hash is an immutable fingerprint. It is not reality. There is an amusing parallel with the laws. The conditions never say ball-tracking is final. The on-field umpire remains at the centre of match control, and umpire's call is the proof — an explicit admission of imperfection. Most overturned reviews trace back to calibration: how damp the pitch is, the camera angle, how much the ball spins. Blockchain cannot detect an error in the data feed; it can only risk freezing a weak input permanently. One further point deserves space. Years of watching tell me the heaviest side effect of live ground data is the betting market. A ledger can clean the pathway of data, but it does not clean the demand. If anything, transparent data becomes more trustworthy raw material for that market. The next reform will land on the signature control of the frame — who mounts the camera, who calibrates it, who writes its description. Whether we notarise the process, or notarise the error along with it, is the question still open.