When the Rulebook Is Written on a Ledger: Blockchain, Contracts and the Arithmetic of Trust in Cricket

The Decision Was Made Before a Ball Was Bowled

On July 14, 2026, at Lord's, England and New Zealand finished tied, and then tied again in the Super Over. No whistle blew. A clause did. The playing condition said boundaries would decide, England lifted the trophy, and New Zealand's name went into the cruellest list in the sport's history. Within four months the MCC abolished boundary countback, replacing it with repeated Super Overs. The whistle blew, and the rulebook started breathing.

I have been sitting in that particular seat since 2026, when I misread a soft push in the 89th minute of a Bangladesh Premier League match, called a penalty I should not have justified the way I did, and was quietly corrected by a retired FIFA referee. The sting sent me back through every tape I could find, filling a notebook with clauses and timestamps. That habit brings me to this cycle's real argument. The dispute is no longer only about umpires. It is about registries — where a birth date lives, where a no-objection certificate lives, where a match fee, an injury scan and a selection decision are stored. And a growing number of administrators want to move that onto a blockchain.

The question is narrow. Does a distributed ledger make cricket fairer, or does it simply relocate trust from a boardroom to a server room?

Where Rules Are Written, and Who Sits There

Cricket is governed in three layers. The ICC writes the Laws and the playing conditions. The Asian Cricket Council handles regional tournaments and development funding. National boards such as the BCB control player registration, contracts and domestic leagues. Each layer has the same failure, and it is not a failure of rules. It is a failure of records. The same player's data sits in three places in three forms. If one office forgets to update a 2026 injury report, a 2026 selection meeting acts on stale information.

Every new franchise league multiplies the paperwork: more NOCs, more clearances, more allegations that someone played without permission or without filing their insurance documents. Almost all of these disputes are factual rather than philosophical. Who submitted which document, to which office, at what hour? The problem is that one board's database is not readable by another. Verification happens through letters, emails and screenshots.

A paper process from the last century, answering a question from this one — that is the plainest case for a ledger. Blockchain here is not a currency story. It is a shared, timestamped, tamper-evident book. Registration, NOCs, age verification and transfer windows are the four processes where a mutually agreed ledger would settle the majority of disputes without arbitration. Because the substance of a dispute is rarely memory; it is proof. And the substance of proof is time.

One Birth Date, Four Offices

An old pattern is written in my notebook. A fourteen-year-old enters an under-16 side at six feet one. Within two seasons he is in under-19, then first-class, then a national standby list. His shoulders, lower back and knees cannot read the signboard that says he is not yet finished. Of everything blockchain could touch in cricket, this is the most ethically interesting and the least discussed.

Four things belong on a permissioned ledger: a birth record and registration date that clubs, boards and regional bodies read identically; per-season matches, overs bowled, balls faced and rest weeks; injury history with hashed scan reports, so nobody can later claim a player was never hurt; and workload caps by age band that raise an automatic flag when crossed.

The objection is privacy, and I take it seriously. But the threshold is clear: when information determines a teenager's future, uncertainty hurts both sides. This should not be a public chain. It should be permissioned, consent-based, readable but not editable.

Football has run a transfer matching system for over a decade doing exactly this — registration, age, clearance in one verified place. Cricket has nothing equivalent. In January 2026, two Gulf-funded leagues launched in the same month, six teams each, stacked with international stars. When a clearance takes three days to verify against letters, the league's schedule and the player's wallet both suffer — and the player is always the weaker party.

Smart Contracts and That Letter From May 2026

In May 2026, with stadiums empty, Bashundhara Kings and Dhaka Abahani proposed fifty per cent pay cuts. I obtained a copy of a force majeure letter sent to twenty-four players. FIFA's COVID guidance said one thing; South Asian contract architecture said another. A player called me, crying. I kept his name out of print and rewrote my ending three times.

That experience taught me two things. On paper contracts are equal; in practice they are as equal as bargaining power. And with a proper audit trail, that player would not have needed to cry on the phone. He would have known who sent what, which clause triggered when, and what he was owed.

Smart contracts offer a limited but real fix. Match fees, per-match bonuses, injury cover and fitness-contingent final instalments can be condition-driven. Force majeure itself cannot be automated, because 'undue influence' and 'exceptional circumstances' require human reading. But the second half — was the condition met — is machine-verifiable, and that is where most fights start. Verifiable conditions do not discipline anyone; they clarify who owes what, by when.

In 2026 I watched France v Australia at four in the morning in Chattogram. In the 58th minute Andrés Cunha used VAR to award the first World Cup penalty, for a foul on Griezmann; France won 2-1. I wrote a 1,200-word explainer citing the protocol, it was shared widely, and then I worried I had oversimplified. Technology looks elegant in the rulebook and is held by operators, error margins and broadcast incentives on the field. Smart contracts inherit the same weakness. Feed a machine a false fact and it records a falsehood with perfect precision.

An Anti-Corruption Ledger: Who Knew What, When

Anti-corruption work depends entirely on a timeline. Who changed hotel rooms, when, which market spiked wrongly, who received which message. Today that picture is assembled from betting monitoring, team manager reports, sources, call records and travel data — five systems, five files, six weeks of searching.

