From Asia Cup Reserve Days to Blockchain Ledgers: Who Writes Asian Cricket's Decision Tree?

Hook: Two Days in Colombo

On 10 September 2026, at the R. Premadasa Stadium in Colombo, the Asia Cup Super Four match between India and Pakistan was interrupted by rain and carried over to the following day. On 11 September, on the reserve day, India posted 356 for 2 and beat Pakistan by 228 runs. Virat Kohli finished 122 not out; KL Rahul made 111 not out.

That week, more column inches went to a protocol clause than to the cricket. The question was simple: why was a reserve day scheduled only for India-Pakistan matches and the final? Pakistan's team director at that tournament was Mickey Arthur. His remarks travelled quickly through the press, and the issue hardened into a single argument: why does one specific fixture get a different rule?

The exception was written into the Asian Cricket Council playing conditions. It was not hidden. The question that remained was different: for whom was the exception written, and who paid for it? After the grand final, I stopped arguing and started documenting. This is one of those documents.

Context: Who Writes Asia Cup Rules, and Who Signs Them

The Asia Cup is a regional tournament, but its governance is not purely regional. The Asian Cricket Council drafts its own playing conditions, clause by clause. Those clauses sit on top of the ICC standard playing conditions and are then amended for local need. Amendment is normal. The real question is where the reasoning behind an amendment is recorded.

The 2026 Asia Cup was staged under a hybrid model. Pakistan hosted four matches, in Lahore and Multan. The rest were played in Sri Lanka, at Pallekele and Colombo. India would not travel to Pakistan, a position approved at an ACC meeting in June 2026. A hybrid model is not only a split of venues. It bundles broadcast windows, team travel, sponsor commitments and crowd attendance into a single negotiation, with four different interests inside it.

There is a structural difference between ICC event playing conditions and regional event playing conditions. At ICC level, clauses are drafted over long cycles, amendments carry explanatory notes, stakeholders are consulted, and the revision history is published. At regional level, decisions are often made quickly, and the reasoning disappears with the tournament. That is the first gap: the rule survives; the explanation does not.

This gap is not new to Asian cricket. Since the introduction of the Decision Review System, disagreement between boards over review thresholds, ball-tracking margins and the preservation of umpire's call has repeatedly surfaced mid-tournament. The 2026 Asia Cup was again staged under a hybrid model, in the United Arab Emirates. The venues changed. The shape of the decision tree did not.

Core: A Four-Layer Replay

The rulebook is a map; the match is the territory I walk. To understand the reserve day question, four layers have to be opened.

Layer One: The Document

In the 2026 Asia Cup playing conditions, a reserve day was attached to the India-Pakistan Super Four fixture and to the final. No other match had one. From outside, that reads as favouritism. From inside, it reads as broadcast risk management. The broadcast and advertising value of an India-Pakistan fixture approaches the combined value of the rest of the tournament. If rain washes out that one match, the loss lands on the event owner. The reserve day is insurance against that loss.

The flaw is that the insurance was purchased in the language of rules, not the language of contracts. Written as a contract, it would say plainly: because of this specific broadcast value, this specific fixture carries a reserve day. Written as a rule, it invites the obvious counter-question: are the other matches worth less, and therefore allowed to get wet? The fact that no reserve day was attached to earlier knockout-stage fixtures answers that question.

Layer Two: The Decision Tree

I write incidents as decision trees: incident, applicable clause, review threshold, outcome. Here the tree runs like this.

Step one: who proposes the clause? The tournament technical committee. Step two: who approves it? The ACC executive body, one vote per member board. Step three: who can veto? No single board holds a veto, but blocks of boards do. Step four: who absorbs the loss? The board whose fixture has no reserve day but carries genuine rain risk.

The awkward detail is that the Pakistan board was part of the June 2026 approval process for the hybrid model. The clause was not written behind its back. But sitting at the table is not the same as tracing the origin of a decision. A board that accepts a package accepts its individual clauses in the same motion, without the chance to audit every word of every clause separately. An unexplained rule shifts power; a rule with a published explanation blocks that shift.

