Cricket's Audit Trail: Money, Data and the Blockchain Ledger

Last month I sat in a Mymensingh gallery with a small notebook and drew two columns. I wrote “what is being claimed” at the top of one, “what has been verified” at the top of the other. By the end of the match the first column had almost filled up — boundaries, overs, who bowled what, which over the game turned. The second column stayed white as paper. That white column is the real subject here.

Because this week I was handed a document that looked like professional analysis — title, tables, eight chapters, sub-headings under every chapter — and contained not a single fact. Every cell read “insufficient information.” No match, no player, no team, no board, no tournament. Yet the document kept calling itself “deep professional analysis,” as if a title and a table were enough.

I went to Mymensingh to count passes and left counting excuses.

In cricket right now, an empty document that looks like data is more dangerous than false data. False data gets caught. Empty data doesn't — it slips quietly into decisions and sits there.

Context: where the money lives, and who keeps the books

I have written about Bangladesh's cricket economy for years and hit the same wall every time. We roughly know where money enters. We have no solid structure to verify where it goes. I have watched games in Mirpur, counted crowds in Sylhet, gathered local league cost sheets in Mymensingh. The gap is identical everywhere.

Take the accounts of staging one international match. Gate tickets, sponsorship, TV production bills, central contract installments, player match fees, umpire honoraria, security, hotel allowances. Much of this still moves on paper, in email, in separate Excel files. A board's financial report comes out once a year, and its credibility rests largely on the board's own goodwill.

Reported figures put the ICC's sale of Indian-subcontinent media rights for the 2026–2027 cycle at around three billion US dollars. When that volume flows through one pipeline, the question is no longer just who won. The question is who verifies what share went where, by what method.

The same story runs through central contracts. Players sign at the start of the year, but when installments arrived, how much tax was cut, how much match fee was deposited — that final truth usually stays between the player and the board's accountant. In franchise leagues it is starker: delayed-payment complaints have surfaced in the press across many seasons, and the board line is always that the matter is “under process.” “Under process” may be the most expensive phrase in cricket; it can bury years.

Tournament allocations, hosting rights, revenue-distribution models — all of it is negotiated between the ICC and member boards. Who sits at the table and who is excluded is politics. But if nobody can independently verify the numbers on that table, “transparency” becomes a slogan hung on a stage every annual meeting.

My problem is not with philosophy. My problem is with receipts. And in cricket you can gather receipts; you cannot staple them back together.

Core analysis: what blockchain actually solves

There is a fashion in cricket circles now. It sounds as if dropping in a distributed ledger will erase corruption, delayed payments and murky accounts. I don't buy that. I also don't buy the opposite — that blockchain is mere advertising for cricket.

The real point is this: blockchain's one great property is that an entry, once written, cannot be quietly changed, and a trail remains of who wrote what and when. Each block carries a cryptographic fingerprint of the previous block; altering an old entry means altering every block after it, and the rest of the network catches it instantly. In cricket, where the central anxiety is whether the paper changed overnight, that single property is enormous.

It can stand up in three places.

First, player payments. Smart contracts for central or franchise wages are conceivable — once conditions are met, the amount releases on a set date, and nobody can say “later” by hand. The triggers live in code: match fees per appearance, bonuses per performance, travel allowances per day. It protects the player and gives the board a record it cannot later dispute.

Second, attendance and revenue records. Tickets sold, bodies in the stands, sponsorship secured, jerseys moved — if these numbers sit in a distributed ledger, the gap between official accounts and reality narrows. The crowd I counted in Mymensingh never appears in official reports at that number; when two figures exist, nobody bothers to ask which is true.

Third, integrity and oversight. Anti-corruption investigations need a safe, time-stamped way to log communications, suspicious betting patterns, odd movements. Blockchain is not the police there, it is the ledger. But that ledger can later stand as evidence, because nobody can claim the record was lost.