One immutable ledger speeds investigations. But here is my deepest doubt, and it is legal rather than theoretical. Blockchain does not stop corruption; it preserves evidence of corruption. If the input is wrong, the chain immortalises the error. That is the oracle problem, and in cricket it simplifies to a single question: who authorised this entry, and what is their record?

So four prerequisites must precede any ledger: a register of who may supply data and with what authority; rules on read, write and amendment rights; a correction mechanism that never deletes but appends, because a cancelled record is itself evidence; and an independent oversight panel with equal player, official and board representation.

The last point matters most. In a 2026 scheduling dispute, two sides called each other untruthful. A ledger would not have prevented that, because no ledger prevents lying. A shared record speeds decisions. It does not give courage to players. It gives comfort to boards.

The Review's Audit Trail: Three Minutes and Forty-One Seconds

Decision Review is my favourite and most suspect invention in the game. Favourite because it makes the law visible; suspect because visibility is not transparency. On the screen the crowd sees ball tracking, an UltraEdge waveform and a verdict. It does not see which source frames were selected, what the waveform looked like before the broadcast cut, or what changed in a two-second gap.

I timed one review. The third umpire's process took three minutes and forty-one seconds. One minute twenty went to frame selection and about a minute to waiting on the broadcast. Players, crowd and even the two standing umpires waited for a cut that might have taken a machine one second. A broadcast-dependent interval has slipped into a process the rulebook never described.

A ledger cannot reduce the delay. It can preserve the decision's full information set. Hash the source camera record, log the frames used, the calibration stamp, the announcement timestamp and the final verdict. Not necessarily public, but preserved — so that next season, when someone asks where that decision went, there is an answer.

And here is my second standing warning since 2026: technology as display and technology as audit are different objects. A ledger does not change where the camera points. It only records who ordered the camera to move. Cricket needs qualified operators, published error margins and an external audit of the review process. The ledger is the best assistant and the worst substitute.

Fan Tokens and Gulf Money

Since 2026, the Gulf and South African franchise leagues have revealed a new truth: cricket no longer waits for capital; capital waits for cricket. In that setting, fan tokens look like a light proposal but raise a heavy question. Does turning supporter engagement into a financial asset deepen the relationship, or convert a fan into a consumer? On the night of a defeat, if the token price falls, is the supporter loyal to the club or to the wallet?

A more practical use sits in broadcast and data rights. Ball-by-ball tracking, injury data and physical markers are already sold to insurers, analysts and broadcasters. Players often do not know who bought their shoulder scan. A consent-based ledger at least tells them where the data went. In Bangladesh's domestic game this conversation has not started, which is remarkable.

Twenty Overs on a Thirteen-Year-Old's Shoulder

I have written this repeatedly, and here it returns as a technology proposal. A physically mature but chronologically young player is pulled upward quickly because he can win a match today. No one keeps a central account of what his shoulder does by eighteen. A match-workload ledger is the least glamorous and most useful application. Every over, delivery, spell and rest week in one verifiable book tells the board what its calendar actually did, tells selectors who has been overused, and — most importantly — gives the player the standing to say 'not now' with evidence rather than memory. That single use is enough reason to explore the technology.

The Contrarian Turn: The Chain Is Only as Trustworthy as Its Operator

Now I argue against my own proposal.

First, a permissioned ledger means an authority decides who joins, reads and writes. In cricket that authority will almost certainly be a board or the ICC. If a board issues a wrong instruction, the chain records it faithfully and permanently. An entry that might have vanished from a filing cabinet stands forever. That is not corruption prevention; it is a corruption museum.

Second, immutability contradicts data protection. Permanent storage of injury or mental health data does not serve the player. A correction-layer model is possible, but it depends on political will, not code.

Third, cost. Running a full ledger needs servers, networks, trained staff and energy. Associate nations, already short of fixtures and funds, would suffer most. Digitisation risks creating a new inequality: rich boards transparent, poor boards more opaque because they lack systems.

Fourth, and hardest: technology delivers truth late, never forgiveness. In 2026 I simplified a protocol and later realised my simplicity had hidden the process questions. In 2026 I rewrote an ending three times because I did not know whether hope was honest. Blockchain storytelling carries the same danger — clean, clear and usually incomplete. I will support a pilot when I see more time spent verifying data sources than announcing the chain.

One voice is missing from every technology debate: the umpires and match referees. Players, boards and broadcasters all get a hearing. The person who decides in one second on the field does not. A ledger can protect officials if it records who ordered what, and why. No data ledger should launch without the consent of match referees and third umpires.

Looking Forward

Three things in cricket depend on paper today and belong on a ledger: registration and clearance, the condition-driven half of payments, and the information audit behind review decisions. The steps are not complicated if the intent is honest — an ICC working group including player, official and associate representation plus an independent data auditor; a limited pilot in one domestic tournament with pre-published success criteria; public read access with restricted write access; a correction process with deadlines written into the playing conditions; and a shared infrastructure fund so associates are not left out.

None of it happens unless supporters push. They will push on the day they accept that the boundary-count rule was written on paper in a hall, and it took a committee meeting to change it. Today the decisions are written in code — registration code, payment code, review code. Who writes that code, who can read it and who cannot will be the biggest legal question of the next cycle. No one in cricket currently knows the answer.

The whistle will blow and the game will go on. But this time the rulebook may not breathe. It may sleep on a server, waking only on a click. Whose hand holds that click is a matter we can still decide.