Layer Three: Technology, from DRS to Blockchain Ledgers

Asia Cup matches use the Decision Review System, with two reviews per team per innings. Ball tracking, UltraEdge and zing bails all apply. The technology makes decisions checkable, but it does not change who owns them. Whether a review is preserved or discarded is still written by people.

This is where blockchain enters. At present, no major Asian board records amendments to playing conditions on a public ledger. What exists sits elsewhere. In 2026, the ICC partnered with FanCraze to launch digital collectibles branded Crictos, built on the Flow blockchain, according to reports. Fan tokens, NFT ticketing and franchise league payment flows have been trialled since. At the governance layer, blockchain use in cricket remains peripheral.

The concept is still relevant, because the underlying problem is identical. Blockchain's core claim is that once an event is written, it cannot be altered, and who wrote it and when is visible. Cricket needs exactly that property for playing conditions, code-of-conduct rulings, match referee decisions and tribunal outcomes. A version-controlled ledger would show which clause changed, when, on what reasoning, who requested it and who approved it.

Smart contracts could go further. Player payment terms, match fees, bonuses and injury clauses written as programmable conditions reduce the room for individual interpretation. But the caution is critical: a blockchain proves that a record has not been altered; it does not prove that the record was true when it was first written. In technical terms, this is the oracle problem. If a match referee's report is wrong, the blockchain stores that error immutably, more credible and more permanent than before.

So the real question at the technology layer is never whether to use blockchain. It is: who verifies the source data, and where does that verifier answer for it?

Layer Four: The Numbers

A regional tournament's decisions are not only cricket decisions; they are revenue decisions. Broadcast value for an India-Pakistan fixture, stadium capacity and rainfall probability, placed side by side, explain the reserve day clause without any need for argument. Colombo in September 2026 carried meaningful rain risk, and the tournament clause anticipated it. Because it anticipated it, the exception was written.

A pattern is worth noting. The 2026 Asia Cup was played in the UAE, where rain risk is near zero, and the reserve day debate barely existed. In 2026 Sri Lanka brought rain and the debate. In 2026 it was the UAE again. The controversy is not a function of the rule; it is a function of geography. The rule stays constant; when geography changes, the fairness of the rule changes too, which proves the rule was written for the calendar, not the cricket.

Contrarian: Emotion Versus Rule

Now to the part colleagues usually skip.

The reserve day debate was conducted almost entirely in the language of emotion: bias, injustice, one rule for one country. I do not dismiss that emotion. But audited, a large part of it is about visibility rather than fairness. The board without a reserve day loses not only cricket; it loses qualification probability. And nobody has published what that probability was worth against the price the event owner was selling it at.

The second uncomfortable truth is that in a DRS-driven game we are loud about consistent application of laws and quiet about consistent governance. The same broadcast deal, the same sponsors, the same calendar, the same economics decide the clauses. We discuss the outcome of a clause; rarely its birth.

There is also a specific risk in blockchain talk. When a governing body wants to avoid accountability, it reaches for the vocabulary of transparent technology. An NFT drop or a fan token creates the image of modernity. If amendments to playing conditions are not published, transparency has not increased; only the display of it has. The quietest matches often carry the loudest rule violations. I have heard that sound in an empty stadium.

Takeaway: If the Decision Tree Goes Public, Who Blinks First?

Based on my years of watching matches, one thing is clear: Asian cricket's weakest link is not its players. It is its documentation.

What should happen is not complicated. The Asian Cricket Council can maintain a version-controlled, publicly accessible, timestamped log of playing conditions for every tournament: which clause was written when, who requested it, who objected, and how the approval vote ran. That log does not require a blockchain; as pure policy it works. Blockchain adds one property only: it is hard to rewrite.

Beyond that, DRS data, ball-tracking margins and appeal thresholds should be released as open statistics, by country, by bowler, by umpire.

And then comes the question no press conference answers: if a regional board began publishing every rule amendment in public, whose discomfort would surface first, the person selling the broadcast rights or the board sitting at the voting table?