The Pitch Blockchain: Dhaka's Data Desk and Cricket's Immutable Ledger

Hook

I opened the Dhaka desk file, and the first column was already arguing with me. The left column was the official scorecard from Mirpur's Sher-e-Bangla National Cricket Stadium — one seamer, four overs, twenty-eight runs, one wicket. Clean, courteous, almost praiseworthy. The right column was our desk's ball-by-ball ledger — and there the wicket was born in the fourteenth over, at the other end, inside six consecutive dot balls from a spinner. The shot the batter played in the final over was not a decision; it was the interest on pressure accumulated across thirteen deliveries. The scorecard wrote the wicket against one name, the ledger against another. I trust the ledger, because it is a blockchain — every delivery is a block, and nobody can walk back in later and rewrite the chain to suit themselves.

Driving home from the ground that night, I was wondering where cricket's largest lie hides. For twelve years in television studios I heard who took the wicket, who won the match, who failed. The ball-by-ball ledger shouts that nobody "takes" a wicket — wickets are built, and the construction date never appears on the scorecard.

Context: one delivery, one block

In 2026, aged fifty, when I joined a new digital outlet in Dhaka as a data journalist, I had a broadcasting degree and a certain stubbornness. That year I built an xG and PPDA collection sheet for the Bangladesh Premier League and logged 1,240 shots across sixty-six matches. After Abahani Limited Dhaka beat Sheikh Jamal Dhanmondi Club 2-1, my match report carried fourteen metrics and no vague adjectives. The outlet adopted the template across all football coverage. From then on I had a rule: no publication without xG, PPDA and distance-covered totals.

I carried the same rule into cricket. Here a delivery is a block. Each block carries fifteen fields: timestamp, bowler identity, batter identity, over and ball, release point, speed, seam position, bounce height, field coordinates, fielder's name, batter footwork, pitch moisture, temperature, crowd attendance, and DRS state. A ball is a block; an over is a chain segment; an innings is a ledger.

This is where the real lesson of blockchain sits. If someone says three days later that the catch was actually at leg gully and not slip, our system spawns a fork. A fork means doubt. We do not accept forks; we record which truth claimed primacy first. The official scorecard is a central bank note — it can be corrected, and usually nobody notices. The ball-by-ball ledger is a distributed journal — thousands of phones, thousands of screens, thousands of dot-live apps carry the same block, and the cost of hiding an error becomes abnormally high.

From 2026 to 2026 every match at the Dhaka desk kept this fifteen-field structure, even low-profile Dhaka league fixtures. The reason is simple: in domestic cricket bowlers are valued on average and economy, batters on strike rate. But those two numbers weld together the pictures from two different ends, and the important thing is precisely what they separate — where pressure is built and where the result lands.

Core analysis: testimony of three blocks

First block. We built a metric for spinners and called it the Pressure Transfer Rate. At Mirpur, where the ball turns slowly, a left-arm spinner's dot balls are largely defended and released — they become dots, but the wicket lands in the column of the pacer at the other end. Across the last three seasons our logs showed that a pacer with excellent figures took a large share of his wickets in the very next over, when his partner had strangled the scoreboard for six or seven balls. The scorecard grants ownership of a wicket; the ledger grants the birth certificate. Ownership and birth certificate are not the same document.

Second block, and the most uncomfortable. When the stadiums went silent in 2026, the home-advantage columns began to confess. Like many leagues, Dhaka assumed home advantage meant the pitch, and the pitch meant spin. Our logs from a crowdless Mirpur showed that assumption to be wrong. With no crowd, a bowler's psychological shield for surviving a mis-length shrinks, and a confident batter hesitates less before the big shot. In dashboard language: patience in the attacking phase fell in empty grounds, and finger spinners started releasing their stock length. The crowd, it turns out, was part of the pitch.

Third block — and here sits the real weapon of someone born in Britain and working in Bangladesh. PPDA is fundamentally an English football model, where a press means speed, sweat and willing legs. When I logged Croatia at 8.7 PPDA and England at 11.2 in the 2026 World Cup semi-final, I published from Dhaka. But in Dhaka's humidity the meaning of a press changes. At thirty-three degrees, a press is not just running; it is a development decision, deducted from the next over's pace. In South Asian conditions an imported model is not a measurement, it is a translation problem. The bowler who can sustain that press in Bangladesh at thirty-three degrees means far more than the same number means in England — yet both collapse into the same cell.

Contrarian angle: the ledger's blind side

The dashboard was never the answer; it was a map I had to redraw. Immutability is good, but immutable does not mean accurate. If someone enters a field coordinate wrongly, that error becomes a permanent block, and every downstream block inherits it and sits beside it. Our logs hold one such case where a batter's "short-ball weakness" persisted for two years because a 2026 catch fell at deep square and somebody mistakenly tagged it at silly point. The error was never erased; it was inherited.

So do not forget: a blockchain proves sequence, not cause. That one block followed another is mathematical fact. That the earlier ball caused the later one is a different claim, and the file will not produce it. Six dots preceded the dismissal; whether those six dots manufactured the pressure or the batter was cramping, the ledger cannot say. Keep logging — but to explain, you have to stand at the ground.

The second blind side runs deeper. The largest evidence from the crowdless stadiums of 2026 and 2026 is what was never measured. DRS decisions, the square-leg umpire's doubt, overnight pitch moisture — none of it is in the ledger, because nobody logged it. What is not measured is not in the ledger, and absence creates no block. That silence is especially dangerous in South Asian cricket, because here the character of a match is often set by things our tracking never captured. And the spectator is the party whose explanation is never written down. On the big screen a DRS verdict arrives without a public rationale, and the person who bought the ticket is expected to accept the outcome rather than understand the decision. We learned the scorecard from imported models; we have not yet taught it to the person standing in the stand.

The same silence is louder in the women's game. Dhaka's domestic women's league has almost no ball-by-ball ledger, almost no field coordinates — because there is no demand and no allocation. Data infrastructure is rarely built for its own sake; it is built when sponsors want to look modern. So the talent exists, and no truthful ledger sits beside the name.

An old suspicion of mine settles comfortably here. The way modern football is erasing the traditional winger hugging the touchline is exactly how the data revolution is erasing the dot-ball bowler. The bowler who exists as 4-0-24-1 is treated by the model as surplus; the bowler who strangled those twenty-four runs in the fourteenth over and prepared the ground has no ID at all. I have learned to trust the row that refuses to fit the story.

Takeaway

Across the first three rounds of the domestic season my eyes will be on two things. One, the Pressure Transfer Rate — how many wickets a pacer takes while his spinning partner is blocking. Two, the silent-wicket index — a bowler's capacity to hold length in home conditions. The gap between those two will be the real signal of the next big decision, and it will not appear in the table. The table only adds runs. The pitch blockchain asks a different question: who built the run, and who paid for it.

Data Verdict Box: Dhaka Data Desk, 2026–2026 — 66 matches, 1,240 shots, fifteen variables. In the 2026 World Cup semi-final, Croatia's PPDA was 8.7 and England's 11.2. In 34 per cent of wicket credits on the scorecard, the bowler who built the chain was a different bowler.