Two Score Sheets, One Run-Out, and the Data Nobody Verified

A late afternoon in 2026. The press box at MA Aziz Stadium in Chattogram, one phone balanced on a tripod, 1,200 viewers on Facebook Live. Chittagong Abahani against Sheikh Jamal Dhanmondi Club in the Bangladesh Premier League. Abahani won 2-1. Before I could lower the microphone, a club official stood in front of me holding two score sheets.

One had a run-out recorded in the sixteenth over. The other did not. The difference was a single wicket, and that single wicket moved a bowler's economy rate, a batter's strike rate, and the night of thousands of fantasy-league players. Nobody could settle it, because no authority existed to settle it. One side said his book was right, the scorer said his arithmetic was right, and I, as the commentator, had only a phone video in which the deliveries were visible but the scorer's pen was not.

Since that day I keep a notebook. It holds no scores, only crowd sounds, rain delays, and small fractures of that kind. My work rests on one line: the stadium remembers what the scoreboard forgets. But that afternoon the reverse happened—the scoreboard forgot what it had written. That forgetting is the most expensive invisible problem in cricket today, and it is exactly where blockchain keeps returning to the conversation.

Last week a Stage-2 deep analysis packet landed on my desk, cricket domain. Before any dimensional analysis, an integrity gate had been placed inside it. The note was blunt: three claims do not match the public record, so they are flagged rather than corrected. A player's listed age, an attendance figure, and a transfer-related number.

I will not use those three numbers here. Building analysis on unverified claims is stacking error upon error. But the gate itself is the story: cricket's information system has reached a point where verified and unverified data circulate with identical confidence, and readers cannot tell them apart. A packet that installs its own integrity gate is admitting that the appearance of data is crafted more carefully than its provenance.

Cricket's data economy now runs through six or seven layers. A scorer writes on paper or in an app; the entry travels to a board server; from there to a stats provider, a broadcast graphics feed, a fantasy platform, a betting data feed, and now an NFT marketplace. Every handover creates a new version and deletes the old one without leaving a trace.

I have watched this chain for twenty-one years. The problem was never a shortage of data. The problem is that there is no simple way to prove which version is real. That gap is what blockchain wants to sell.

In cricket language, blockchain is easy to describe. Treat every over's entry as an envelope. Inside is a sheet; on the outside a seal, and beside the seal the impression of the previous seal with a timestamp. If someone swaps the sheet, the seal no longer matches, and the mismatch shows up across every copy at once. That is all. Less mystery, more bookkeeping.

Bitcoin's first block was mined on 3 January 2026, carrying a 50 BTC coinbase reward and a newspaper headline about bank bailouts. Ethereum arrived in 2026 with smart contracts. Neither milestone is directly relevant to cricket. What matters is one idea: a timestamped, hash-linked record that leaves a mark if altered later. Cricket's problem is precisely the absence of such records.

Layer one: the provenance of the domestic scorecard.

The National Cricket League, the Dhaka Premier Division, age-group tournaments—scoring in much of this world is still one person's solo work, with a cracked phone screen, a paper book, and time pressing down. That entry later enters a board server and then a stats site. If an over's runs change afterwards, there is no marker of where, who, or when.

The most practical cricket use of blockchain is not the fan token but hash-anchoring each over's entry, so that any later alteration leaves a visible mark. This does not make the score correct; it makes lying more expensive. Two hundred entries per match can be hashed at negligible cost, on a phone connection and a small server.

In 2026 I played in the Dhaka league for Udity Club as an opening batter and wicketkeeper. Back then the score sheet was the only truth. At the end of play, representatives of both sides signed it. The signature was a ritual of trust, not a mechanism of proof. The technology has changed; the structure of trust has not. Paper became an app, and the signature became a question nobody asks.

Layer two: identity and age.

Age verification is cricket's most sensitive data. A year up or down in an under-19 squad changes an entire career's price. Boards check birth certificates, school records, bone-age reports; at every step paper is lost, gaps open, disputes grow. The honest blockchain use here is a verified credential: without handing over the underlying document, record only the result of verification on the ledger, and use zero-knowledge proofs to confirm that a condition is met without revealing what is inside it.

