The Ledger That Cannot Be Erased: Ball-by-Ball Cricket Data, Blockchain, and the Question of Ownership

It was nearly two in the morning in March 2026. The door was shut in my room in Barishal, an old laptop on the table, a hand-ruled notebook beside it, and a single-camera stream flickering on the screen. When the match ended, the broadcaster's scorecard said that bowler had conceded 34 runs. My notebook said 31. A three-run gap, and the cause was not arithmetic. Their scorer had counted three leg-byes separately; on my sheet those had gone into the byes column. One match, two numbers, neither of them a lie. Two different definitions.

What I understood that night has followed me for nine years since: the problem is not calculation, it is custody. On the path from a delivery to a number, who writes the first entry, and who can audit it afterwards?

I started with a pencil, because the numbers were speaking too softly.

After years of working with ball-by-ball cricket data, I have landed somewhere strange. We now have charts, heat maps, wagon wheels, xG, PPDA, fielding maps — all of it. And yet the most basic question in cricket still hangs in the air: whose is the first entry for a delivery, and would we know if it were changed later? That question is what finally pulled me toward blockchain. It pulled me there because the distinction between what a chain can actually do and what it cannot has rarely been written clearly in cricket journalism.

In the 2026-18 season, taking a junior post at a new-media desk in Dhaka, I was handed the least glamorous beat on the roster: the Bangladesh Premier League. Working nights from Barishal, charting from single-camera streams, I logged all 132 matches by hand and 1,187 shots on a second-hand laptop. The finding nobody ordered was the one I value most: champions Abahani Limited Dhaka scored 41 league goals from 34.6 xG, and 11 of those 41 goals came from set pieces.

The piece ran at 900 words and was read 40,000 times. Not one of those 40,000 readers asked for the notebook. Nobody asked how I had derived that 34.6 xG, which definitions I had used, how I had corrected myself when I got it wrong. That is the real crisis of data journalism: everyone reads the result, nobody reads the method.

The next year, Russia 2026. I went with a small outlet's press pass, no camera crew, just a notebook and a pen. Sitting in the stands, I charted all seven of Croatia's matches by hand. Three hours after the final I published 4,000 words in which one number was unambiguous: Croatia's PPDA was 9.1 in the group stage; after the 70th minute of knockout matches it drifted to 13.4, and in that window their xG conceded roughly doubled.

In Croatia, every pass became a line I could not erase.

Then came 2026. The outlet folded, I moved back to the family house in Barishal at twenty-nine. The games had stopped, but I had not. From May 2026 I charted 81 Bundesliga matches played behind closed doors. The result was startling: home teams won 33% of them against a five-season baseline of 43%, and home-favouring refereeing decisions fell by 12%. By August my free newsletter had 900 subscribers; by December, 6,000.

When the games stopped, the silence became the largest dataset I ever faced.

Those notebooks still sit in a steel trunk in Barishal. They are a ledger — sequential, timestamped, with corrections initialled in the margin. The problem is that nobody else on earth can audit that ledger. If I say so, it is so; if not, it is not. That is the central weakness of cricket's data economy, and it is where the blockchain question becomes urgent.

What is a ledger, really? A computer ledger does three things. Entries are appended in order, so nobody can slip a page into the middle. Every entry is signed with a time. And every entry is bound to the previous one by a mathematical hash, so altering an earlier line becomes visible immediately. A paper scorebook is already a chain in spirit — written in sequence, corrected by a struck-through line and an initial. The difference is one thing: paper allows erasure, a hash chain does not.

That difference deserves sitting with. The ability to erase is not only a weakness; it is also an advantage. I will come back to it.

What blockchain establishes in cricket is provenance. It cannot be loaded with the burden of establishing truth. Conflate the two and the whole conversation becomes meaningless.

Look at the actual production chain of ball-by-ball data. A delivery happens. A charterer sits behind a tablet and types it. A 4G connection uploads it. It enters a cloud database, and from there it flows into a broadcaster's graphic, a scout's report, a fantasy app, a betting model. Along that entire chain there is exactly one place where a human sits: behind the tablet. Everywhere else the number is only copied. That is why one bad entry spreads to seven hundred places in seven days and nobody knows where it came from.

Suppose two broadcasters cover the same domestic league match in Bangladesh and their logs differ by four runs. Who is right? Normally that is settled by whose feed we bought — by power, not by truth. If every delivery entry carried the charterer's digital signature and a timestamp, and any later correction appended a new, visible block to the chain, the question changes. It stops being whose feed and becomes whose definition sheet.

The second application, in anti-corruption work, is more direct. Imagine an integrity unit notices eight consecutive dot balls in the 17th over. In normal circumstances that pattern carries no evidential weight, because the bowler can simply say the next day that he could not hold his line. What an investigation needs first is a log nobody could quietly rewrite. In a spot-fixing case, the timestamp is the evidence. A paper notebook can be dated later; a hash chain cannot.

The third application is the most usable for Bangladesh's franchise system: performance-linked contracts. Match fees, bonuses, injury cover — today these run on trust and follow-up phone calls. A smart contract whose trigger comes from a signed match record could remove much of the dispute. But there is a condition nobody writes down: the software that feeds the match result into the contract is still written and operated by humans. Where there are humans, there will be errors.

