Ledger, LBW and Trust: The Limits of Blockchain in Cricket Governance

Chattogram, twenty minutes to three in the morning. Lights off, only the blue of the screen. The replay rolls. Ball-tracking draws a thin white line and sends the ball skimming past the leg stump; a small caption says the ball was hitting, but inside the margin. The on-field call stands.

I freeze the frame.

The question is not whether the ball hit. The question is: who owns this frame? Where was the raw sensor data at 2:47 a.m., before the graphic was drawn? Who touched it, who changed the calibration, and at what timestamp? A review system whose entire legitimacy rests on the claim that what we are shown is neutral truth has no public, tamper-evident, machine-verifiable log behind that claim. At three in the morning, that is a strange place to stand.

I have written many times that the whistle blew, and the rulebook started breathing. Tonight the whistle does not blow. Tonight a ledger has started breathing.

In the last two years the word "blockchain" has entered cricket's corridors — sometimes through ticketing, sometimes through fan tokens, sometimes through player registration — and it arrives with the posture of bringing extra trust. My position is not easy, because I am not against technology. In 2026, watching France against Australia from Chattogram at four in the morning, I wrote a 1,200-word explainer on the first VAR penalty of a World Cup, citing IFAB's Article 3. It was shared 50,000 times; coaches and referees read it. I celebrated quietly, then feared I had oversimplified. That fear is why this piece exists.

Context: who writes, who reads, who verifies

Cricket's governance looks simple and is layered. The ICC sits in Dubai, with an Integrity Unit whose predecessor was the Anti-Corruption Unit, renamed in 2026. The Asian Cricket Council sits in Kuala Lumpur. The Bangladesh Cricket Board sits in Dhaka, and every country has its own board. Above them float the franchise leagues — the IPL, the BPL, the ILT20, the SA20, The Hundred, the CPL, Major League Cricket. The most important document moving between these layers is the NOC, the No Objection Certificate. If a player wants to play abroad, his home board issues a piece of paper. With it, he plays; without it, he does not. Who holds that paper, for how long, on what terms — that is, in practice, cricket's border control.

And the money? Central contracts, auction purses, appearance fees, image-rights deals, sponsorships — almost all of it a board-controlled private ledger. The player knows what he is paid. He does not see the whole picture. The fan never does.

That gap built a market for blockchain. Sport let the technology in through several doors. Socios fan tokens, built on Chiliz, were sold under the names of Barcelona, PSG and Juventus. NBA Top Shot, on the Flow blockchain, and Sorare built markets in digital cards. Cricket followed: in 2026 the ICC announced an NFT partnership with FanCraze; in 2026 FanCraze reportedly raised a $100 million Series A led by Insight Partners. Rario signed with Cricket Australia in similar fashion. On ticketing, European club football ran blockchain pilots, most of which ended as quiet failures.

Then came 2026. Terra collapsed, and in November FTX went bankrupt — the same company that had bought an arena's name. Trust in crypto brands broke, and sports sponsorship money withdrew. So in this 2026 moment, the word "blockchain" enters a cricket board's meeting room carrying an odour.

I am not the reader of a token sale. I am the man who asks for the clause. So the question here is not whether blockchain will save cricket. The question is: cricket's trust deficit, which we argue about every day — what kind of deficit is it? A cryptographic one, or a problem of publication?

Core: what a ledger does, and what it cannot

Start at the foundation, because that is where the greatest misunderstanding lives. A distributed ledger has four properties: it is append-only, so old entries cannot be erased, only added to; it is replicated across many copies; every entry is bound by a cryptographic signature; and consensus makes all copies agree.

Notice that none of the four says the entry is true. A blockchain does not verify truth; it only makes a claim to truth permanent. This is the oracle problem — before real-world data enters the ledger, someone reads and writes it down, and that written line becomes final. The weakness is not at the technological layer but in the writer's hand.

With that in mind, four domains in cricket.

One: player registration, NOCs and agent commissions. Imagine each NOC as a signed entry — which board, on what date, permitted which player, in which league, for how long. The same ledger holds the agent's registration, the commission rate, the contract's term. Third-party ownership, which FIFA banned in 2026, could not hide. Dual contracts, shadow deals, the quiet sale of a player's economic rights without his knowledge — all of it would leave a visible trace.

But here is the first trap. If the board alone writes to the ledger, it is not transparency — it is a digital seal. The registry only becomes meaningful when an independent custodian holds write access — a joint key among the ICC, the players' association FICA, and the league organiser. Otherwise we move from a paper NOC to a hashed NOC while the power relation in between remains untouched.

Two: integrity, reporting and chain of custody. October 2026. Shakib Al Hasan was sanctioned under the ICC Anti-Corruption Code for failing to report a bookmaker's approach in time — a two-year ban, one year suspended. The failure there was a failure to report, not a failure of any ledger. Bookmaker money moves in cash; a ledger will not see it.

Yet there is a narrow, real benefit. Between the Integrity Unit, betting-market monitors, boards and law enforcement, information moves by phone, email and meeting. When disputes later arise, memory must be trusted: "we informed them on the 9th"; "the board says the 14th." A timestamped, signed, append-only record can end that argument. When a suspicious market alert arrived, who saw it, who forwarded it to whom — all of it is bound into the chain of evidence. Whether in the 2026 IPL spot-fixing investigation or the 2026 Al Jazeera sting, where the timeline of evidence itself was questioned, hash-stamped records would have helped.

I want to state my own boundary clearly. Better chain of custody makes investigation easier; it does not create jurisdiction. A blockchain cannot move a matter from suspicion to judgement; only rules, investigation and a hearing can. Technology can only keep the process honest.

