From the Scorebook to the Ledger: Cricket's Data Integrity, Blockchain, and the Archive of Invisible Labour

One evening in December 2026, in a small scoring room beside the Sylhet International Stadium. Twelve scorebooks spread across the table, each with fine pencil marks along the margins and eraser dust gathered in the corners. Fog outside, tired fluorescent light inside. That evening I learned that these books, hand-kept for twenty-six years, were no longer needed — the board had decided to digitise, and our unit was surplus. The work ended before the pencil came down.

Three months later I sat down for a new outlet in Dhaka. The work was the same — watch, count, write. Across Abahani Limited Dhaka's 2026-18 Bangladesh Premier League title season I hand-coded all twenty-four matches: 1,043 defensive actions, an average PPDA of 8.4 in wins against 13.9 in draws. No editor in the country had seen pressing data applied to domestic football. Nothing about it was new to me. What is written in the margin is the real thing. The margin note is where the match actually lives.

Now, standing inside the 2026 transfer window, I am looking at another kind of book — the blockchain. Writing one over means a dozen decisions: which ball is legal, which is a wide, which runs are byes, which catch is clean. The scorer makes those calls, the broadcast shows three of them, and the other nine disappear. I count what the camera refuses to count. The silent pressure of dot balls, the dust of the domestic league, women's cricket, ground staff, scorers — the accounting of this invisible labour appears nowhere.

Franchise leagues, boards, broadcasters and sponsors all now pronounce the same word: blockchain. Fan tokens, digital collectibles, blockchain ticketing, transfer clauses written into smart contracts, player registries, even the promise of immutable records for anti-corruption work. Does an immutable ledger make cricket's accounting true? The question is simple; the answer hides inside the structure of the book itself.

What double-entry bookkeeping has done for five hundred years, blockchain does in digital form — every transaction is written in two places, and no one can change one side alone. A scorebook is a ledger too. Runs on the left, wickets on the right; change one side and the other stops balancing. I have spent thirty-four years balancing those two sides. When they do not balance, the written record is wrong, however beautiful the camera's picture. Silence has a box score.

Blockchain automates part of that balancing. Each entry carries a cryptographic hash and a timestamp; the next entry holds the previous one's hash. To alter an earlier figure you would have to rewrite every subsequent hash, and that change would surface across every copy on the network. In football and cricket franchises it has already entered experimentally — fan tokens granting votes on club decisions, digital collectibles of match moments, blockchain-based ticketing where a forged ticket is nearly impossible to issue.

The most interesting possibility lies in player registries and transfer clauses. If a release clause is written into a smart contract, no one can secretly alter a figure on a given date. Suppose a domestic league contract states a bonus after a set number of matches, or a transfer fee triggered once a performance threshold is crossed. The smart contract verifies that condition itself. It is cleaner than a paper contract. But where do the numbers in the condition come from? That is the real question.

Here is blockchain's first gap. A ledger can be immutable, but immutability is not the same as truth. If someone enters false or mistaken data, blockchain preserves it forever — it cannot be changed. Bad data, but permanent. The question is the old one: who enters the data, and who holds them accountable? The model-first world skips this question, because it is far less pretty than a clean dashboard.

In anti-corruption work the gap is sharper. In 2026 Shakib Al Hasan was sanctioned by the ICC for failing to report corrupt approaches. Those approaches came in private messages, on the phone, in hotel lobbies — nowhere were they written on a blockchain. Corrupt decisions are not made on the field but off it, where there is no camera and no hash. An immutable ledger cannot reach that invisible place. I do not predict; I archive the conditions of prediction.

The transfer window deserves to be read in this light. Much of what is happening in Bangladesh's domestic market during these weeks of 2026 is rumour — which franchise is signing whom, which agent is dining with whom. A rumour has zero value because it cannot be verified. Three things are verifiable: contract length, the structure of release clauses, and the wage-bill space. The transfer window is a ledger, not a soap opera. A paper that sells rumour drifts away from cricket's accounting.