One distinction matters above all: public versus permissioned chains. If a board stands up a private chain inside its own walls and calls it transparency, that is just another internal database — expensive and shiny. And that is the most likely outcome, because a board under scrutiny finds it most convenient to keep its own books in its own closed ledger.

Possession without territory is just a receipt for a meal nobody ate.

The same rule applies to information. Technology alone does not audit. Auditing happens when writing and verifying sit in different hands. When you write and verify your own accounts, what stands between them is not accounting — it is an excuse.

And this is where the empty document teaches its lesson. An analysis with no facts inside is all performance: its tables, its headings, its “depth.” Conversely, if unverified data is written to a blockchain, we have simply placed bad data on an immutable ledger. Blockchain does not make data true; it makes data tamper-resistant. An immutable wrong number is not less wrong — it is permanently wrong. Miss that distinction and the whole conversation is pointless.

Speed matters too. Every blockchain transaction costs time, energy and consensus. During a live tournament, thousands of ticket scans, catering bills and security contracts in real time would strain any chain. The practical answer is usually hybrid: daily accounting on normal systems, with a daily or weekly summary anchored to a chain. Not everything rises to the chain, but the proof that “this was the state of the accounts on this date” survives.

Then there is player control. No-objection certificates, franchise windows, international calendars — caught between all three, the player is often the one squeezed. If it were public and verifiable who paid whom, and under what playing conditions, much of the board-versus-league blame-shifting would shrink. A board could no longer say it didn't know.

And I keep seeing a venue-level gap. The same tournament reports two different crowd figures at two venues, two pitch reports, two revenue accounts. Decide from one venue's data and the other vanishes. So anyone invoking blockchain must check at least two venues, two seasons, two formats — otherwise it is just another “I saw it with my own eyes” argument.

The counter-argument: where I could be wrong

I know the weak points of this piece, and I won't hide them.

Suppose blockchain is installed and payments and records become transparent. Does that change cricket's power structure? Probably not. The problem is not technology; it is incentive. Anyone can run a “transparent” chain while keeping off-chain dealings going — gate cash, cash sponsorship, informal agreements. Technology can only capture money someone agrees to write down. Money that is never written has no ledger, chain or not.

The transfer market is not a market; it is a theater with accountants in the wings.

A second weakness: cricket governance is international. BCB accounts, ICC distribution, franchise ownership — different legal structures, different geographies, different cultures of secrecy. A chain crossing borders collides with privacy, data sovereignty and players' personal information. Putting player salaries on a public chain is not transparency; it is surveillance. Drawing that fine line between public and private is not easy.

Third, however good a chain is, if the validators are the board's own people, we get staged transparency. Real auditing requires that the party writing the ledger and the party checking it are not the same family. In cricket the opposite happens: the board writes, the board's committee verifies, and anyone who asks gets their credentials questioned.

None of these three objections breaks the argument; they set its limits. Blockchain is not a substitute for cricket governance — it is a tool. And a tool matters only when paired with an independent verifier, an honest question and a journalist who isn't afraid. Changing the format does not change the structure; changing the ledger does not change the power. Power changes when incentives change.

Takeaway: no verification, no ledger — only an excuse

So here is a benchmark you can use in the coming years, and one I will use myself.

My prediction: within five years, at least one major cricket board will announce a blockchain-based ledger for player payments or ticket revenue. The announcement will be glossy, there will be photographs, and the word “transparency” will appear repeatedly — even on the cover of the annual report.

But the question will be one: can an outsider independently run a node and verify that chain? Can someone reconcile the books themselves and say, “this entry was here, and still is”? If the answer is no, it isn't blockchain — it is a shiny spreadsheet with paint on it.

With data, a ledger means something. Without data, a ledger is only an excuse. And until cricket's two columns — “what is being claimed” and “what has been verified” — stop being separate, we will sit in the stands counting blank paper. And a blank sheet, however beautifully ruled, never becomes a receipt.