Cricket's Data Chain: Blockchain, Betting Feeds and the Lesson of an Empty Spreadsheet

Hook: The Spreadsheet With No Numbers

On a Monday morning in September, in a Brisbane newsroom, I opened a match file. The grid was flawless—every row, every column in place. Yet every cell was empty. No runs for an over, no ball-by-ball tracking, no strike rate, no field-placement map. The frame of an analysis was built; inside it was a quiet zero.

What I understood that morning was not about a single match. It was about cricket's data supply chain. When a ball crosses the boundary rope, the event stops being just an event—it becomes a number, then a feed, then a betting market, then a green or red arrow on your phone. At every link of that journey, someone gains and someone counts the cost.

The numbers were never the story; they were the trailhead. The real story is where the numbers come from, who verifies them, and who takes the risk of trusting them.

Context: Cricket's Invisible Supply Chain

Cricket is now the most data-dense sport on earth. Ball speed, spin revolutions, bat swing, fielder position—all measured. Hawk-Eye, UltraEdge, Snicko—the names are familiar to fans. What is less known is that this data flows through a narrow channel owned by very few hands.

The ICC and national boards hold the rights to match data. They license it to collection companies. Those companies sell feeds to broadcasters, fantasy platforms and betting operators. At every joint of this chain, money changes hands and an assumption of trust hides inside.

In 26 years in this industry I have seen the chain from both sides. In 2026, sitting in Brisbane, I live-tweeted a data thread on the Sydney FC versus Melbourne Victory Grand Final—Sydney's 1.31 xG to Victory's 0.84, PPDA of 7.9 versus 12.4, 14 high turnovers. The thread reached 280,000 impressions. What I did not understand then was that nobody asked where those numbers came from.

In the 2026 Russia World Cup I remotely modelled the France–Croatia final. France 2.1 xG, Croatia 1.8, but six shots on target to Croatia's three. Croatia had three extra-time matches, 1,200+ minutes played. I hosted a panel in Brisbane with Croatian and French fans. One supporter asked me: who verified these numbers of yours?

That question stayed lodged in my head. I had started with data, but cricket pulled me back to the terrace—where the fan sits, and where there is no way to verify.

Core Analysis: From Ball to Blockchain—The Data Journey

Walk the chain step by step and you see where integrity breaks. First, collection. Cameras on stadium roofs, microphones in the stumps, sensors inside the ball. The first risk is here: if a camera drops a frame, that ball's speed is wrong forever.

Second, aggregation. Raw signals arrive from a dozen sources. Someone assembles them into one grid, computes strike rates and economies. Here the data changes hands—an operator, a piece of software, a deadline. Mistakes enter here.

Third, distribution. The finished feed travels to broadcast graphics, fantasy apps, betting markets. This is where the biggest asymmetry lives: the same feed arrives in one place in 1.5 seconds and another in three. That gap of seconds creates a multi-million-dollar edge in betting markets.

Fourth, consumption and betting. A fan sees a number on a screen and assumes it is true. He does not know how many hands it passed through or who touched it last.

The job of data is to ask why, not just how much. This is where the blockchain question becomes relevant. A blockchain is an immutable ledger—once written, it cannot be erased. For cricket data, that means: who created each ball's data, when, and who altered it—all recorded.

Imagine an over showing two different run totals in two places. A blockchain ledger tells you who wrote first and who changed it later. This transparency is not new to cricket—we already see ball-tracking predictions in DRS, where bounce and impact are forecast. Blockchain turns that forecast into a verifiable history.

In Asian cricket the question is sharper. The IPL, PSL, Asia Cup—these tournaments are enormous data commerce. Boards, broadcasters, sponsors all depend on this data. Yet the verification framework is centralised, on paper. A fan can never verify the maths behind the scorecard himself.

From years of watching matches, I can say the fan's deepest fear is not losing a match—it is the suspicion that the match was not real. A fixing scandal does not just ruin one game; it ruins trust in a whole league. Blockchain could be a tool to restore that trust, because manipulation leaves a trace.

But here comes cricket's community-cost accounting. Installing a blockchain-based data system costs money. Who bears that cost? Smaller boards? Associate nations? Or does the big betting operator pay, and in return take even more control over the data?

In 2026, during the COVID-emptied stadiums, I analysed the A-League restart. Nobody expected home advantage to fall so far without crowds—home teams won 38% of restart matches versus 52% pre-pandemic. I learned then that data is never just numbers; human presence or absence hides behind it.

The same holds for the data chain. When a feed silently breaks, the loss is felt by the weakest person—the fan with a small bet, or the journalist at a small outlet. Big operators cover it with backups; the small ones get caught.

In 2026 I worked on penalty culture at Euro 2026 and Tokyo 2026—Italy 1.14 xG, England 0.94, yet Italy converted 3 of 4 penalties and England 2 of 5. The numbers said England were close; the nerves said otherwise. Read data without the human story and the picture is incomplete.

At the 2026 Qatar World Cup I modelled the Argentina–France final—Argentina 2.19 xG, France 2.31, shots 20 to 10, then a 4-2 shootout. I also tracked mid-season fatigue and migrant-worker stories, because both those who build stadiums and those who watch them deserve a place in the data story.

Contrarian Angle: Blockchain Is No Magic

Now to the part I believe most. Blockchain is not the solution to cricket's integrity problem; it is only a tool. Technology never makes honest people; it only leaves a trace of dishonesty.

Second, correlation is not causation. Concluding that corruption will fall simply because a blockchain system exists is a mistake. The real question is: who runs the ledger? Who decides what gets written? If that power stays with the same few large bodies, the technology changes but the balance of power does not.

Third, feed speed. Blockchain takes time to confirm transactions. In live ball-by-ball data, seconds matter. So writing every ball to a chain is unrealistic. Instead, a verifiable summary—a hash of the key numbers—could be written at the end of a match or a day.

Fourth, who gains and who pays. The betting market gains most, because verifiable data means less uncertainty, less uncertainty means more confidence, and more confidence means more money. But will that verification benefit reach the ordinary fan, or only the big operators? That is the real question.

My deepest worry lies here. Live data flowing straight into betting companies is the darkest side of sport's datafication. While a fan watches an over in the stands, every ball of that over has already reached an algorithm and turned into an odds line. Blockchain can make that flow transparent, but it cannot stop it.

Takeaway: A Signal for the Next Innings

My empty spreadsheet taught me something no interface or live feed could—silent failure is the most dangerous failure. When information is blank and nobody notices, decisions go the wrong way.

Next season I am starting a new habit: at the start of every analysis, verify the source ledger of the data, and write beside every number who supplied it. Blockchain or not, the question stays the same—who wrote this number, and who will own it?