When the Scorecard Is a Suspect: Cricket's Data Integrity and Blockchain's Quiet Experiment

The Night the Scoreboard and My Notebook Disagreed

Late last season I sat through a night match at a district-grade ground a few hours out of Dhaka. The board lit up 173/6 at the close. My notebook said 173/5. I burned nearly two hours on whether that sixth dismissal was a run-out at all, because a single wicket decides net run rate, and net run rate decides who goes through.

Back home I laid four artefacts side by side: the scorer's handwritten book, the live data operator's feed, the television graphics, and a betting settlement report. Four numbers, four versions, and not one of them carried a verifiable seal. Cricket usually absorbs this because the result rarely moves. The economics no longer can. A wrongly logged wicket can shift settlement totals worth crores. That is roughly where blockchain stops being a pitch deck and starts being a plumbing question.

Who Actually Writes a Scorecard, and Who Gets Paid For It

Cricket data is never born in one place. It travels a supply chain. At the first layer sits the ground scorer, often a volunteer, sometimes a club treasurer, sometimes a retired umpire. His handwritten book is the primary document. The second layer belongs to live data operators; companies such as Sportradar, Stats Perform and Opta build ball-by-ball feeds that flow straight into broadcasters, fantasy platforms and betting apps. The third layer is the broadcaster painting graphics. The fourth is the market holding money against that feed.

In South Asia the first two layers are simultaneously the weakest and the worst paid. Below the top tier of the Dhaka Premier League, or across Bangladesh's first-class circuit, power cuts, patchy mobile data and a shortage of trained scorers create exactly the gap where records go wrong most easily. The value of those records keeps climbing anyway.

In June 2026 the Board of Control for Cricket in India sold the Indian Premier League's 2026–27 broadcast and digital rights for roughly 48,390 crore rupees, among the largest single-league media deals in sport. The International Cricket Council's India rights cycle for 2026–27 was reported around three billion US dollars. That money sits at the media layer. Beneath it, ball-by-ball data rights, fantasy data rights and live settlement feeds are bought and sold separately. When a number commands a price and carries no provenance, that is not trivia. It is counterparty risk.

I learned the shape of it in 2026, calling an ICC Trophy match between Bangladesh and Kenya from a radio box. I did not understand the money then. I understood something else: a scorecard can look immaculate while an entire over has quietly gone missing, because nobody bothered to audit the hand that wrote it.

What Blockchain Actually Answers

Blockchain is most often misunderstood as a truth machine. It is a tamper-evidence machine. A hash function turns any record into a fixed string; change one character of the source and the string collapses. Anchor a per-ball feed to a chain and any later rewrite trips immediately. A Merkle tree then does the useful work of scale, collapsing thousands of ball-level hashes into a single root so a whole quarter of data can be checked against one line.

The real question is whose chain. Permissioned ledgers such as Hyperledger Fabric let a handful of partners—boards, broadcasters, regulators—run nodes. That buys speed, privacy and control. Public chains such as Polygon or Ethereum let any party verify independently, at higher cost and lower throughput. Cricket's live experiments are running on both sides of that divide.

FanCraze announced an ICC partnership in 2026 for cricket digital collectibles on the Flow blockchain. Rario, built on Polygon, signed Cricket Australia and several franchises for its card marketplace. Cricket Stars also runs on Polygon with Jump Crypto backing. In football, FIFA+ Collect sits on Algorand and Sorare on Ethereum. Most of that list monetises fandom rather than protecting the record.

Scorecard integrity is the unglamorous version, and the one that matters. Three applications look viable to me.

First, ball-level anchoring. Every event—run, ball, umpire signal, review—gets corroborated by two or three independent collectors, then hashed into a regional ledger.

Second, player registration, transfer certificates and contract ledgers. This is where my professional scars are. In franchise cricket, importing an overseas player requires clearances that move through email, handwritten paper and occasionally a verbal promise. Players end up contracted to two leagues at once and boards discover it days before a tournament. A shared ledger of clearances, contract timestamps and disputed claims removes the ambiguity.

Third, age verification, handled carefully. Boards such as India's use the TW3 bone-age method because age suppression in domestic cricket is not rare. A verified age attestation on-chain, combined with a zero-knowledge proof, would let a board prove verification happened without publishing a medical file. Privacy and verification can coexist quietly.

This is where I return to old work. In Mymensingh, the first xG model was a lantern in a league of shadows. There were no tracking cameras, no stadium-grade video. I logged every shot by hand and built the simplest repeatable rule I could defend. District cricket needs that same lantern. There is no technology budget, only a phone and unreliable connectivity. A small permissioned ledger run collectively, at low cost, does the job of the lantern.

The 2026 hiatus taught me something that has become oddly relevant. Empty stadiums taught me that silence can be a data source. A Brazilian striker carried 0.78 xG per 90 in behind-closed-doors matches, a headline number. Once the context model absorbed it, his distance covered had dropped 18 percent and his pressing figures against weak defences were inflated. Four matches, no video, no context tags. I recommended against the deal and the club walked away. He scored twice in fourteen appearances elsewhere. Missing records are still records, and silence does not lie. It simply stays silent.

Where Blockchain Becomes the Suspect

A hash on a chain promises one thing: the record has not changed since it was written. It does not promise the record was right when written. A model without context is just a calculator wearing a scout. Immutability produces the same trap at scale: a permanently wrong document that can also prove it has always been that wrong.

Legal friction follows. India's Digital Personal Data Protection Act of 2026 grants a right to erasure. Public chains are, by design, hostile to erasure. Put injury histories, medical records or anti-corruption testimony on an immutable public ledger and protection collides with justice. Permissioned ledgers soften that collision and invite a different charge: five institutions running a shared ledger is a shared database with extra code.

My larger objection is elsewhere. If blockchain makes live data faster, verifiable and provable, the greatest beneficiary is the sector holding money against it. Settlement within a second of a delivery is not transparency; it is market acceleration, and faster markets make misconduct faster too. A result that moves slowly leaves room for detection. A market that moves instantly consumes that room without a trace.

The ethical question drifts to young players. Perfect, permanent age verification does not only close the fraud route. It freezes a fifteen-year-old as a proven fifteen-year-old, and clubs holding that proof become more confident loading senior workloads onto him. A body still developing inside senior rhythms pays interest later. A chain can verify an age. It cannot manage a workload.

I am not a purist opponent. I once blocked a false-positive transfer because one number refused to fit the story. The transfer market, football or cricket, is a rumour engine; I only turn gears with data. If blockchain adds another gear, it can have a place. I simply refuse to let the vocabulary paper over the mechanism.

Forward Signal

Cricket's successful ledger experiment will not begin at a national board. It will begin inside a domestic league, where the gaps in the record are widest and its price is least understood.

My proposal has three layers. Capture: two or more independent witnesses, plus cheap smartphone video wherever possible. Attestation: separate signatures from the board, an independent auditor and the broadcaster. Anchoring: the only layer normally called blockchain, holding nothing but hashes, batched annually. Technology at the far end, cost at its lowest, accountability kept human.

My forecast: within two tournament cycles, at least one South Asian domestic league will pilot ball-by-ball feed anchoring. I put that probability at 60 to 70 percent, because both regulators and rights holders are now pushing provenance demands downstream. The handwritten scorecard will not vanish. It will simply carry a seal beside it, proving who wrote what, and when. The open question is this. In a sport where the number is the only truth, who should own proof of the number: the hand that writes it, or the hand counting the money?