Ledger and Line-up: The Quiet Arithmetic of Blockchain Records in Asian Cricket

Sylhet International Cricket Stadium, the back row of the press box. During a 2026 BPL evening match I was still counting balls on a paper grid. Fourth ball of the fourteenth over — a front-foot no-ball from the spinner. The umpire raised his right arm, the scoreboard added an extra run, and in the margin of my sheet a small hand wrote: NB 14.4, front foot. After the match the board's digital portal showed the over count as 14.3. My sheet said 14.4. Nobody lied. Nobody knows which file is the master record, because there is no master record — there are three parallel files, one tired scorer, and a closed evening.

The same night a second thing caught my eye. Three different dates were circulating for one overseas player's No Objection Certificate: 11 January on the franchise contract, 13 January on the league register, 9 January on a forwarded agent email. The truth of a match lives in the margin of the scorebook; the legitimacy of a player lives in the forward button of an inbox. The blank cell was not empty; it was waiting for someone to write the true value into it. This piece is an attempt to keep the accounts of that waiting.

From 2026 to 2026, twenty-six years, I hand-scored board domestic fixtures in Dhaka and Sylhet. In 2026 the digitisation drive made our unit redundant. I did not retire; on a freelance contract I hand-coded all 24 matches of Abahani Limited Dhaka's 2026–18 season for a Dhaka football outlet — 1,043 defensive actions, an average PPDA of 8.4 in wins against 13.9 in draws. Nobody in the country had seen pressing data applied to domestic football before. The method was football's; the habit was cricket's.

In 2026 I was passed over for the Russia World Cup credential; the explanation was that a woman colleague would not be comfortable in the mixed zone. From Sylhet, across three time zones, I coded all 64 matches — 1,704 shots, 169 goals — with my own xG model. In my France file I wrote that they held 40 percent possession in the semi-final and conceded six goals across seven matches; the low block was structural, not lucky. Night shift is not a schedule; it is a confession — an account of who works without being credited.

Cricket's records do not sit in one place. Broadly there are four layers: one, match data (scorers, ball-by-ball, field maps); two, player registration and NOCs; three, contracts, transfers, wage bills and agent commissions; four, ticketing and fan products. Four layers, four sets of owners — board, league, franchise and marketing agency. There is no mandatory handshake between them.

It is worth saying plainly what a blockchain is, because the fog around the word is itself damaging. It is not magic, not a forecast, not a currency. It is a ledger in which each new block conceals the cryptographic hash of the previous one. To alter one page you must alter every page after it, and that alteration shows up in everyone's copy. A distributed, immutable record of authorship — in short, signatures and timestamps given a collective form.

Asia is running its experiments. In 2026 the ICC launched digital collectibles called Crictos in partnership with FanCraze (source: the ICC announcement that year). Franchise leagues discuss fan tokens, blockchain ticketing has been trialled, leagues have marketed collectibles. Meanwhile the core player registration documents still live in PDFs and email threads. The technology has reached the door of the showroom; it has not reached the door of the ledger.

Ledger one: registration and clearance

The normal process is guessable. A home board issues a No Objection Certificate for a defined window, the franchise files it with the league register, the league sends it to the board for verification. Three steps, three databases, three different loyalties. Somewhere in the middle someone loses paper, someone rewrites a date, someone simply mistypes.

If a remedy is wanted, nothing luxurious is required. One body — say the Asian Cricket Council — could publish a Merkle root of that month's registrations on the last working day. The root is small, a string of thirty or forty characters. If anyone alters a page, the root no longer matches. Nothing confidential is lost; salaries are not lost; only the convenience of denial is lost.

I have counted something else. In domestic tournaments, NOC disputes usually surface on the submission deadline, because when dates differ by more than a day, the league and the board each cling to their own convenient version. A deadline document without a timestamp turns accuracy itself into a matter of negotiation.

Ledger two: contracts, release clauses and wage bills

The transfer window is a ledger, not a soap opera. A national central contract list, a franchise auction budget, an agent's commission — these are not stories for the emotions, they are stories for the arithmetic. Shakib Al Hasan, Mushfiqur Rahim, Tamim Iqbal, Litton Das, Taskin Ahmed, Mustafizur Rahman — names on central contracts reshuffle the wage bill every season, and that reshuffle lands directly on how the national bowling load is shared. In the Pakistan Cricket Board's central contracts, the category shifts for Babar Azam and Shaheen Afridi point to the same economy.