I always keep hand-coded data as the first scorer and the model as the second. A model loves clean numbers, and cricket is not clean. At Russia 2026 I coded all sixty-four matches by hand across three time zones — 1,704 shots and 169 goals. In the semifinal France held 40 percent possession and conceded six goals across seven matches. The numbers suggest France were weak. Reality was different — the low block was structural, not lucky. A model reads low possession as risk; I read it as a decision.

The same holds in cricket. An innings strike rate is a number, but without context — which over, against which bowler, with how many wickets down — the number is meaningless. The margin of the book carries that context. Blockchain can hold that context, if someone writes it in. And here the question of invisible labour returns.

In 2026 a national ICT recognition came to a Bangladesh cricket data platform. The people behind it — scorers, coders, editors working nights — never appear in large type. An award goes to an institution; the work is done by many. This inequality is not the ledger's fault but the culture's. A blockchain can record exactly who made an entry, but who receives credit for it is decided by editors, institutions, power.

There is another gap in domestic data infrastructure. Domestic league matches have fewer cameras, so video-based models are blind there. Where there is no camera there is no data — and yet that is where players are made. A large share of young players crowd into big academies while fewer than ten percent get a genuine first-team path. No one writes that number on a blockchain, because it benefits no one's promotion. A blank cell is not empty; it is waiting.

In scouting and the transfer market, youthful potential is inflated and dressing-room chemistry undervalued. That is not the model's fault but its limit. Chemistry cannot be measured, so the model does not count it. And yet a team breaks precisely when trust leaves the dressing room. Behind Abahani's 2026-18 title was a stable structure — PPDA of 8.4 in wins against 13.9 in draws. That difference was not talent but cohesion. Blockchain cannot buy cohesion, only record it.

Now the uncomfortable part. Blockchain's biggest promise is trustlessness — no intermediary needed. But in cricket the source of the data is itself an intermediary. The scorer who writes the ball is the oracle. If the ledger is decentralised, the point of data entry remains centralised — in one person's hands. Power thus moves from the storage layer to the entry layer, where there is no audit.

The fan-token question sits here too. A vote on club decisions sounds democratic. But tokens can only be bought by those with money. A supporter's vote becomes a vote of capital. This does not build community; it converts community into a financial asset. Fandom was sometimes fandom, and sometimes became an investment. The ledger will record that transaction perfectly, but the question is not about the transaction — it is about who gets to vote.

Another trap is permanence. An immutable record helps in legal disputes but closes off correction of an individual's error. If a player's name is spelled wrongly, written for good, it cannot be corrected. Accounting keeps reverse entries for correction; many blockchain structures lack that elegance. So my advice is simple: every smart contract should carry a correction process beside it.

The conclusion is clear. Blockchain can make cricket's accounting more secure, not more true. Security means no one can change it; truth means what is written actually happened on the field. Between the two sits a blank cell, and a human fills it — a scorer, an auditor, a journalist. If no one will speak of that cell, the accounting stays incomplete however strong the ledger.

Technology is no enemy to me, but a colleague. And a colleague's work is mine to verify. When I did a long interview with the young Soumya Sarkar in 2026, I learned that writing praise requires information, and writing information requires patience. That patience is the scarcest asset of this new ledger age. Anyone who thinks a dashboard answers every question has not read the margin of the book.

My plan for the coming weeks of the transfer window is simple. Beside every rumour I will place one verifiable fact — contract length, release clause, wage-bill impact. When an announcement comes, I will ask who the source is and where their information came from. If someone says the data is on the blockchain, I will ask who made the entry. Those two questions are the real filter, and that filter is the most useful thing in the 2026 market.

I leave the last question open. On the day cricket's accounting moves entirely to the ledger, who will keep the small note written in the margin of the book? Will the pencil-holding scorer, whose name appears nowhere, become part of the ledger, or remain written in the margin forever? Night shift is not a schedule; it is a confession. Without writing that confession, no blockchain will ever be complete.