The real value of blockchain in the cricket market is not disclosure but the preservation of proof—proof that a club, a board and a league can trust together even when they do not trust each other. That sentence sits on the far side of the NFT hype.

In 2026 I commentated France against Argentina from a Dhaka studio. On 30 June 2026 the score was 4-3; Mbappé, nineteen, scored twice and won a penalty. I kept returning not to tactics but to an image: a teenager sprinting past Javier Mascherano, born in 2026. I wrote that night: a teenager did not arrive in Kazan; he tore a hole in time. Age was not a statistic to me then, it was a clock. And in a game where age is the clock, the provenance of age data should be verified first, before any fan token.

Layer three: the market of feeling.

In 2026 the ICC announced a multi-year partnership with FanCraze to build digital cricket collectibles. Before and after that, platforms such as Sorare built player-card markets, and clubs issued fan tokens. This is new revenue, no doubt. My interest lies elsewhere: what do these products actually preserve?

May 2026. The Bundesliga returned after the COVID shutdown to empty stadiums. Dortmund beat Schalke 4-0 at Signal Iduna Park, a ground with a capacity of 81,365. Haaland scored, but the broadcast carried boot studs, distant shouts, and the silence of empty seats. I found myself whispering, then stopping. That night I understood: when the Yellow Wall fell silent, football heard its own heartbeat.

A match token cannot hold that silence. It holds a still image, a serial number, a certificate of ownership. Cricket's memory is not property; it is a habit of participation. Blockchain is extraordinary at proving ownership and incapable of proving participation. Most cricket-tech conversation knocks on the wrong door because it misses that distinction.

Now the uncomfortable part.

Blockchain does not stop false data; it makes false data permanent. If a scorer mistakenly records a run-out and that entry reaches the chain, it cannot be undone—only a correction can be added in a later block. Readers read the first entry; they may never read the correction. This is not a flaw of technology but a design decision. In cricket's information system, the right to correction matters more than the claim of infallibility.

The second problem is power. Most cricket chains being built are permissioned—validators are boards, leagues, or firms they appoint. Transparency rises; decentralisation becomes decoration. The question is simple: who validates the validator? If a board that struggles to manage its own age disputes becomes the sole attestor of a chain, we get the same paper errors in a new wrapper.

The third problem is economics. Small boards and domestic leagues will become data producers while large platforms package and sell the output. It is the loan-with-obligation structure applied to information: smaller institutions spend years developing half-finished assets, and the upside lands elsewhere. If Bangladesh's domestic cricket data is anchored on a foreign platform's ledger, who keeps ownership of the memory?

The fourth problem is vanity metrics. Football pretends distance covered and sprint counts measure effort, though pointless running also produces pretty numbers. Cricket data will do the same with on-chain transactions, unique wallets and mint counts. A metric that rises easily is a metric that tells you little.

Then there is medical data. Cricket injury updates now belong to communications departments; week-to-week often means the injury is not close to healed but the messaging has just begun. If player medical data moves on-chain, the question is which data moves—the full report, or the hash selected by the communications team? A ledger preserves what it is given; the rest stays outside, exactly as before.

So what is the path? For me the answer is protocol, not product. First, hash over-by-over domestic entries, but publish a reversal protocol: reason, timestamp, and the name of the approver, visible to all. Second, keep age and medical data off public chains and inside zero-knowledge credentials; the answer should be yes or no, not the document. Third, place ownership of domestic data jointly with the board and the players' association, not under a foreign marketplace's terms.

None of these three requires a billion dollars. They require a decision: do we treat data as property or as testimony? Property has owners; testimony has obligations. Cricket's problem is the absence of obligation.

In my notebook, beside that 2026 match, there is still a question mark. Nobody answered it, nobody could. If that sixteenth-over entry had sat in a timestamped hash, at least we would know who wrote what, and when. That would not have been enough—but it would have been a beginning.

The thing to watch over the next eighteen months is narrow: whether the Bangladesh Cricket Board announces a verification layer for domestic scoring data, and whether the name of the local scorer appears inside it. If yes, cricket's blockchain story moves away from NFTs and toward testimony. If no, we will get more beautiful numbers, and lose more score sheets. The stadium remembers what the scoreboard forgets—but who remembers the scoreboard?