Empty Blocks, Broken Chains: Cricket Data's Blockchain Provenance and the Crisis of Witness-less Numbers

Last night, in a small flat in Manchester, I opened a data file and stopped cold. The structure was familiar — questions on the left, answers on the right. The questions were written in the language of the field: which format, who is playing, what happened in which innings, who is batting, how fast was that ball. Down the answer column, one sentence kept returning — "insufficient information." Not a single number, not a single name, not a single date. In one corner of the file, a label blinked: cricket_asia. Seventeen years of watching matches tell me the field is never empty. Even a rain-soaked pitch holds a story, a dressing room's breath. But this file was silent. No ball, no witness. In that moment I understood: the problem is not cricket. The problem is the system that translates cricket into numbers. And when that system comes back empty, the easiest task becomes the most dangerous: filling the blank with your own imagination. Every number has a first touch, and every first touch has a witness. Today's empty file is the story of searching for that witness. I am Nazmul Rahman. Born in Bangladesh, raised on Dhaka's cricket fever, my working life spent in Manchester's data rooms. I began writing at The Daily Star's sports desk in 2026, and in 2026 I turned a hobby page into a professional cricket portal called BDCricTime. Both ends taught me the same lesson: information matters only when it has a source and a witness. I remember 2026. I was a 26-year-old junior analyst at ScoutLab in Manchester, handed the due diligence on Manchester City's 35 million pound signing of Ederson. I built a pass-origin map — 38.2 passes per 90 at 85.4% accuracy, with 12.1 long balls. City fans on Twitter pushed back: Portugal's Primeira Liga is slower, so those numbers are inflated. I spent two weeks re-coding ten Benfica matches, adding PPDA faced (9.8) and pressure-adjusted pass accuracy. Then a 14-tweet thread. Since then, every report of mine carries a section: "Fan objections." That habit is what makes today's incident so uncomfortable. We work in two stages. Stage one breaks a raw article apart: title, source, core claim, and most importantly, the small units of fact called information points. Stage two builds deep analysis on those units. Today, at stage two, we got an empty plate. No title, no source, no type, no claim, no information points. Only the label remains: cricket_asia. From here, two paths. One: build something fast — slot in a name, a score, a story. Two: stop and say, a block is missing from this chain. I chose the second. The simplest idea of a blockchain is this: once information is written to the ledger, it cannot be quietly changed. Each block holds a hash, and each new block carries the hash of the one before it. If someone alters the middle, the whole chain breaks — and everyone can see the break. Sports data needs exactly this. Every number needs an origin, a timestamp, a sensor log, an edit history. Who wrote it first, when, and what changed in which edit. In cricket we use Hawk-Eye, Snickometer, ball-tracking, DRS — yet we think little about the chain of custody of that data. Without a chain of custody, data is an orphan number. Take the speed of a ball. The broadcast shows 145 km/h. But that number has a birth. Who measured it? Which radar? At what frame rate? Was it measured at release, or just before it pitched? Without answers to these questions, 145 km/h is a number, not evidence. Building a trend on a witness-less speed reading is building a house on sand. Consider DRS. A review is not merely tracking a ball; it is reconstructing a chain of decision — where the ball pitched, where it impacted, where it met the stumps. Each step is a piece of evidence. If one step is missing, what stands between 'out' and 'not out' is a guess, not proof. The same rule holds across every corner of cricket data. Today's analysis examined eight dimensions. Format and match, player technique, team landscape, league and commerce, rules and governance, risk, public narrative, and industry transmission. All eight returned the same answer — "insufficient information." Eight empty blocks. Eight links of a chain, each one zero. One thing must be clear here: an empty answer does not mean "nothing exists." An empty answer means "the step above did not work." The domain label arrived, but the content did not. That means the labeling module ran, but the extraction module stopped. Exactly where the real information should have been, a block was never hashed. And here lies a resemblance to blockchain that should make us cautious. Blockchain gives immutability, not a guarantee of truth. A blockchain of lies is still a lie. The industry has a name for this — the oracle problem. A smart contract does not know what happened on the field; it must be told through an oracle. And if the oracle is wrong, perfect code produces a wrong result. Cricket data works the same way. Our sensors, scorers, broadcasts — all are oracles. Someone speaks first: "that ball was 145 km/h." The rest of the chain stands on that first sentence. I fear the day an empty file lands in the hands of a language model, and the model politely, confidently fills it in. A fabricated scoreline, a fabricated half-century, a fabricated dropped catch. That data will look real, because it will be shaped exactly like real data. This is not a chain hack. It is worse — it is smuggling counterfeit blocks into the chain. The model did not change because of the speed; it changed because you voted. I learned this in 2026, in that France-Argentina 4-3. Mbappé's 0.78 xG, 5 shots, 4 progressive carries, and a 37 km/h sprint. After the match, French and Argentine fans argued: was the decisive factor Mbappé's speed, or Argentina's high defensive line? I ran a poll. 12,000 votes came in. Then I added two new variables to my model — "line height" and "recovery runs." Here is the real lesson: fan doubt is an input to the model. But be careful — a poll is never a verdict. A vote is evidence, not a final word. So every poll needs a traceback and a sample audit. And what does traceback mean? It means following the ball backwards. I traced the pass back until the highlight forgot where it began. Sensor logs, forum posts, broadcast edits — three placed side by side and compared. So the highlight never forgets where it came from. I remember 2026. May, aged 29, at Football Analytics Lab in Manchester. I analysed 50 Bundesliga matches played in empty, pandemic-era stadiums. The home win rate fell from 43.3% to 32.0%; fouls awarded to home teams dropped by 1.2 per match. Using PPDA and distance covered, I showed pressing intensity fell 7%. The numbers were clean. But alone, alone, I was breaking down. So I started a weekly Zoom called "Data & Fans" with 30 supporters from City and United groups. They shared not only numbers but grief and anger. That experience is proof to me: the witness of a number is not only a sensor, but a person. The drop from 43.3% to 32.0% in empty stadiums was never caught on any dashboard — it was caught in a fan's voice. Coming from Bangladesh to Manchester, I understood something else clearly. In the eyes of a diaspora fan, data has a different value. Those of us abroad watch matches behind a camera, across a time difference, maybe at half past midnight. For us, data is the bridge that brings the field home. But if that bridge is bolted together with witness-less numbers, what we get is not the field but a picture of the field — and if the picture is false, the home becomes false too. Early in my journalism, at The Daily Star's desk, I learned something from the older reporters. To write about cricket's old days, they said, you had to trust memory carried mouth to mouth — because there were no sensors then, only eyes. And each pair of eyes saw differently. Even then I understood: evidence is not a single truth; evidence is the combined effort of many eyes. In the digital age we are losing that many-eyed system — we have begun to treat one number on a screen as the final truth. So I do not worship the dashboard; I ask who is missing from it. In today's empty file, everyone is missing. There is no batter, because there is no witness. No bowler, because there is no witness. No match, because there is no witness. A transfer rumor is a data point until it becomes a person. In the same way, a data point is a number until it has an origin and a witness. Today's file has no origin, so it cannot become a story. It is only an empty block. We are in the middle of a transfer window, where rumors flood and facts drip. In this window the real story is never the rumor; the real story is the structure of release clauses, the wage bill, the agent's movement. And all of it needs evidence, a source, a witness — exactly what an empty file needs. Now I come to the place where I argue with myself. The easiest conclusion is this: an empty file means a failure, and the failure belongs to the pipeline. I cannot fully accept that. An empty file is, in fact, an honest file. An empty file is far more honest than a file stuffed with lies. Imagine the system had politely filled the blanks with imagination. Set the format to "T20," slotted in a batter's name, set the score to 164/6. None of us could have caught it. Because those numbers would look exactly like real numbers. Immutability would not have protected us then; immutability would have become a seal — an unchangeable stamp placed on a lie. Blockchain enthusiasts often say immutability means trust. I say immutability means only trust transfer. The responsibility moves from the sensor to the place where the first block was written. And if that first writer is not himself a witness, the whole chain becomes a hall of mirrors — everything it shows is false, yet every reflection is perfect. The second objection is more uncomfortable. In cricket analysis we spend far more time on the content of numbers than on the plumbing of numbers. No one reports that the extraction module stopped. No one writes the headline "label arrived but content did not." Yet that very gap is the biggest story — because every other number comes from there. And the third objection points at myself. My own habits are my danger. Community verification and the practice of re-coding again and again taught me patience, but they can also push me into a trap — always believing that one more round of verification will reveal the truth. If there is no truth, verification is useless. Run all the verification you like on an empty file, and the empty file returns. Here what is needed is not changing the model, but repairing the step above. So my contrarian claim is this: today's decision was not wrong — it was the right decision. The real mistake was that the system was ever allowed to run on an empty input. A chain should never be started with an empty block. So today I ask the reader one thing. The next time you see a number — an average, a strike rate, an xG — ask: who is this number's witness? Who wrote it first? Which edit changed it? If you get no answer, treat the number as a suggestion, not a truth. In the next round, I will watch three signals. First, a minimum-input gate — stage two will not run without at least a title and one information point; an empty input returns on its own. Second, a provenance ledger — beside every number, the name of its witness, the time, and the edit history. Third, a community audit — so fans can ask, "where did this number come from?" Because in the end the question is not cricket's; the question is ours. Will we build a system where every number has a witness — or a system where any blank can be filled by anyone, at any time, exactly as they please? When the chain breaks, who do you call?