From Scoreboard to Blockchain: Who Verifies Cricket's Data?

Goa, 2026, inside the bubble. Bengaluru FC beat Kerala Blasters 1-0, but there was not a single fan in the stands. I stood forty metres from the pitch and heard only studs on turf, breath, and the fourth official's whistle. Sunil Chhetri's pre-match habit made it into my notebook — clapping toward an empty East Stand. But the moment the match ended, something else happened, and it was no longer a story about the stands. The score, the ball-by-ball data, the player-tracking — all of it scattered across the world within seconds. A fan in Dhaka, a fan in Bengaluru, a fan in Dubai — all of them got the same scoreboard. The question is: who actually made that scoreboard, and who verified it? Based on my years of watching matches, cricket's strangest quality is the sheer abundance of its numbers. In a football match you can count goals, shots, passes. In a T20 match, every ball spawns dozens of data points: bowler speed, line and length, the batter's swing plane, field placement, the wagon wheel. Today these numbers no longer live only in a commentator's notebook. They live on the official data partner's server, in the broadcaster's graphics, inside the fantasy platform's algorithm, and in the live feed of a betting company. This entire supply chain is cricket's silent infrastructure — infrastructure the fan in the stands never sees. It is worth breaking that chain open once. First sits the scorer at the ground, writing every ball by hand. That information then moves to the feed operator, who digitises it. The official data partner then verifies and distributes it to broadcasters, apps, and betting markets. Since 2026, Sportradar has performed this role as the International Cricket Council's official data partner. At the very end sits the fan, who sees only the result, never the source. If a single wrong number enters this long chain, no one can say where it entered. At the 2026 World Cup in Russia, I saw another face of this chain. There, news of Japan's 2-1 win reached Indian readers before dawn. I filed eight dispatches from Saransk, but the most-read piece was a 1,500-word guide on how a fan in Bengaluru could watch the knockouts at 11:30 p.m. IST. 'The final whistle in Russia reached Bangalore before breakfast' — that was the essence of my whole job. I understood then that the time zone is not just a climate problem; it is a data problem. The result is declared in one place, the celebration happens in another, and the verification happens somewhere else entirely. That gap is the widest distance between a fan and the game. This is where blockchain becomes relevant. Most talk around sports data revolves around 'faster scores' or 'tokens for fans.' The real question is deeper — data provenance and integrity. Where did the number on the scoreboard come from? Which scorer wrote it, which system verified it, who can change it? Blockchain's most honest application lies exactly here — not spreading the live score faster, but keeping an immutable, timestamped record of every data change. Think of a cricket scorecard as a small chain. Every ball adds a new block — runs, ball, batter, bowler, fielding position. If these blocks are written to a single verifiable ledger, no one can later alter the result or 'accidentally' erase a ball. At the 2026 Qatar World Cup I saw the power of tracking data — Sofyan Amrabat averaged 12.1 kilometres per match, and that single figure explained why Morocco's 4-1-4-1 shape worked. If that data were bound to a public, verifiable ledger, the room for manipulation would shrink sharply. Consider a small example. If a no-ball in the final over of a T20 match is not recorded correctly, the result can change, and that error spreads identically across every app and every scoreboard. Under tournament pressure such errors are most dangerous, because millions of fans then trust the same wrong number — and no one gets a chance to verify it. You may ask what the fan gains. The gain is trust. Those of us watching from afar often see two different numbers — a few seconds of lag between the broadcaster's score and the app's score. That lag breeds suspicion. Blockchain can turn that lag into proof: which source the number came from, when it arrived, who confirmed it — all in one place. Another door blockchain opens in cricket is fan engagement. Platforms like Socios.com issue fan tokens, letting supporters vote on small club decisions. The token, the vote, the ownership — all written to the blockchain, so a club cannot later reverse its decision. Some cricket franchises and leagues have begun walking this path. There are also efforts to use smart contracts for match tickets, digital collectibles, and event-based prize distribution. The ICC itself has released digital collectibles. In fantasy sports the matter is even clearer — the scoring of millions of fans across Bangladesh and India depends on exactly that data feed whose source they never see. But I want to stop here, because this story has a dark side, and ignoring it would be dishonest. Cricket's data today largely travels as a live feed into the hands of betting companies. The data generated every second during play is the most valuable product of all — and it is often used not for the fan's benefit but in the betting market. Blockchain does not solve this on its own. In fact, if the same fast, precise feed is written to a blockchain, betting companies get even better, even more verifiable data. The technology is neutral; the question is who controls it. To me, the darkest side of cricket's data age is exactly this — information born from the players' bodies becomes a betting product before the game has even finished. Inside the 2026 Goa bubble I saw this up close. We played twelve matches in empty stadiums, and during that time I quietly helped arrange fourteen mental-health sessions. I learned then that a player's data is not only performance — it is a record of body and mind. Blockchain could make a player the owner of his own data. That is the biggest opportunity and the biggest risk, because if someone buys that ownership, the ownership itself becomes centralised. If the data belongs to the player, it is protection; if it belongs to the league, it is surveillance. Now to the objection I hear often: blockchain is just hype, what does it have to do with cricket? That objection is looking in the wrong place. Blockchain is no magic; it is a method of keeping a ledger — a public, tamper-proof ledger. The problem is not the technology, but who keeps that ledger and who has the right to read it. If a club, a league, and a broadcaster together run a single central ledger, it is no longer decentralised — whatever it is called. And if the fan holds only a token whose price rises and falls, without the power to verify, that is not data transparency but a new kind of gambling. Real transparency means the fan can verify it himself — which scorer wrote which ball, when it was stamped, who tried to change it. And here my suspicion deepens — cricket's verification has never been done by machines, but by people. Scorers, groundstaff, managers — these invisible workers have written the game's data by hand for decades. Blockchain cannot replace those people; it can only record their work immutably. In my bus-seat diary I have seen that a match's most important detail often comes from the person whose name appears nowhere. 'I keep the beat from bus seats and locker-room silence' — that line is my working principle, and for cricket's data it is also true: the real story is not on the scoreboard, but behind it. So what is the solution? I do not want to give a clean answer, because I still lack a fact verified by two independent sources. My rule is simple — I do not call something true until two separate, independent sources agree. The same rule applies to data. But the direction is clear: a public, open, verifiable data layer is needed, where the scorer, the league, and the fan all see the same copy of the truth. There the data stays in the hands of players and fans, and verification happens independently. Blockchain can be one tool for building that layer, on one condition — it must be built for the fan, not for the betting market. 'I don't chase headlines; I keep time with the team.' In cricket's data age, this principle is my greatest caution. So the question for the fan is no longer simple — it is not how fast your scoreboard arrives. The question is whether it is true, and whether you hold the power to verify it. If the answer is no, then blockchain or anything else, technology alone cannot restore trust.