Smart contracts could genuinely work here, if part of the remuneration is tied to match appearance. When conditions are met, payment is released into a designated ledger and the two parties need not trust each other separately. But this is exactly where the oracle problem bites. A chain cannot see the grass. Whether the match happened, how many overs were bowled, whether the player was on the field — somebody outside has to supply that. If the supplier errs that day, the chain immortalises the error.

My hand-coded file of 1,043 actions from the 2026–18 season still exists, with the time and reasoning of each decision written beside every row. If someone wants to send that file to a chain today, I will send it; but first I want it made explicit who is writing and what is being left out. I do not treat a model as an oracle, I treat it as a second scorer; and where the manual count and the chain count disagree, I publish both rather than welding them into one.

Ledger three: the integrity of match data

The most coherent use of a blockchain in ball-by-ball data is an audit trail — a permanent timestamps record of every recalculation, correction, revised target and status change. When rain rules change the arithmetic, the question is not whether the number changed but who changed it, when and in which version; if the answer sits in a hashed log, the argument becomes technical rather than conspiratorial.

I count what the camera refuses to count: dot-ball pressure, strike rotation, the empty overs inside a partnership, the wicketkeeper's footmarks, the pattern of no-balls. Most of that work is done in women's cricket, domestic cricket and by night-shift scorers — the layers the cameras barely visit. Integrity technology becomes meaningful when it reaches that layer; before that it merely decorates a big-match column with a famous byline.

The shape of the mismatch is worth tabulating.

|| Layer | Current store | Real bottleneck | | One | Match data | Scorer's sheet, live software | No reconciliation between the two systems | | Two | Registration, NOC | Board spreadsheets, email | Timestamp-free versions competing | | Three | Contracts and wages | Paper, PDF, office | No public accountability | | Four | Ticketing, fan products | Central database | Intermediaries already entrenched |

One sentence belongs after the table: this changes who holds custody of the record, because the guardian shifts from the board's office to the hash of the document, where anyone can verify it.

Ledger four: tickets, tokens and the noise ratio

This is where the talk is loudest and the numbers are thinnest. The fan-token market is negligible beside the cricket contract market, yet its presence on the sports pages runs in inverse proportion. The reason is simple: a token makes noise, a wage bill does not.

Blockchain ticketing offers a real gain in transferability and in squeezing touts. But the actual problem in Asian cricket is not touting; it is the supporter standing outside the ground who still cannot get a ticket, and the absence of transparency about who sets the price of each ticket. That is not a technology question, it is a will question.

The contrarian angle: a chain preserves errors with great care

A blockchain proves who wrote what, and when. It does not prove that what was written is true. In Asian cricket the weakness is not forgery, it is indiscipline in record-keeping. A board that does not get a scored card signed at the end of play will send the same untouched garbage onto a chain — more firmly, in fact, because there it will no longer be permitted to correct it.

The second hazard is cost and control. Signing up for a pilot is easier than writing every day; institutions tend to choose what can be displayed over what is genuinely difficult. I do not read the revival of the back three as progress, because it is not the success of attacking football — it is a manager avoiding the reputational risk of an exposed four-man line. Many blockchain announcements in cricket are the same move: standing behind a shiny method rather than pointing a finger at a weak process.

Third, chemistry beyond the camera. Transfer-market models overrate young potential and underrate the dressing room. Every statistic on the chain is present; absent are the people who stayed awake to hold a side together during a partnership.

Takeaway: what I will watch next window

Three hard signals stay on my desk. One, which board first publishes a monthly registration root — not names, a monthly hash. Two, which franchise league puts appearance-fee payments on-chain through an open oracle log, where even academy players get proof of who is reliable. Three, which broadcaster first puts a verifiable timestamp of the scorer's log on air — that is, makes the process itself the content.

I do not predict; I archive the conditions of prediction. Silence has a box score, and every switch of the chain, every quiet correction, is being written on that scoreboard — you only have to know how to read it.

Footnote: sources for this piece — the author's hand-coded 2026–18 dataset; the ICC–FanCraze partnership (2026); official board domestic registration and BPL-related announcements. Match-level figures are drawn from the author's own scoring sheets; they can be questioned, but their dates cannot be moved.