I followed the transfer market until I found the invoice hiding inside the rumor. Much of the mountain of rumor around manager and agent fees in cricket's auction market is simply the result of not having a paper trail. An auditable payment trail shrinks the space for rumor and makes the player's share visible.

The fourth application is the least interesting and the most heavily sold: fan tokens, ticketing, digital memorabilia. The technology works here, and so does the economics, but it adds little to our understanding of cricket. What it does add is a new kind of fan-finance relationship whose beneficiaries are usually the club and the platform, not the supporter.

While writing all this, I have to remember that the numbers I love most inside cricket have almost nothing to do with blockchain. Dot-ball pressure, the respiration of a partnership, the heart rate of a bowling spell. Those three are what I spent years charting by hand.

The spreadsheet had a pulse; I just charted its breathing.

The method is simple and laborious. Every delivery is a cell — bowler, batter, line, length, shot, outcome, and a pressure flag I assign before the ball is bowled, based on the set field and match situation. Then I compute a rolling twelve-ball dot rate. Charting one spell in the 2026 league, I found a fast bowler's dot rate holding at 0.58 across his first three overs and collapsing to 0.19 in his fourth. That is not abstract fatigue; it is the breathing pattern of one specific spell. A bowler's tiredness becomes visible exactly when the breathing of his dot rate breaks.

I sat with the numbers until they confessed the context I had missed. In my 2026 notebook I had not initially reconciled my leg-bye definition; four matches later I realised my run totals disagreed with the broadcaster's for precisely that reason. Before the context arrived, the number was meaningless — and it could still have been written into a ledger, perfectly, and wrongly.

One thing needs saying about PPDA, because it shows that a ledger and a model are separate objects. PPDA measures how many passes a side allows per defensive action by the opponent. The definition sounds simple, but what counts as a defensive action — interception, tackle, foul, or mere pressure — varies by provider. Binding Croatia's 9.1-to-13.4 story to a chain would answer who measured it. It would not answer what was measured.

The same caution applies to the 2026 Bundesliga data. Thirty-three per cent against 43%, and a 12% fall in home-favouring referee calls, are not exact. My sample was 81 matches; two matches going differently would move the numbers. Three competing explanations were live at the time: the compressed calendar, different acoustics in empty stadiums, and referee decision psychology without a crowd. I could not partition how much each contributed — and admitting that is part of the work. An analysis that does not record its own uncertainty is not an analysis; it is advertising.

So where does the reliability of ball-by-ball data actually come from? In my experience, three places: multiple independent charterers, a published definition sheet, and error bars. I had two friends re-chart twelve matches. Agreement on run totals was 99.4%. Agreement on whether a chance had been created was 71%.

The more interpretive the metric, the less a ledger can do.

Now back to erasure. Immutability means not only protection but permanent error. In 2026 I mis-attributed a run-out to the wrong fielder and only caught it four matches later. On paper I struck it through, initialled it, fixed it — ten seconds of work. On a hash chain that error would have remained forever: a beautiful, highly verifiable scar, but a scar. A pencil's capacity for erasure is a form of scientific humility; immutability can take that away if we quietly assume the first entry was right.

When blockchain tells you who wrote it and when, its job is done. Whether what was written is correct lies outside its jurisdiction. Provenance and truth are separate questions.

The model question is equally tangled. On the same shot, two xG providers give two different numbers, because they weight distance, pressure, body position and goalkeeper position differently. A flawless ledger will make both numbers immortal without telling you which is right. In most cases it will grant both equal validity — which is not helpful for analysis, merely irritating.

Cost and access are bigger still. Running a node takes bandwidth, electricity, hardware and time. In Barishal in 2026 my node was a 3G dongle and a laptop at the end of its life. Ledger infrastructure lives where servers live. The raw material — the ball, the sweat, the single-camera stream — is produced at the margins.

If the South supplies the raw material and the North keeps the ledger, that ledger produces a new kind of keeper, the same as the old scorebook. Only the keeper's name changes.

This is why a suspicion lingers in my reading of blockchain talk, a suspicion that comes from my anti-hype habit. I do not believe cricket data's strongest reform will arrive through cryptography. It will arrive through a shared definition sheet and one independent second charterer. Cost near zero, density of truth doubled. Blockchain sitting on top of that is good. Sitting underneath it, it is a well-organised error in a well-organised cabinet.

So what am I watching this season? Three signals. First, whether franchise leagues publish ball-by-ball logs — and publish them in auditable form, not as graphic screenshots. Second, whether anti-corruption units begin using timestamped, tamper-evident logs, or keep relying on phone records and witness statements. Third, whether the players who produce this data all year receive any share of its value, or whether it remains the scout's and the broadcaster's.

Thinking about domestic cricket makes this conversation harder. However much is written about the ball-by-ball records of Tamim Iqbal or Shakib Al Hasan, a young fast bowler's spell on a wet Barishal Division ground gets a tenth of that attention. Yet that is where the ball is made — and the raw material for the data we write about comes off that wet ground.

I am not claiming to have reached a conclusion. I keep my notebook photographs, scripts and notes on deleted entries public — and if someone charts differently and arrives at a different number, that will be the best possible ending for this piece.

It is nearly two in the morning again, and I am sitting in that same room in Barishal. The laptop has changed; the notebook has not. A ball goes beyond the boundary again, and I write a number by hand. The question is still there, and sharper now: for the delivery that no camera ever catches, who will keep the first entry — and who will own what is written?