Where the Scorecard Falls Silent: Cricket Data's Credibility and the Limits of Blockchain

Last month in a Brisbane press box, one small thing stopped me. The scoreboard said a bowler had conceded 47 runs in nine overs. The ball-by-ball feed sat open on the monitor beside it. Six deliveries in the 14th over carried six separate figures, and the sum did not match the innings total — a two-run gap. Nobody said anything. Nobody wrote anything down. By the end of the match the gap had quietly closed itself, because somebody at the back had fixed an entry. I did not chase those two runs. I chased the silence around them. Much of what cricket calls data is the work of one tired person's fingers, and nobody checks it, because no structure for checking has ever been built. It is worth breaking open how ball-by-ball scoring works. A scorer at the ground logs every delivery — bowler, batter, runs, extras, wicket. That entry travels to a data provider's server and scatters from there into broadcast graphics, fantasy leagues, betting markets, ranking calculations, and finally the record books. Every joint in that chain holds a belief: that the previous joint was right. Records like Virat Kohli's 50 ODI hundreds or Sachin Tendulkar's 100 international centuries survive only because thousands of separate entries were written correctly and never quietly altered. The record belongs to the batter. Its foundation belongs to the scorer. The two cricket cultures I move between treat numbers differently. In a Dhaka tea shop, people argue over a score for an hour, because there the number is part of memory. In a Brisbane press box the number is a product — it enters the feed, climbs into the graphics, and is forgotten by the next match. In one place the number is emotional, in the other it is operational. In neither place does anyone ask who wrote it down, or whether someone changed it afterwards. The trouble is that correction is legal in cricket. Wrong runs, wrong byes, wrong no-balls — all correctable. But where does the correction itself live? Usually nowhere. The old figure is deleted, the new figure takes its place, and nobody can tell that anything moved. I keep a notebook called Pitch Images. No scores in it, only images — an abandoned scarf, the tilt of an empty seat, the sound of a press-box door. For years I thought the scorecard was the last word on a match, until I watched a number change quietly. Since then I treat numbers as the last evidence, never the first. Blockchain can fill this gap in exactly one way: it keeps proof of a score's movement. What the number is, that is not the chain's job. Whether the number changed — that is. The mechanism is simple. Each delivery is rendered into a unique identifier — match ID, innings, over, ball number, bowler, batter, runs, wicket, timestamp. That string goes through a hash function and returns a 256-bit fingerprint. The hash is bound to the hash of the delivery before it, so every ball carries the history of all the balls preceding it. Change one entry and its hash changes; every hash after it changes too. The chain breaks, and the break is visible. Here is what gets skipped: blockchain does not make data true, it makes data immutable. The difference is enormous. The SHA-256 standard is specified in NIST's FIPS 180-4 document, and Bitcoin's genesis block was created on January 3, 2026. The structure is not new. The application is. A workable cricket design would be hybrid. Rather than writing full ball-by-ball data on-chain, only the hash and the timestamp go on-chain; the actual data stays in an ordinary database or distributed storage. A Test match can contain more than 2,700 deliveries, and writing every ball of every match permanently on-chain is expensive and unnecessary. Hashes are enough. Where is the gain? If a provider quietly changes a series average tomorrow, anyone can compare hashes and show that this number is not what it was on the night of the match. That verification capacity is the actual product. In betting markets the value is sharper still: illegal markets run on feeds, and proving when a feed changed is currently close to impossible. A tamper-proof log could give a regulator a timeline for the first time. Consider aircraft maintenance logs. Every repair is signed, retained, and answerable years later. Cricket data has no equivalent. Fan tokens and digital collectibles are blockchain's loudest application in sport; cricket's most necessary one is its quietest — an immutable amendment log. There is a layer that gets less attention. Providers want their raw feeds private, because the feed is the asset. Zero-knowledge proofs offer a path through that tension: a provider can prove a specific hash existed at a specific time without revealing the underlying data. Verification without surrender of secrecy. For cricket administration this is probably the most usable proposal on the table, and the least discussed. The most important design decision is not technical but attributive. If every entry is signed with a private key generated on the scorer's device, the number has a name attached. Right now it has none. This is where my objection begins. First, blockchain does not clean dirty data; it makes dirty data permanent. If a tired scorer's error goes on-chain, it stops being an error and becomes a cryptographically certified error. What is more dangerous than a mistake is a mistake wearing a seal. Second, cricket's record books rest on the right to correct. Many figures have been revised years later, and they should be. An immutable ledger of a wrong score is worse than a correctable wrong score, because the first makes correction impossible. Third, and least comfortable: the problem is governance, not technology. The bodies that own the data derive money and power from controlling it. An open, verifiable ball-by-ball log means partial surrender of that control. So blockchain has entered cricket where revenue lives — fan tokens, digital collectibles, sponsorship — and has not entered the scorer's desk. That is not a technology failure. It is a clear statement of priorities. I accept the strongest answer to my own objection. If what goes on-chain is not the score but the record of amendments — who changed it, when, and why — then correctability is not lost; the correction itself becomes visible. Two things are protected at once: the right to fix a mistake, and the impossibility of hiding one. But the same wall stands there. Who agrees to publish that log? A board that sells data rights has no commercial reason to allow a public audit trail. So my deepest doubt is not about the technology but about where the enthusiasm points. Fan tokens sell by the minute because they convert devotion into product. An amendment log has no market, because it exposes institutional discomfort. So the next time someone says blockchain will make cricket transparent, I will ask one question: transparent to whom? The question nobody asks yet is the only real test. I still have that two-run gap written down. No explanation beside it, only a date. Perhaps a new system will close the gap soon enough. But as long as corrections stay invisible, however immaculate the scorecard becomes, our trust in it will remain nothing more than habit.