The Analysis That Had No Data: Cricket's Data Trust, the Betting Market, and the Limits of Blockchain

I turned the first page of the report and stopped. Eight sections, eight frameworks, tables drawn with care — and in every cell the same sentence returning: “insufficient information, cannot assess.” No team, no player, no ground, no date. The document in front of me was not about cricket; it was about cricket analysis. And that is exactly where its weight sits. The analyst who, with nothing in hand, can still fill nine pages is the most dangerous person in this game. What this report did when it reached that trap — it stopped, and admitted it did not know — says something about a quiet crisis in cricket journalism.

The biggest change in modern cricket did not happen inside the ground; it happened between the ground and the screen. Pause on how many numbers a single delivery now generates: ball speed, line-and-length coordinates, the batter's footwork, the angle of a cover drive, the keeper's reaction time. The tracking systems of the ICC and the major leagues generate hundreds of thousands of data points per match, and in a Test that runs into the millions. One part of that hoard never reaches broadcast, one part lives on team analysts' dashboards, and one part streams silently into the betting market. The T20 leagues have turned this data into a product. Wagon wheels per over, matchup matrices, field maps — broadcasters, fantasy platforms and betting markets all feed on the same raw material. Sydney taught me the touchline now lives inside a screen. The darkest corner of that screen is the pipeline carrying live data straight toward betting companies. Where information is hidden, the market is blind; where information reaches someone first, the match is still running while the result is already clear to them. To block that pipeline, both football and cricket now invoke blockchain. The idea is simple: if every event of a match is written into a ledger no one can later alter, the room for fraud shrinks.

Here is where the real lesson hides. Blockchain can make information immutable, but it cannot make it true. An immutable ledger guarantees only that what was written cannot be erased — not that what was written was ever read. And analysis begins precisely there. The empty report that reached us carried one simple principle: where a cell has no information, no guess may be placed in it. In cricket analysis this is the hardest discipline of all, because an empty cell always screams to be filled.

Technology itself left an example of that discipline. The Decision Review System came to cricket on exactly this reasoning — not the eye's guess, but measured evidence from ball-tracking and UltraEdge. Years on, the argument has not quietened. When the camera angle shifts, when the projection line slides a fraction, the boundary between “out” and “not out” begins to tremble. The curious thing is that the finer the evidence became, the greater our unease grew. The problem is not a lack of information but the limits of information. The analyst's real job in this game was never to answer everything; it was to mark honestly which questions remain unanswered.

A reckoning from my own life comes back. In 2026, at fifty-three, I left a secure TV panel in Sydney to start an independent tactical newsletter. The first paid piece was on Sydney FC's 4-2-3-1 press in the 2026 A-League grand final — 3,200 words, fourteen annotated diagrams. Subscribers grew from zero to 4,700 in six months. What I never forgot is that I wrote it for “the coach who watches alone,” not for the general viewer. Back then I left space beside every diagram, because for some overs I did not myself know the explanation. Those empty spaces were my most honest asset.

I left the coaching box, but the box still frames what I see. The habit I carried out of it was a single sentence — “I am not certain.” In 2026, in a pre-World Cup friendly, we were 0-2 down at halftime. I argued for a switch to 3-4-2-1, the head coach overruled it, we lost 0-3. That night I resigned, and I kept the tactical sheet with 27 arrows in my wallet. Why? That sheet was my empty cell — where I kept measuring the evidence of my own mistake.

There are two kinds of cricket analysts. One is ashamed to see an empty cell, so he fills them all — with guesswork, averages, received wisdom. The other stops at an empty cell and writes “not known.” The first is instantly more popular, because his writing looks tidy, every question has an answer, the reader leaves reassured. The second is uncomfortable, because he teaches the reader to live with uncertainty. History says only the second endures.

Picture a T20 innings. In the seventeenth over a spinner is bowling, his economy 7.2 — neither weak nor extraordinary. Does the captain remove him? Plain data says this over belongs to a seamer, because the batter is left-handed and the boundary is short. But the data no one reads is this spinner's variation against the slog-sweep in the seventeenth over, or that batter's habit of playing toward the boundary. The scrutiny poured on an all-rounder like Shakib Al Hasan is mostly of this second layer — the part no scorecard shows. The right decision comes at the intersection of the two datasets, not by trusting one. The analyst who comments on economy alone fills one cell and leaves another empty — and that empty cell is what explodes in the match.

And in one place this data culture does its worst damage — youth development. Elite academies now select boys and girls by the number, yet fewer than ten percent of academies give their young players a genuine path to the first team. A number judges a sixteen-year-old bowler's potential in an instant, even though his line and length are not yet formed. The greed for a filled cell does its greatest harm here, because one guess can stop a teenager's career.

Now the counter-argument. The common belief is that more data improves analysis, and that an immutable ledger like blockchain would reduce both fraud and uncertainty. I do not fully accept it. The problem is not a lack of information; the problem is the greed for a filled cell. A match's worst decisions happen in the moments when the analyst holds plenty of information — so he errs with confidence. Yet the game turns in the nine seconds nobody rehearsed — a bowler's one-second hesitation, a fielder's half-step, a captain's delayed signal. No data exists in advance for those moments, and blockchain cannot change that. Technology tells us what happened; the match is decided by what could have happened.

The betting question is harder still. If the same live data is stored in an immutable ledger on one side and streams straight to a betting company's servers on the other, transparency and exploitation stand on two banks of the same river. An immutable ledger can bring betting under accountability, and it can also make that betting more efficient. Technology never says on its own whose interest it serves.

So the next time you read — or write — an analysis, ask one question. Is that empty cell truly empty, or has someone placed a story in it to tidy things up? I still keep the sheet with 27 arrows in my wallet. Because the analyst who remembers his own empty cells is the one who may one day recognise that unfamiliar nine seconds of a match — the one no one had written down in advance.