Who Touched the Ball Data: Blockchain's Real Job in Cricket's Supply Chain

In January 2026 at Mount Maunganui, I replayed Ebadot Hossain's 6 for 46 spell at least ten times. I broke every frame down—release point, seam angle, where the ball landed on the deck—and beside each frame I kept notes pulled from three versions of the same spell: the broadcast infographic, a commercial ball-tracking feed, and the scorer's coding sheet. One ball, three definitions, three timestamps, three owners. That night my question changed. I used to ask how much seam an inswinger used. Now I ask who wrote that number down, at exactly what second, and whether anyone could change it after the match. That is where the blockchain conversation in cricket should sit—not on fan tokens or expensive digital cards, but on the provenance of data. Years of watching tape taught me that cricket data is not a single number; it is a supply chain with four layers, each with a different owner and timestamp. Layer one is capture: ball-tracking systems, stump cameras, pitch sensors, and the oldest technology of all, a human being. Whether a scorer calls a shot a drive or an edge becomes the raw material for thousands of downstream analyses, and the raw material is never recorded as an assumption. Layer two is the proxy: economy rate, strike rate, phase-based control, boundary-suppression indices. France had 39 per cent of the ball in the 2026 final and all of the game. In cricket the logic is sharper still. When spinners at Mirpur shut the slog-square boundary, the opposition's run rate does not fall because they stopped attacking; it falls because the place to attack was moved. The scorecard shows economy, not relocation. Layer three is distribution—who sees the data and when. This is cricket's most uncomfortable truth. Franchise analysts get a post-match file, broadcast gets near-live graphics, and low-latency feeds sold to bookmakers arrive first. The market stands on whichever data point moves fastest. Live cricket data being the raw food of betting markets is a sentence rarely spoken without a smile. Layer four is storage: where the data lives, who can change a version, who can retrieve a twelve-year-old file. Since joining the BCB's digital and media advisory panel last year, I have seen this chain from the inside. The realisation is mechanical rather than despairing: our cricket invests least at exactly layers three and four, where ownership and audit are decided. That gap is what pulled the blockchain wave into cricket. In November 2026 the ICC announced a digital cricket collectibles deal, and leagues and federations worldwide began testing chain-based ticketing, collectibles and fan ownership. Between 2026 and 2026 speculative enthusiasm cooled considerably, and the attention that left speculation settled on two unglamorous places: ticketing and data provenance. The first is an easy ledger. Identity-verified digital tickets, verified ownership on the secondary market, royalties to clubs from resale—a direct fix for an old black-market problem. It changes nothing at the gate and a great deal in the books. The second is harder because it reaches inside the game. For me the only mandatory use of a chain is a provenance ledger: for every data point, who wrote it, on which device, at which second, and who altered it afterwards. It is tape-room forensics with log files instead of cameras. With that ledger, three old analytical problems suddenly become visible. The first is reproducibility of phase data. The method I used on the Mymensingh bench was numbered phase maps with a timestamp on every rotation. I replayed the Mymensingh back three until the gaps started explaining themselves. The trouble is that my phase map and an opposing analyst's phase map never match, because we work from different scoring sources. An immutable ledger cannot settle the argument, but it can establish which file each argument stands on. The second is transfer valuation. In the 2026 IPL auction Sunrisers Hyderabad spent 1.4 crore rupees on Mustafizur Rahman, and the auction record is public. What is not verifiable is how much of the data behind that valuation holds up. Franchises now buy latency-measured performance data rather than scout reports. A transfer is never a name; it is a new trigger inside an old spacing problem, and telling real triggers from ego requires the birth certificate of the data. The third is injury and comeback history. Here I am most cautious, because rehabilitation records scatter across thousands of files. The hardest part of a return is not the body but the mental block, and that block is written down nowhere. Put injury data on a chain and you also raise medical privacy in the same breath. My central observation lands here. The real value of blockchain in cricket is not selling data but publishing its edit history. If a phase map is released with its source, timestamp and version record, analysts and fans at least argue over the same page. Working with Bashundhara Kings taught me this differently. They did not press the ball; they pressed the next three seconds. Where was that recorded? Not in a file—in a coach's voice, in dugout instruction. In the silent stadiums of 2026 I learned that a phase can be louder than a crowd. Tracking how clearly a keeper's calls carried in an empty ground, I found defensive line shifts changing; the data was evidence of a signal that had otherwise vanished. The biggest trade-off, though, is administrative, not technical. Running a chain costs money, nodes need maintenance, and the question of who holds the keys shifts the balance of power between boards and franchises. Every federation wants a central archive; no franchise wants to surrender ownership of its match data. An immutable ledger freezes that boundary in place—good data and bad data alike. Here I have to admit my own built-in error. A forensic mindset teaches me to fragment phases, but too much fragmentation shows readers a map instead of the gap. So after every phase note I write one separate sentence: who sweated in this match, and who is paying the bill. The numbers never answer that, and that is the reader's real question. Now to the place where blockchain enthusiasm is loudest and the reasoning thinnest. An immutable ledger does not prove truth; it proves the record was not altered. If a scorer codes an edge as a drive, that error is carved in permanently and ten years of statistics are built on top of it. Immutability is not accuracy. The second gap runs deeper. If betting markets pay most for speed, a trustless chain does not change the incentive; it only makes the race visible. Visible ledgers help some people and hurt others. Take a profile like Mustafizur Rahman's. His IPL price was set in the era of scouting intuition. Today's franchise buys strike-zone data instead—but if the buyer defines the data, auditability only verifies the buyer's arithmetic, not the bowler's value. Auditing a transfer means asking which number is ego service. In the phase usage of Litton Das and Taskin Ahmed that distinction is visible. Same ball, same field placement, but if one scorer writes voluntary run and another writes fielding error, two years later the statistics describe two different cricketers. With Mehidy Hasan Miraz, the economy rate is not the evidence; the map of overs that emptied the slog-square boundary is. Putting that on a chain requires putting the coding chain on it too—otherwise the chain only immortalises the mistake. So my test for the coming season has one condition. When a league, federation or platform claims it has moved cricket's data on-chain, I will ask one question: can an independent analyst reproduce a single phase map from it? If the answer is no, that is not a blockchain. That is a brochure.