From Review Ledger to Blockchain: How Cricket's Decisions Become Legal Documents
**মূল উত্তর (≤৬০ শব্দ):** ক্রিকেটে ব্লকচেইনের বাস্তব ব্যবহার ডিএসআর রিভিউ লগ, ম্যাচ রেফারির সাজার নথি, ওভার-রেট জরিমানা ও প্লেয়ার চুক্তি—এই চার ক্ষেত্রে টেম্পার-প্রুফ, স্বাধীনভাবে যাচাইযোগ্য রেকর্ড তৈরি করা। তবে এটি সিদ্ধান্ত ভুল-শুদ্ধ করে না; ব্যাখ্যায় স্বচ্ছতা আনতেই কাজে লাগে। **মূল তথ্য:** - ১৪ জুলাই ২০১৯, লর্ডস: ম্যাচ ও সুপার ওভার টাই, বাউন্ডারি কাউন্টে ইংল্যান্ড ২৬–১৭ নিউজিল্যান্ডকে হারায়। - অক্টোবর ২০১৯: আইসিসি বাউন্ডারি-কাউন্ট বিধান বাতিল করে সুপার ওভার পুনরাবৃত্তি চালু করে। - ২০০৮, কলম্বো টেস্ট: ভারত–শ্রীলঙ্কা ম্যাচে প্রথম খেলোয়াড়-রিভিউ ব্যবস্থা পরীক্ষা হয়। - টেস্টে প্রতি Inningsে দুইটি, সীমিত ওভারে একটি রিভিউ; বল-ট্র্যাকিংয়ে "আম্পায়ার্স কল" থ্রেশহোল্ড নির্ধারক। - ২০২২-Next সময়ে আইসিসি মাঠেই ওভার-রেট বাধ্যবাধকতা ও স্টপ-ক্লক ব্যবস্থা চালু করে। **সূত্র:** ক্রিকেট রেফারি ও খেলার শর্ত-ভিত্তিক বিশ্লেষণ; প্রকাশকাল: ১৩ আগস্ট, ২০২৬ | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: ডিএসআর সিদ্ধান্তের পূর্ণ কল-চেইন কি দর্শক যাচাই করতে পারেন? উত্তর: এখন পারেন না; কেবল সংক্ষিপ্ত ফলের সারসংক্ষেপ প্রকাশ পায়, কারণ খোলা রেজিস্টার নেই। প্রশ্ন: ব্লকচেইন কি ক্রিকেটে ভুল রায় কমাতে পারে? উত্তর: পারে না; এটি কেবল নথি অপরিবর্তনীয় করে, ব্যাখ্যাকারী বিবেচনায় হাত রাখে না। প্রশ্ন: বাংলাদেশ ও ইংল্যান্ডে একই ক্রিকেট আইনে সাজার পার্থক্য কেন? উত্তর: কারণ আইন এক, স্বচ্ছতা আলাদা — cricsultan.com Match-Officiating Transparency Index এই ব্যবধান মাপে।
Hook: That Night at Lord's, and the Three Columns in My Notebook
On 14 July 2026 at Lord's I closed my notebook with three columns filled in: match number, over, and the clause under which the decision was made. The match was tied, the Super Over was tied, and the title went on boundary count — England 26, New Zealand 17. That night I did not write the word "cruelty" in my review ledger. I wrote: "Playing Condition boundary-count provision — rarely invoked, non-reversible outcome." Four months later, in October 2026, the ICC removed that provision and opened the route to repeated Super Overs.
What a billion viewers read that night as fate was a written clause. A written clause can be changed, erased, and it always leaves a paper trail behind it. The match ends; the paperwork keeps moving. That was my first big realisation: in cricket, much of what happens on the field was already written before the field — in the playing conditions, the Code of Conduct, the match referee's report.
But one question kept nagging: if cricket's decisions really are legal documents, where are those documents kept, and who controls them? The answer is uncomfortable. Much of the record sits on a single central server owned by the tournament organiser. Where the evidence is itself editable, adjudication and trust sit in the same hand.
This piece is about that gap — and about one strange possibility. Almost all blockchain talk in cricket right now is tickets, fan tokens and sponsorship. I am arguing something else: what an open, tamper-proof register could and could not change in DRS review logs, match-referee sanctions, over-rate fines and player contracts.
Context: How Cricket's Decision Architecture Is Built
The current system has layers, each with its own record and none with an independent route to verification. The on-field umpire applies the Laws and playing conditions. The third umpire watches replays. Technology — ball tracking, UltraEdge, real-time snicko — sits beneath him. The match referee writes the report and applies Code of Conduct sanctions. A disciplinary committee or judicial commissioner hears appeals.
Player reviews were first trialled in Colombo in 2026 in the India–Sri Lanka Test. Since then: two reviews per innings in Tests, one in limited-overs cricket. On ball tracking, "umpire's call" is a threshold rule — if the ball is on course to hit the stumps but impact falls under a set proportion, the on-field call stands. The vendor's precision is debated, but the threshold is not public.
My real worry is this. For eighteen years we have argued about DRS outcomes, not about the record. How many components does one review contain? On-field call, data feed, 3D projection, speed and spin, stump position, umpire's-call threshold, and the decision-maker's explanation. How much of that does the viewer see? One replay, one graphic, one word — "stands" or "overturned."
When I built a database on semi-automated offside in 2026, I learned the method. Applying it to cricket, the problem is not technology; it is process throughput. Football at least shows the projected line on broadcast. Cricket shows the full projection rarely and never the threshold number.
Core: Four Layers Where Blockchain Is a Real Question
_One: the review log._ Every DRS review's footage and data sit in the broadcaster's archive; a summary goes to the umpire database. If I ask three weeks later how many millimetres the ball's centre was inside the stump line, I cannot get the answer. Yet tournament fortunes have turned on that single data point.
Imagine each review entered as a hash into an open register — timestamp, review number, ball number, original on-field call, tracking-threshold version, final outcome. Any later edit would break the hash, publicly. Blockchain changes no viewing experience here; it creates knowledge.
_Two: match referee reports and Code of Conduct sanctions._ Over rates, sledging, ball tampering, on-field conduct — settled in a closed room, arranged along a Level 1 to Level 4 ladder. Fine percentages, suspension lengths, appeal grounds — no uniform public record. In a federated ledger, decision, clause citation and sanction would sit together, letting us measure over years how interpretation is applied.
I have repeatedly seen the same conduct yield different outcomes in two countries. Domestic cricket in Bangladesh and county cricket in England impose different sanctions for the same behaviour — not because the process differs, but because transparency does. An open ledger would be a tool to measure that cultural gap.
_Three: smart contracts and automated sanction._ ICC over-rate policy has shifted year after year — from post-match fines toward in-match fielding restrictions, then the stop clock. Legally the idea is simple: fail to bowl the overs in time, take a defined consequence. That logic is codeable. Smart contracts will not please spectators — but they reduce dependence on the match referee as an individual and equalise the expectation for both sides.

