Empty Cells Testify Too: Cricket's Data Integrity and the On-Chain Verification Question

At the Sher-e-Bangla press box I pulled the scorer's ledger toward me. Everything tallied up to the seventeenth over, then one column went entirely blank. Ball-tracking never reached that match — only runs, wickets and extras, written by hand. The stands were moving; the paper was silent. A colleague beside me asked, “There is no data. So what is there to write?”

The question is easy. The answer is not. We treat cricket as a game of numbers, yet the most honest form a number can take is its absence. An empty cell is itself a finding. That evening I did not watch the match; I watched who was manufacturing numbers, and where those numbers had no witness. The conversation now gathering pace around blockchain in cricket sits on precisely the same question: who verifies the number?

Cricket's data layer was built in stages. The Duckworth-Lewis method was first applied at the 2026 World Cup, pulling rain-shortened results inside the arithmetic. Hawk-Eye ball-tracking entered Test broadcast in England in 2026, and the Decision Review System was first used in the 2026 Sri Lanka-India series. At every step, decision-making authority drifted from the human to the system.

Authority moved. The verification architecture did not. A franchise T20 match generates dozens of data points per delivery — pace, spin revolution, pitch map, the shadow of field placement. A domestic four-day game in the same country may generate one scorer, one ledger and one phone. Both sets of numbers are written in the same format; the difference in witnesses behind them is vast.

That asymmetry is budgetary as much as technological. Where broadcast money exists, tracking exists; where it does not, there is a handwritten sheet. Cricket's global data vault is therefore dense around a handful of wealthy leagues and thin everywhere else. Analysis built on that vault is more confident about players from rich leagues and less confident about players from the margins — because we have less information, not less talent.

Bangladesh sharpens the point. Many Dhaka Premier League and National Cricket League matches carry no ball-by-ball tracking; scoring happens by hand and is uploaded later. Player evaluation therefore rests on a handful of columns. A large share of national selection decisions is built on exactly that narrow base.

Blockchain does not establish truth here; it establishes accountability. Hash a scoring entry at the moment of entry and write it to a ledger, and you can later prove the number was not altered. You get an immutable timeline of who wrote what, and when. In journalism's language, it preserves the witness's address, not the witness's honesty.

The distinction matters, because cricket's most visible use of blockchain remains collectible cards, fan tokens and digital memorabilia — entertainment product. The real crisis is infrastructural. If a full season of ball-by-ball logs from a domestic tournament were public and verifiable, selector, coach and journalist could look at the same number. Today they look at three different ledgers.

The ICC Anti-Corruption Unit's work connects here too. Match-fixing investigations hinge on evidence, and the credibility of that evidence depends on preserving its chain. A verifiable data log makes investigation easier; it does not replace investigation.

I opened the spreadsheet, and the stadium exhaled. During the empty-stadium matches of 2026 the sensation was sharper still — the empty stadiums made every data point echo, because the number was the only witness left. That experience taught me a habit: before making any metric claim, ask who collected the number, who verified it, and who wrote it down.

The old rule of data journalism applies. The urge to fill a blank cell is the biggest trap. In statistical language, null and zero are not the same thing; “nought runs” and “runs unknown” are different realities. Many dashboards erase the distinction, so viewers assume the picture is complete while some cells sit silently empty. This may be the most valuable thing on-chain verification can do — attach a timestamp and an identity behind every cell.

Still, there is an uncomfortable truth. More data has not made cricket fairer; it has moved decision-making power from the umpire's shoulder to the system's server. The “umpire's call” margin in DRS is an admission of that reality — some uncertainty is deliberately left with the human judge, because tracking is not perfect either. A system that admits the limits of its own error is trustworthy; a system that claims precision is dangerous.

That is where my deepest scepticism about blockchain lives. An immutable wrong number is far worse than a correctable wrong number. If a faulty scoring entry enters the chain, it does not merely stay wrong — it becomes wrong with proof attached. Handwritten ledgers in cricket's data history have been corrected later. Where is the space for that correction on an immutable ledger?

One comparison, offered once and flagged as such — from football. Mbappe ran 4-3 into history, and the numbers finally blinked. That night's memory was assembled from eyewitnesses, broadcast and later-verified data: three separate layers meeting. Blockchain does not merge those layers; it only shows you the stitching between them.

Rajshahi taught me silence; the World Cup taught me signal. My interest now lies not in token prices but in one question — which cricket board will be first to publish a data-provenance log for its own domestic season? The day a selector and a journalist look at the same hashed scoresheet and see the same number, cricket's data argument will move somewhere else entirely.