The Ball-by-Ball Ledger: Who Guards Cricket's Data, and Who Sells It

September 2026, the Edgbaston press box. The rain stopped ten minutes ago; the ground staff come off the covers with mud to their knees. The scout to my right has a ball-by-ball feed open on his laptop. The ball has not yet pitched. Line, length, seam angle, release angle, speed out of the hand are already on the screen. Nobody in the stand behind me has stood up yet. Ball, then sound. Sound, then roar. Screen, then ground.

Those three seconds. In cricket today the most expensive object is neither bat nor ball; it is the size of that gap. Whoever receives it first knows first; whoever knows first prices it first. And the pricing happens far outside the ground, in a control room cricket has never visited.

In a transfer window the release clause and the wage bill usually tell you the real story. This year the clause that matters is the one that does not exist — a data-rights paragraph that should be sitting in a domestic cricketer's contract.

In 2026 I was in a Dhaka radio studio commentating on Bangladesh against Kenya in the ICC Trophy. Data then meant a scorebook: runs, wickets, overs, who faced how many balls. Twenty years on, a single delivery yields more than forty separate measurements — swing, seam rotation, backlift height, the fielder's starting position, and a modelled run value for that one ball. Cricket now writes a small database every six deliveries.

So the question arrives, and it is not a naive one. Whose database is it? The venue's camera owner? The rights-holder's server? The board with the central tender? Or the twenty-year-old whose elbow angle gave birth to the number?

The answer is settled in three places. First, the board's data-rights tender; India, Australia and England all sell ball-by-ball feeds on multi-year deals, and that money is now among cricket's most stable revenue. Second, the broadcast contract, where the data feed is bundled in almost free. Third, and least comfortably, the in-play betting market, where knowing a delivery's outcome one second early means pricing it one comma early.

The industry calls this data-driven cricket. I do not think the data is the problem. The problem is that the man standing on the grass generating the value is almost absent from the accounting.

Blockchain entered this picture through the wrong door. First fan tokens, then NFTs, then the festival. In 2026 an Indian cricket-NFT platform raised 120 million dollars, partnered with Cricket Australia, sold cards of leading IPL names. Two seasons later those cards were worth roughly nothing, and the festival never once touched the question of data ownership, because a token was packaging for fandom, not a transfer of title.

Meanwhile the blockchain use that will never trend is arguably the only one that works.

In cricket, blockchain means a ledger, not a coin — a record in which who touched which data, and when, cannot be quietly deleted the next morning.

There is a specific reason this matters. In August 2026, spot-fixing around the England-Pakistan Test at Lord's was exposed. Investigators chased phone records, bank statements, a witness's memory. Salman Butt, Mohammad Asif and Mohammad Amir were banned, and in 2026 a London criminal trial convicted them. Almost everything the investigators held was circumstantial. Somebody knew. But who knew first, and how many seconds first, was written down nowhere in a form that could not be altered.

Now imagine the ball-by-ball feed, the image-rights approvals, and the declarations filed with the anti-corruption unit all timestamped on a tamper-evident ledger. Investigations change speed, because the evidence no longer has to be found; it is already on the table. This is not romantic technology. It is as dull as a bank's ledger. That is precisely why it works.

The second use is clearer and more uncomfortable. Late match fees in domestic cricket are the rule, not the exception. Bangladesh, Sri Lanka, the West Indies — a 22-year-old's last two match payments routinely arrive six to nine months late. A smart contract cannot print money here; it cannot close a budget hole. What it can do is hold contract money in escrow and release it on a fixed date, automatically. Technology does not create money. It removes the excuses for withholding it.

Cricketers generate the value of the data; bookmakers collect the price — and that gap is the quietest fact in the modern cricket economy.

We write poetry about cricket's purity very easily, imagining the pre-data era as innocent, plain, full only of memory. The truth is less pretty. In 2026, in that Dhaka studio, I heard the producer tell someone on the phone that a particular batsman would be kept quiet today. The information came from nobody official; it came from an unverified source. Today the same information arrives from a purchased feed and is sprayed with the word analytics.

The product changed; the structure of power did not. Those who owned the ground once held the profit; those who own the server hold it now. In between sits a twenty-year-old left-arm spinner with six first-class matches, whose workload data is sold as part of a bundle, and whose contract contains no data-rights clause at all, because nobody told him one should exist.

In 2026, during the shutdown, I stood outside an empty Anfield and learned that absence can be a character. There is an absence in this story too — the cricketer who is the raw input of the data product, but who does not own the product.

This is where the blockchain evangelists get pricked. They say the technology decentralises power. But decentralisation in cricket has only just begun, and it came from organising, not from software — West Indies players demanded ownership long before any chain existed. A ledger can force a board to be transparent if a players' association is willing to push the door. The ledger does not push the door itself.

Wembley did not lose its ghosts; we simply stopped listening for them. Cricket's integrity reports read the same way — the ghosts sit inside the documents while we stare at the numbers in the table. The question was never whether the record was falsified. The question was who saw it first.

One imbalance still has to be admitted. In 2026 Shakib Al Hasan was found to have failed to report two approaches, and he was banned. The easy moral is that a senior international dodged his responsibility. The uncomfortable part is why the approaches reached his phone at all: because many people can learn a single delivery's outcome early, and the price of that word early is high enough to make a young man in a dressing room hesitate. Shakib's responsibility is clear and the sanction fair. He is not the only address for the blame.

In the 2027 calendar I will be watching two things. First, the next central data-rights tender from the ICC and the boards — if a players' representative or a players' association signs it formally for the first time, the argument has moved. Second, the first standard domestic contract anywhere to carry an escrow clause and a data-rights clause: a small paragraph, but the first real evidence of noise about a gap twenty years in the making.

That evening, fifteen minutes after the Edgbaston press box emptied, I was among the late leavers. A laptop still glowed on a desk in front of me, left behind. The last ball's data sat frozen on it — speed, length, swing, field map. The ball had stopped long ago. The number had not. It had gone to a server, been bundled somewhere, priced somewhere, and somebody had paid for it.

Some matches end; others keep ticking in the quiet metronome of memory. And some numbers, belonging to no one, stay for a very long time.