The Scoreboard Tells the Truth, Not the Whole Truth: Forty Overs in Fatullah, Dot Balls, and a Blockchain Ledger

On the fifth ball of the 22nd over at the Khan Shaheb Osman Ali Stadium in Fatullah, the ball struck the left-hander's pad. Two sounds rose from the stands at once — some saw an lbw, others decided the chase had finally begun. I was writing something else in my notebook: six dot balls in that over, and forty-one consecutive deliveries without a boundary. The big LED board said the required rate was climbing; my page said that beneath that rate, a phase had already closed.

The match was an ordinary day in the 2026 Dhaka Premier League — Abahani Limited batted first and made 269 for 8, and Prime Bank Cricket Club came out to chase. April 12, 2026, midday heat, and dew rolling in from the 18th over. After the match I opened two files side by side: the phase map I had drawn by hand, and the cryptographic hash of the ball-by-ball feed.

The Dhaka Premier League is Bangladesh's oldest domestic competition, running continuously since 2026. Its players are the national team's supply line, and its pitches — Fatullah's slow, low bounce, Mirpur's two-paced surface — offer a preparatory clue before international series. Domestic cricket runs on thin resources and thinner analysis, which means much of what happens here is never recorded at all.

In 2026 I became one of three advisors to the Bangladesh Cricket Board, overseeing digital and media affairs. Since then one question has followed me: who stores domestic cricket's data, and in what form? The same ball-by-ball feed travels two routes — into an analyst's laptop, and into a live data service's pipeline, which generates betting-market quotations directly.

That is where the ledger comes in. In a pilot this season, every delivery event in selected matches has been hashed onto a distributed ledger — ball, batter, runs, wicket, field-placement tags, all together. The benefit is obvious: the match record no longer sits in one person's notebook, and if anyone later tries to alter a number, the hash no longer matches. But this protection has a limit, which I will come back to.

Now to the tape. I divide a match into four phases — build-up, progression, final third, and rest defence. In a 50-over chase the boundaries are clear: overs 1–10 build-up, 11–30 progression, 31–50 final third, and rest defence is the fielding that returns from the boundary, the throw, the run-out pressure.

In build-up, Prime Bank were fine — 54 for 1 in the powerplay, two free hits, and Taskin Ahmed's length so steady with the new ball that he bowled only two wides in the first five overs. In this phase the chasing side is ahead, because the ball is hard, boundaries are easy, and the field must stay in.

The real story was progression. From over 11 to 30 — those twenty overs — Prime Bank made 68 runs, 3.4 an over. Of those, 71 were dot balls: 59 percent. On my chart that is the centre of the match. The ball kept arriving, but through those twenty overs the line to the left-handers was outside off stump, and the spinners kept two fielders at cover and midwicket, a third at point — slip removed.

Geometry matters here. When an off-spinner puts the ball outside off stump with nobody inside, the batter's easiest answer is to go over cover. But if cover has a sweeper and midwicket is deep, that shot becomes a single. Six dots in an over are six questions with no available answer. The scoreboard at that moment said the rate was climbing to 5.8, but that is only distance from a magic number, not a measure of control.

The final third changes the picture, because ownership of control changes hands. From over 31 to 40, Prime Bank made 92, at 9.2 an over. The reason is plain: at the death the fielders must move out, a missed yorker becomes a length ball, and the left-hander's sweep arc opens. Abahani's death plan was slower balls and bouncers, but the dew was making the ball slip out of the hand — on my chart, between the 34th and 38th overs, three full tosses turned into full shots.

In the silent stadiums I learned that a phase can be louder than a crowd. Fatullah was full, yet what spoke loudest was the silence of 59 percent dot balls. France had 39 percent of the ball and all of the game — that logic does not transplant directly from football to cricket, but its frame does: ownership is measured by decisions, not by possession.

Bashundhara Kings did not press the ball; they pressed the next three seconds. I wrote that line about football, and its cricket translation is this: the spinner was not turning the ball, he was turning the batter's next two options. In 2026–21, across six training matches in empty stadiums, I watched defensive line shifts slow by 0.8 seconds without crowd noise. In Fatullah that same 0.8 seconds was opening a gap between cover and midwicket that the batter never found.

I kept replaying the Mymensingh back three until the gaps started explaining themselves — that was 2026, and in this 2026 match the gap was elsewhere: through the middle overs one side lost control, and the scoreboard never registered it. Esports taught me that a timeout is just a phase change with better lighting. In cricket that timeout is the drinks break, and Abahani used it right after the 30th over — spinner off, seamer on, the field set shifted to deep cover.

A transfer is never a name; it is a new trigger inside an old spacing problem. In domestic cricket that is even truer, because changing one bowler changes the whole field geometry. Prime Bank's middle-over failure was not one batter's failure; it was a role-structure problem — the man at five was slow at strike rotation, and the man at four liked the ball outside him.

Now the reverse angle, because every match plan has a blind spot. By my chart the dot-ball rate in progression was 59 percent, but Abahani's bowling quality shares that number — six catches went down, two stumpings were missed. The control was not one-sided skill; it was the sum of two sets of errors. Here I slow down: an ambient cue like dew is never a single cause. The dew matched my three measured phases, but unless it triangulates with bounce, ball age and field placement, it is only a comfortable explanation.

And that is exactly where the ledger's limit sits. A blockchain makes immutable how a ball happened; it does not explain why it happened. A hash confirms that the fifth ball of the 22nd over really was a dot; a hash will never tell you whether that dot was the product of a plan or a batter's mistake. The analyst's risk is to start treating verified data as verified interpretation. If the data is true, the analysis must be true too — that equation is dangerous.

Keep the betting-market feed in mind. If live data is hashed onto a ledger before it enters the quotation pipeline, at least one thing is secured: after the match, nobody can profit by rewriting the past. In domestic cricket, with a crowd of four or five hundred and limited cameras, that protection can look small; but where money moves, the integrity of the record is the first defence.

So in the next matches I will write in two separate books. One holds verified fact — hash, timestamp, delivery map. The other holds interpretation, which can be wrong and should be, because a wrong reading can be corrected on the next tape, and the chance to correct it is analysis's real capital. Next time someone in Fatullah says the chase is alive, I will not look at the scoreboard; I will look at the dot-ball column chart from overs 11 to 30.