Blockchain Gives Data Ownership, Not Definitions: The Politics of Measurement in Asian Cricket

I watch matches with the ledger open, and almost every week I stall at the same place: what is the number, actually?

Hook

Before the Asia Cup, two analysts walked into a franchise selection meeting with two different workload figures for the same fast bowler. One said the boy had bowled 142 overs in six weeks. The other said 81. Neither lied. The first had added every domestic format; the second counted only T20 and List A. On top of that, the two boards counted overs differently—bowler-overs in one database, match overs in another, and a third stripped maidens out entirely. At the end the coach asked me which number was real. I said there is no real number. There are three numbers and one dictionary. That night I wrote in the ledger: the blockchain conversation now thundering through Asian cricket should centre on definitions, not technology.

Context

The Asia Cup finished in the United Arab Emirates in September 2026, with India as champions. Six months earlier, in March 2026, India beat New Zealand in the Champions Trophy final in Dubai. The 2026 Asia Cup was staged in Sri Lanka and Pakistan under a hybrid model. In roughly thirty months, Asian cricket has passed three times through venue politics, visa politics and broadcast politics. Ahead lies the T20 World Cup 2026, hosted by India and Sri Lanka. At the 2026 Asia Cup, the ticket to an India-Pakistan match was a diplomatic object; every match's data was the private property of a handful of vendors.

Data volume has exploded inside that geography. Ball-tracking on every delivery, edge detection, stump cameras, smart balls, fielding maps—a one-day match now generates thousands of discrete data points. The IPL, PSL, BPL, LPL, ILT20 and SA20 each run their own analytics vendor, their own dashboard, their own definitions. Boards are separate, broadcasters are separate, selection committees are separate. Into this, fan tokens and NFTs have put a hand on cricket—from board-level digital collectibles to club-level token sales. Smart contracts are now ordinary talk in league offices.

Here I must be blunt, because I keep a ledger of misses and the hits already have press officers. I have not personally verified any arrangement in which an Asian cricket board runs its match data on a blockchain. What I have verified is market behaviour: technology arrives first, definitions arrive later, and without definitions technology only spreads error faster.

Core

What blockchain actually solves

A blockchain does one real job: it proves who wrote a record, when, in what order, and that nobody quietly changed it afterwards. In cricket that lands in three practical places.

Player registration and clearances. NOCs for overseas players, agent changes, league-to-league transfers—these files travel by hand, by email, by messaging app. When a dispute breaks out, three weeks vanish in searching for proof. A timestamped ledger can erase much of that argument.

Payment escrow. Complaints about late payments in domestic leagues are not new, and they recur in Bangladesh, Pakistan and Sri Lanka. A smart contract can hold match fees in escrow up front and release them only when conditions are met. Here the technology is honest, because the conditions are written down.

Chain of custody in anti-corruption investigations. A message, an audio file, an interview—who received it, when, and whether the file was altered. Here an immutable timestamp genuinely earns its place.

Blockchain here is a timestamp machine; it is not a truth machine.

What it does not solve: definition drift

From my Rangpur newsletter years I have kept one lesson: arguments about numbers are arguments about words. What counts as a dot ball when byes or leg byes are involved? How is a dropped catch attributed—to the fielder or the bowler? Does strike rate exclude no-balls? Does workload include overs bowled in practice, and light spells in the warm-up? Are the first two matches after an injury counted separately? When normalising for venue, how many seasons of average do you use—three, five, ten?

Every one of those questions gets a different answer across five Asian boards. So one bowler generates five workload figures, and each is correct inside its own board. Jasprit Bumrah, Shaheen Afridi, Taskin Ahmed, Rashid Khan, Wanindu Hasaranga—the reason two boards can disagree about each of their loads is definitional, not technical. Bumrah's load is managed at board level because the organisation has the will to manage it; that will comes from understanding a fast bowler's value, not from a dictionary.

Write a wrong definition into an immutable ledger and the error becomes permanent and authoritative. It is far more damaging than a mutable spreadsheet, because afterwards nobody asks the question again.

Latency: the fifteen-second lesson

In Russia my live xG model updated every fifteen seconds, and that summer I learned to wait—not for the number to arrive, but before trusting it. In live operations that discipline is the real skill.

Blockchain collides with it directly. On a public chain, block confirmation takes seconds to minutes depending on consensus. Cricket's decisions are not made in minutes. A captain must pick a side before the toss. When rain falls, Duckworth-Lewis-Stern shifts the target and the dressing room needs to know immediately. In that moment a provably immutable number arriving twelve seconds late is worth nothing.

In live operations, speed and immutability are in conflict; which one you sacrifice is a policy decision, not a technological one.

Sample windows and base rates

The biggest error at a tournament like the T20 World Cup is mistaking a small sample for character. A thirty-ball spell, four matches of form, one series across two venues—none of that judges a player. I believe in rolling windows, and I fix the window before the first ball, not after seeing the result.

Blockchain does not touch this problem. It can change how durable data is; it cannot change how representative data is. A figure can sit in a ledger forever and still be a permanent error if it was built on ten deliveries.

The existence of evidence and the representativeness of evidence are separate things; the first is a technology problem, the second is a statistics problem.

One data dictionary: the lesson of fourteen producers

At Euro 2026 and the Tokyo Olympics in 2026 I imposed a single dictionary on fourteen producers and built a 0-100 efficiency score so that a football press and a 100m sprint final could sit on one scale. It worked because the dictionary came before the technology, not after.

Asian cricket needs the equivalent, and it is far less glamorous than a chain: one page stating how overs are counted, in what proportion match, practice and warm-up overs enter workload, how injury-return matches are flagged, how many seasons of average normalise venue, and what the minimum sample window is.

Without a dictionary, an on-chain ledger is an expensive rubber stamp and nothing more.

Who writes the smart contract

This is where power hides. Whoever writes the smart contract decides which information counts as true and which does not. Whoever writes it becomes the effective legislator. In Asian cricket today the real power over data sits not with boards but with vendors, because they build the dashboards, the definitions and the injury indices.

Blockchain can make that vendor power permanent—unless the board writes the dictionary first.

Contrarian

The obvious question: blockchain brings transparency, so where is the problem?

The problem is that transparency and accuracy are not the same thing. A player may be registered on-chain, paid through escrow, logged in a workload ledger—and none of that makes him less likely to break down. Injuries come from load, recovery, sleep, travel, venue and luck. A ledger can record those variables; it cannot change them. A club that will not invest in injury prevention will simply get a flawless ledger predicting exactly when its players snap.

Second, fan tokens. Streaming platforms made a specific mistake during the rights bubble—buying rights with loss-making money to hold on to viewers' patience—and cricket's fan tokens are a smaller version of the same mistake: converting a supporter's emotion into one-off revenue while the long-run value of the product stays close to zero. Buying a token does not change a match result; it makes a balance sheet look better for a while.

Third, the cost of losing mutability. Cricket needs corrections—investigations, retroactive rule changes, fixing bad data. A system that declares old records can never change also closes the road to correcting error.

The job of technology is not to tell the truth; it is to make lying harder. And harder is not the same as right.

Takeaway

In the coming cycle I will watch two signals. First, whether any board publishes its data dictionary before or during the T20 World Cup 2026—one page stating how overs, workload, injury returns and venue factors are counted. Second, whether any league actually holds player payments in escrow—not an announcement, an audited account.

Whether anyone buys a token is a market question, not mine. My question is simple: if not one board prints its dictionary before the next Asia Cup, the next conversation will again be about technology, not about arithmetic.

The team does not need more data; it needs one number it can defend.