The Genealogy of Numbers: Blockchain-Style Verification Discipline in Cricket Analytics

Last night in my Mymensingh study, as the clock neared two, I opened a spreadsheet. Twenty rows, seven columns, and exactly in the middle a cell that was completely blank. That cell was not the data of a new match; it was the far end of an analytical chain where no input had arrived, so no output had been born. I stared at the screen for a long while, the coffee beside me going cold. Because that empty cell taught me a truth more important than any filled number: an analysis that cannot verify its own input is not analysis—it is decoration. For forty-seven years I have hand-coded cricket events, but this was the first time an empty cell put my entire method on trial.

Cricket is now a game of numbers. Every ball, every run, every delivery's pace, every fielder's position—all of it is stored as data. But more data does not mean more understanding. Blockchain's core promise is verifiability: every transaction carries an immutable, auditable record, and anyone who wishes can cross-check it independently. Cricket analysis needs exactly the same discipline. Every number should carry a source, a time, a method. That is what I call the genealogy of numbers.

I began writing in 2026, covering the Wills Cup in Dhaka for Prothom Alo. Back then I described matches by eye—which batsman looked at ease, which bowler looked sharp. That habit broke in 2026. At fifty-five, sitting in my Mymensingh study, I launched a one-man data newsletter called "The Mymensingh Metric." I hand-coded every Bangladesh Premier League match. The first was Abahani Limited Dhaka versus Sheikh Jamal Dhanmondi. Abahani's PPDA was 6.8, Sheikh Jamal's 11.2; xG was 1.9 versus 0.6. I logged 12,000 passes, built a spreadsheet of 240 matches, and found that PPDA predicted points better than possession. That spreadsheet was read 4,200 times. I worked alone, but I shared raw data with a video analyst to cross-check.

In 2026, at fifty-six, I built a pre-tournament xG bracket for the Russia World Cup. My model gave Croatia only an 11 percent chance of reaching the final. When Croatia beat England 2-1 in the semifinal, the xG was 1.4 versus 1.1. I had already published a 12,000-word preview flagging Croatia's midfield press and set-piece xG. That episode taught me that 11 percent is a real signal—if its genealogy is clean.

In 2026 the stadiums emptied. I was working as a transfer market administrator. Tracking home advantage across 1,200 matches, I found it had fallen from 0.35 goals to 0.12. Reviewing a deal for Bashundhara Kings, I saw that the target midfielder's high-intensity sprints had dropped 22 percent after COVID. I rejected the transfer and saved the club 180,000 dollars. I built a model showing that xG overperformance in empty stadiums was random, not skill. I worked nights alone, cross-checking distance-covered data with a fitness coach. Ever since, I hold that an empty stadium is not a neutral stadium; it is a controlled experiment.

In 2026 I studied Italy's Euro 2026 win and the Tokyo Olympics. Italy's PPDA was 8.3; Jorginho averaged 7.2 progressive passes per match. At the Olympics, Pedri completed 92 percent of his passes and made 11 progressive carries per match. I built a "press-resistant midfielder" framework around five metrics, tested it on 40 midfielders across Europe, and found it predicted team xG better than pass completion alone.

Through all these paths I arrived at one lesson: every number has a genealogy; if you ignore it, you inherit its lies. Twenty years ago I decided from a match average. Now I first ask—on which pitch, against which opponent, at what time, over how many balls was this average made? If there is no answer, I do not use the number; I leave a question mark beside it.

So I run a tiered evidence system. Tier one: clean, large-sample, independently verified data—these I publish with confidence. Tier two: partial data with incomplete context—these I publish as probabilities, not certainties. Tier three: signals only, small or contaminated samples—these I keep as internal notes, never as the basis of a decision.

There is one blockchain quality I want to borrow for cricket—attaching a timestamp and a verification link to every record, so that later someone can cross-check it independently. Every column of my spreadsheet now carries a date, a source, and the name of whoever verified it. I do not trust any sprint metric unless I get the raw GPS data from the fitness coach. The spreadsheet is my monastery, but the pitch is where sins are confessed.

