From Rulebook to Codebook: The Door Through Which Blockchain Enters Cricket Governance

On 17 June 2026, at Villa Park in Birmingham, the first Premier League match after the pandemic shutdown was played. In the 42nd minute, a Sheffield United shot crossed the goal line by 3.7 centimetres, yet Hawkeye gave no goal signal and referee Michael Oliver's watch did not buzz. That night it became clear to me that the blind faith we place in technology is not faith in technology at all—it is faith in the institutions that control it. Cricket stands in exactly that place today. DRS, the third umpire, ball-tracking, Snicko and UltraEdge are all systems in which the decision is centralised and effectively held by one party. It is into this architecture of centralised trust that blockchain is now stepping. Walking the road from The Den to the VAR desk taught me that every roar hides a ruling. Cricket's rulebook grants that ruling its legitimacy. The MCC Laws, the ICC Playing Conditions, the Anti-Corruption Unit's code—these are all ledgers, recording who may do what and who judges it. Blockchain's advocates argue the ledger no longer needs to sit in one hand; a distributed ledger keeps its own proof, and no one can quietly tear out a page. The question is how much of this actually works in cricket, and how much is marketing slogans. The reality is that blockchain's most visible entry into cricket has come through the door of fan economics. Cricket Australia brought digital collectibles to market in 2026, where fans buy ownership of specific moments. Since then, franchise leagues, fan tokens and NFT platforms have followed one after another. These are entertainment and assets—their relationship to cricket's rulebook is indirect. But the real question lies beyond fan merchandise, where the integrity of the game is staked. Consider a match-fixing investigation. Today the anti-corruption unit must rely on phone records, bank transactions, witness statements and internal whistleblowers. Every layer of evidence is centralised, and every layer can be interfered with. If player contracts, payments and certain workflows were placed in smart contracts, an immutable record of transactions would be created. But here is the first gap—the fixer sends money in cash or crypto, not on the blockchain. Where corruption happens, the ledger never reaches. Blockchain proves that what was recorded has not changed; it does not prove that everything that happened was recorded. That distinction is what cricket administrators most need to grasp. Yet where blockchain could genuinely help is data integrity. Modern cricket stands almost entirely on information—ball-tracking, Hawkeye, UltraEdge, Snickometer, Spidercam. A DRS decision depends on the combined output of three technologies, and that output is produced by a private contractor. When a decision is challenged, no one can independently verify which version of the data the umpire or match referee is actually seeing. If every match's sensor data were written to a time-stamped, distributed ledger, no one could later alter that information and build a different story. Investigators, journalists and judges would all see the same truth. Here lies my second objection, and it is the most important. Blockchain does not remove trust; it changes trust's address. A smart contract states that if conditions are met, this will be the outcome. Whoever writes the code is, in that moment, effectively writing the rule. We know this problem in cricket. Who wrote the DRS protocol, what error tolerance ball-tracking has in which version, where the limits of bounce or pitch-mapping lie—these decisions are taken in technical committees, and they are exactly what changes results on the field. Blockchain does not reduce that committee's power; it may obscure the code-writer's power further, because ordinary viewers cannot read a smart contract. Once code becomes law, the code-writer becomes the legislator. The question is therefore ethical, not technical. The biggest risk is of course regulation. If a league creates new revenue streams from fan tokens or NFTs, it will affect player salary structures and revenue distribution. The balance of power between the ICC and member boards is already fraught; who owns digital assets—the board, the franchise or the player—will spark fresh disputes. A clear precedent is needed here, just as exists for salary caps or draft rules. And if player contracts convert to smart contracts, who determines injury and form clauses will become a new battleground. My third objection concerns timing. Cricket decisions sometimes must be made in fractions of a second—an LBW, a boundary line, a run-out. Blockchain's consensus mechanism can be slow, and a delay of a few seconds in a live match means enormous controversy. But where immediacy is not required—ticketing, doping-test records, age verification or multi-year contracts—the immutability of blockchain is clearly advantageous. The technology must be placed in the right spot, not forced into every spot. At the 2026 World Cup I tracked all 29 penalties and every VAR review with timestamps; after that Hawkeye failure of 2026 I wrote a system post-mortem. The lesson was single: machines and humans both err. The difference is only that a human error can be apologised for and corrected, while a system error is often left uncorrected. Blockchain's great promise is incorrigibility; but cricket's history says correction is what keeps the game alive. After the Wembley disorder at the 2026 Euro final, I learned that security and order are a story written in advance—a protocol that must be drafted before anything happens. So the question ahead is not of technology but of administration. Will cricket adopt blockchain? Probably yes—but slowly, and only where trust is built, not broken. The game will be played as before; only the ledger will change. The question remains: who will write this new ledger, and will anyone be able to read it?