Three: DRS and data provenance. Here the subject deepens. Ball-tracking, UltraEdge, Real-Time Snicko — these technologies sit with ICC-approved providers. Sony acquired Hawk-Eye in 2026; Virtual Eye is a separate provider. But the raw data lives with the provider and the host broadcaster. Domestic boards and match referees receive only the final graphic and a report.

So what can a fan verify? He sees a projection. There is a difference between a projection and a photograph. The ball-tracking line is not a photograph of the future; it is a model with a declared error budget. The very idea of "umpire's call" is that declaration — if the ball is shown striking within the margin, the on-field decision survives.

The central question of a review system is not one of technology but of design: who holds the raw data, how long it is kept, and how much is published. At the 2026 ODI World Cup, DRS was in place across all 48 matches, as in the 2026 and the current 2026 T20 World Cup cycle. Yet nowhere is there a match-by-match, public "birth certificate of data": this camera, this calibration file, this session's raw data, this hash.

Imagine the ICC hashing and publishing the raw data and calibration logs of every review session after each match. Not one decision changes. But the argument on social media the next day changes. Today we either believe the graphic or we do not — an emotional judgement either way. Then it becomes a documentary one.

One more thing: a failed review costs a team its review. That is not a limit of physics; it is a design choice. How many reviews a side gets, which errors cost it one — that is governance, not engineering. A ledger changes nothing here; the decision is made in a boardroom.

Four: money, tickets and fan tokens. Against duplicate scans, counterfeit tickets and touting, an immutable ledger helps. The hard problem is touting itself and dynamic pricing — there, the decision is policy, not technology. Who gets a ticket at what price, which club member gets priority — not a blockchain question.

My objection to fan tokens is sharper. In a fan token, the supporter does not buy governance; he buys a share in a promise, priced by the market, with the risk carried by himself. The club receives a fixed income; the downside lands on the fan's shoulders. The 2026 collapse showed the risk flows downward. In cricket, where domestic leagues run on ticket money, pushing derivative risk onto the fan is not partnership.

Five: who runs the nodes. The biggest question of a consortium ledger is constitutional, not technical. Who gets write access? Who can read? What is the correction path — old entries cannot be deleted, but who may append a correction? Where does personal data live, and where must it never live? Medical records, data on minors, anti-doping whereabouts — none of that belongs on a public ledger.

And here is my most personal worry. Cricket has developed a bad habit: because a teenager's body is not yet finished, a brilliant spell is followed almost immediately by senior rhythms — central contract, franchise call-up, social-media hype. If a ledger publishes that player's contracts, call-ups and fees, the gain comes only if we remember that what is being recorded is part of a human life. Before the ledger, the question should be: who gets hurt?

Contrarian: cricket's problem is publication, not cryptography

Now let me stand against my own position, because this piece is not a memory aid for anyone.

First objection: cricket's laws breathe, and ledgers do not. In the LBW law, in the culture of on-field observation, even in the declared margins of the playing conditions, cricket deliberately leaves room for doubt. Discretion lives between what the player intends, what the pitch does, which way the wind blows. Blockchain's secret promise is finality. Cricket needs revisability. If a board errs and the ledger cannot delete the error, the ledger becomes a monument to error. There is a solution — append a correction — but then the ledger is no longer a book of truth; it is a history of disputes. That is still valuable, but far less romantic.

Second objection: audit theatre. A board can buy a blockchain, publish a daily hash, and claim complete transparency while nobody can read it. Transparency is not cryptography; transparency is legibility. A document that an ordinary journalist or fan cannot read is no better than secrecy.

Third objection is the counterfactual test. If a blockchain had existed, which incident would not have happened? The 2026 IPL spot-fixing? No — the money changed hands in cash, the suspicion was born in rooms and phone calls; that investigation was built on wiretaps and testimony, not hashes. The argument over the first VAR penalty in 2026? No — that was a correct on-field decision. So what exactly would blockchain have changed?

The narrow, honest answer: cricket's trust deficit is not a cryptographic problem; it is a publication problem. The cheapest trust upgrade available to the ICC is not a chain but a changelog. A board that publishes the reasons for its decisions, admits its errors and records its corrections over time earns trust without any ledger at all.

None of this means discarding the technology. It means reversing the order. Decide first what you will publish; then decide how to store it. Blockchain can be the plumbing. It must not be the pulpit.

Takeaway: when the next review goes upstairs

The calendar ahead gets denser, not lighter. Franchise leagues multiply, bilateral series pile up, and cricket's return at the Los Angeles 2028 Olympics adds a new layer of scrutiny — the Olympic movement's anti-doping and integrity standards, where the demand for accountability is far stricter. Between 2026 and 2028, the demand for data disclosure in cricket will rise, and today's arrangements will look old against it.

So my expectation is that the first pilot will not come from the ICC. It will come from a mid-tier franchise league's ticketing, or from a bilateral NOC registry — where risk is low and politics is easier. That is not bad news, because small trials teach the real lessons.

I would want the ICC to issue a Data Provenance Standard. The economics are simple: for every match, a signed, time-stamped certificate covering the calibration logs of the technology used, the raw data of every review session, and the final graphic. It can be done with a ledger. It can be done with a file. Either way, one principle should hold: the path of correction stays open, but the history of corrections accumulates. Just as the game does not decide without evidence, the evidence should learn to show itself.

And I leave the last question open. When the next review goes upstairs and ball-tracking draws that thin line, who will be the witness — the ball, the algorithm, or the board?