Now to that empty cell. If no input arrives in the analytical chain, there is only one honest answer—"insufficient information, cannot assess." But the temptation is strong. The moment we see a blank cell we fill it with a guess, because a blank cell looks like failure to a reader. Yet the most dangerous analysis is the one with no input but a conclusion. I call this process risk. Many wrong decisions in sport were born not because the data was false, but because the data did not exist at all, and no one dared to say "no."

I still hand-code, because doing it by hand attaches a memory to every number. I remember which ball I discarded and why. Automated tools are fast, but they do not know whether a wicket fell because of an easy pitch or a batsman's bad mood. Once I delayed an article by two weeks to verify a single xG figure. Readership fell, but the number held. This slowness is part of my method.

Right now we are inside a major tournament cycle. Tournament pressure compresses emotion—flag and story carry the reader away, and that is exactly when numbers become most misleading. We sometimes treat a single match-winning innings as proof of an entire career. Yet in a tournament, squad depth, rotation, and fatigue are often more decisive than individual brilliance.

In the Bangladeshi context this is even truer. Take Litton Das's strike rate at home versus in foreign conditions—they are not the same; Mushfiqur Rahim's situational average differs on a slow pitch and a quick one. Shakib Al Hasan's bowling economy in the powerplay is not the same as in the death overs. When Mustafizur Rahman's cutter works, his data shines; but the real question is on which pitch that cutter works. In each case I look at sample and context first, then the number.

I have found much information that is not shiny yet is powerful. A team's small fielding error, the rhythm of a dot ball, the tempo of a partnership—these do not make headlines. Yet the quietest datasets often hold the loudest truths about the game. When readers look only for sixes and fifties, these quiet truths are lost.

So I am especially cautious with domestic cricket data in Bangladesh. Our data quality is not equal to world cricket's. Reaching a conclusion from four good innings in one league is not the same as reaching one from a full season's sample. I do not import a metric from a foreign league directly into ours. Because the Mymensingh Metric taught me that context travels slower than data. A success born in one condition often loses its meaning in another.

Asia's cricket context is more complex still. Here the domestic league, the national team, and star culture run together. A player turns out for a franchise one week and for his country the next. In that shift his role changes, so his data changes. An analyst who cannot catch that shift evaluates two different jobs with the same number—and is very often wrong.

I owe the reader a duty. Analysis does not mean hiding uncertainty. When I make a claim, I give it a probability band. Sometimes I say—this judgment carries seventy percent confidence, the rest depends on context. Readers like this honesty, because they know where the limits of my knowing end. Writing that says nothing new is meaningless; so in every piece I try to give at least one fact the reader did not know before—a ratio, a context, or a question.

Now the reverse side must be seen. If I always plead context, I will never reach any conclusion. This is the biggest trap of my method—excessive context dependence. So I decide in advance which contextual changes I will let into the model and which I will not. Pitch, weather, travel load, crowd presence—these four I treat as conscious covariates. The rest of the excuses I keep outside the door. Otherwise context becomes not a tool of analysis but an escape route.

The second trap is mistaking correlation for causation. When a team scores more, we say its batting is good; but perhaps the pitch was easy, the bowling weak, or luck kind. Correlation is not causation. I do not trust a model that cannot survive a red card, a rain interruption, or a data patch. In cricket, rain, Duckworth-Lewis, DRS—each of these uncertainties must be brought inside the model and accounted for, not discarded outside it.

The third trap is my weakness for underdogs. I believe in probabilistic underdog nerve, not in love. Croatia's 11 percent taught me that an underdog sometimes creates a real edge—through rotation arrogance, a low-block press, and asymmetric risk. But not every underdog gets an edge. So I now set an explicit threshold: unless my model's gap against the market probability is large enough, I do not back any underdog.

There is a moral question here too. As a transfer market administrator I protected a club's money because I could say—this data is not enough. If I had filled that empty cell with a guess, the club would have bought the wrong cricketer, and no one would even know why. An analyst's honesty is therefore not only a question of method, but of money and careers.

Finally, one direction. Cricket's future is not only more data, but more verification. Fan tokens, NFTs, and blockchain-based match records—if they truly arrive, their real value will be transparency, not speculation. The league that makes every ball's data independently verifiable will earn the most trust. And as an analyst my job is simple—I will ask every number for its genealogy. Do you know where your favourite statistic came from, and who verified it?