_Four: player contracts and free agency._ In domestic leagues and franchise cricket, movement, NOCs, payment clearance and draft order still run on a mix of paper, email and messaging apps. Tracing one league's file, I found the delay and inconsistency came less from technology than from non-uniform documentation.
Contrarian Angle: Blockchain Saves Records, Not Judgement
My professional risk is "codification overconfidence" — assuming that once a process is written down, interpretation stops mattering. It does not.
Cricket's trust crisis is not in the numbers; it is in the explanation. Even if a decision record becomes immutably preserved, human beings still interpret. "Umpire's call" is a policy preference; keep it in a tamper-proof ledger and the policy argument remains. What is broken is not accuracy — it is transparent reasoning. And that lives inside the verdict, not the ledger.
There is a practical problem too: an open register becomes an attack surface. If deletion is impossible, personal data cannot be truly erased, creating privacy risk. No ICC, no Dubai office, no written record is ever politics-free. I learned in 2026, building a VAR ledger in football, that when a system's legitimacy is contested, nobody cares about its data. That applies directly to cricket: if the public does not believe the system is honest, an open ledger will not fix it.
A third obstacle is the officials themselves. They often argue that opening up explanations would destroy "the freedom of instantaneous decision." That is a good argument. But it does not justify secrecy — it justifies a different publication window: not live, but in review. Do not pressure the umpire during the match; publish the full call chain of every decision within three days. That is the plausible compromise.
And one warning: every cricket fan treats DRS as a truth machine. It is not. A perfect record of a weak process is still a weak decision. In my 2026 review log one line still stares back unchanged: "The process was correct; the path to the answer was inverted."
The Diaspora Rulebook: Same Qualification, Two Realities
Take a nearby example. In England, where I work around matches, third-umpire review, technology, ground-staff training and audit culture sit on mature infrastructure. A vendor change becomes news, and contract documents can be questioned in detail.
In Bangladesh, on the domestic circuit, the same cricket laws apply — but it is healthier to acknowledge the infrastructure gap politely. In first-class matches, ball tracking is not guaranteed, and players are still learning review culture. So at home I push a different question: without transparency in decisions, how does my reader separate politics from performance? MCC Laws will not close that gap. You have to go to the layer of club, board and national federation relations. This is why I read review logs, over rates and player contracts differently in the two markets.
Takeaway: The Next Change Is Not Technology, It Is Publication
The real value of blockchain in cricket is not in crypto tokens; it is in the economics of legibility. If a review ledger becomes genuinely independently verifiable, the next generation's cricket argument changes shape: not "he lost the call" but "which data and which threshold produced the call."
I still end my ledger with a question rather than a conclusion: will the ICC ever state publicly that the full call chain of every DRS review over the next five years will be published? If the answer is yes, few results will change — but the basis of fan trust will.
Referee Dot DIR.
— Root: Referee

