The No-Ball Written on a Chain: When the Dead-Ball Ledger Goes On-Chain

The 19th over at Mirpur. In my hand, a field map sketched before the first ball: two men on the off-side boundary for the wide yorker, one deep at long-on, one up at square leg. I had written the date at the top of the column before the bowler began his run-up. What followed did not fit neatly into any box of my ledger: front foot over the line, the umpire's arm up, free hit, and the next ball straight into the stands. Six.

The crowd went quiet. Twenty-seven thousand people falling silent is a sound I have learned to hear.

That silence stayed with me. The same delivery was recorded on more than a thousand phones that evening, yet there is no single, publicly verifiable place that holds the answer to three simple questions: which ball of which over it was, who wrote it down, and whether that record could later be changed. Scorebooks are edited. Broadcast overlays differ. Screenshots vanish. And this dead-ball arithmetic is exactly what match results, net run rates and franchise bonuses rest upon.

I spent thirty-three years in broadcasting booths before moving into sports science research as a second career. Every match report I file begins with a hand-drawn diagram and a ledger. When I wrote about Antonio Conte's Chelsea 3-4-3 in 2026, I discovered that a diagram does not merely explain a game; it opens the writer. Now it is time to place a second ledger beside the first — one written not on paper but on a chain.

The dead-ball arithmetic nobody owns

Cricket's statistical architecture is scorebook-centric. An umpire signals, a scorer writes, a broadcaster buys the feed, and a handful of commercial data firms process it and sell it onward. In that chain, a no-ball, a wide, an umpire's call under DRS, all remain inside a centralised record with no ordinary route to verification for the spectator.

Bangladesh played its first Test match against India at the Bangabandhu National Stadium in Dhaka on 10 November 2026. From that day to this, the verdict on every dead ball has effectively been locked inside one person's handwriting or one vendor's software. I have sat in broadcast studios on many nights and watched two productions display different speeds for the same delivery, with no way for the viewer to know which one was true.

This is where the blockchain proposal enters, and it is far more an engineering question than a crypto enthusiasm. A distributed ledger seals every entry with a timestamp and a cryptographic hash; no single party can erase or quietly rewrite it. Record a delivery once — bowler, over, ball number, umpire's signal, free-hit outcome — and it becomes a record nobody can silently correct later.

A scorebook does not tell the truth; a scorebook is a document of power. An on-chain ledger distributes ownership of that document — and ownership is the real question here.

Three areas where cricket is already prepared

Opening my ledger, I tried to imagine what the dead-ball entries of recent franchise seasons would look like if they sat on-chain. Three layers emerge clearly.

The first is event integrity. How many balls preceded a free hit, how many legal deliveries remain in the over, whether a bowler's quota is exhausted — get any of those wrong and the fate of a match tilts. A smart contract can encode those rules: each legal delivery sits on the ledger like a meter reading, and the free hit attaches automatically to the following ball. Under DRS, an append-only trail would appear — which angle, which frame, who decided, in how many seconds. Today we see eight seconds of that on television and the rest is lost.

The second layer is contracts and money. Many franchise deals carry appearance bonuses, match fees and performance-linked payments. Those payments move through bank transfers, sometimes months late. A smart contract releases funds the moment conditions are met — no intermediary, no "processing" excuse. In Bangladesh's domestic league, where questions about payments to second-tier players recur, a verifiable account has real value.

The third layer is fan tokens, and here my scepticism is sharpest. While watching all 64 matches of the 2026 World Cup in Russia, I built my set-piece ledger: roughly 43 percent of the tournament's 169 goals arrived from dead balls, and I indexed every goal by origin. Fan tokens sell the same aesthetic — "you are a part-owner of the club." Yet the ledger shows that where the broadcast revenue of women's leagues remains a small fraction of the men's game, tokenisation is simply a new channel moving money from supporters' pockets into club budgets. Partnership arrives wrapped in CSR language, never at the table where actual revenue is divided.

Injury timelines: how honest can an on-chain record be

My second research field is injury and return. One habit is close to universal: "week-to-week" usually means the injury is nowhere near healed, and the wording came from a PR office. The true measure of a fast bowler's hamstring sits in a medical report; the public receives a sentence without a date.

An on-chain record raises an uncomfortable question. If scans, rehabilitation milestones and return-to-bowling load approvals were stored in sequence, the gap between "nearly fit" and "actually fit" would become public. The question is who owns that data. The club? The player? The board? Blockchain is not neutral here — the table on which something is written belongs to whoever writes it.

Technology locks a truth in place, but it does not decide who writes the truth. That is politics.

The gaps a chain cannot fill

I spent a long time looking for arguments in favour of the chain, and then my own diagram stopped me.

The first problem is immutable error. The virtue of a blockchain is that records do not change. But in cricket, wrong decisions do change. Had the umpire at Mirpur missed that no-ball, the delivery would have been sealed as a legal ball — forever. An immutable record legitimises a wrong call rather than correcting it. The umpire's call protocol is proof of this: cricket has already conceded that keeping a gap between the ball's actual path and the decision is the better arrangement.

The second problem is cost and access. Running an on-chain record requires nodes, electricity, networks. Small boards, age-group sides, district clubs — who pays? At domestic level in Bangladesh, where a scoring computer is not always available, putting a chain in place means buying another centralised service, and the club carries the monthly bill.

The third problem is the hush of the stands. My ledger carries three kinds of entries: balls, runs, and noise. At Mirpur in the death overs, a decibel meter never returns the same figure twice — the silence before the free hit, then the explosion. That silence tells you how much the bowler's hand shook. That data will never sit on a chain, because its owner is a spectator, not a meter.

The fourth problem is attribution. Who makes a dead-ball goal? The finisher, or the person who draws the routine? Since Russia 2026 my habit has changed: when a goal comes from a free kick, I write down the set-piece coach's name first. An on-chain ledger awards permanent signature to the finisher, not the routine designer — unless the data model insists otherwise.

The signals I am watching

Next season I will watch two fronts. First, whether bilateral broadcast deals introduce new clauses on sub-licensing dead-ball data — because data ownership is the first chain. Second, whether franchise league fan-token announcements deliver payment transparency or merely branded keychains.

In my diagram, tomorrow's field will look the same: wide yorker, deep square, long-on. Only one new box joins it — a hash beside the ball number. And one question will remain: who writes that hash, and if someone gets it wrong, to whom do they apologise?