The Scorecard Nobody Audits: Cricket Data, Blockchain and Bangladesh's Arithmetic in the Asia Cup Cycle

The Scorecard Nobody Audits: Cricket Data, Blockchain and Bangladesh's Arithmetic in the Asia Cup Cycle

The Same Over, Three Different Totals

In December 2026, at the Zahur Ahmed Chowdhury Stadium in Chattogram, I sat through a BPL match with a handwritten ball-by-ball sheet in front of me. The broadcast graphic showed nine runs off one over. One app showed eight. Another showed ten. The reasons were not poetic: a leg bye, a wide on a free hit, and a mis-field that three feeds assigned to three different bowlers.

For anyone who treats cricket as a game of sixes and fours, three runs is noise. For the person writing the last column on a selection spreadsheet, those three runs are the difference: in run rate, in net run rate, and in which team advances. A limited-overs innings has 120 legal balls. A dispute over ball-counting is a dispute over the arithmetic that decides a tournament.

The real blockchain question in cricket is not fan tokens or digital collectibles. It is this: who keeps the ball-by-ball ledger, who verifies it, and what happens when someone quietly changes it.

The xG map said 2.7, but Burnley scored three — the gap between model and result is the story. In cricket that gap is created one step earlier: if the data feeding the model comes in three versions, how honest is the model?

— Root: Chattogram xG blog after Burnley

Context: The Asia Cup Cycle, Scoring Discretion and the Data Economy

Bangladesh's Asia Cup Arithmetic

In 2026, Bangladesh reached the Asia Cup T20 final in Mirpur, where India won by eight wickets. In 2026, in Dubai, Bangladesh lost the ODI final off the last ball, India winning by three wickets. Two finals, two defeats, and on both occasions the match was dragged to the final over before the trophy slipped. Those two finals fixed Bangladesh's position in Asian cricket: a semi-final-standard side, not a trophy-standard side — and the distance is measured mostly in run rate and final-over decisions.

The T20 edition of the Asia Cup was held in the United Arab Emirates in September 2026, where India beat Pakistan by five wickets in the final. The 2027 edition is expected to return to the one-day format. Between those two cycles, Bangladesh has two jobs: fix the T20 structure, and fix the data structure. Nobody talks about the second, though the first depends on it.

Scoring Was Never Neutral

We treat the scorecard as a court verdict. In practice it is a document written by a person who must make six or seven judgments per ball: is the delivery legal, who gets the runs, how are byes and leg byes separated, was it a drop, to whom is a run-out credited, is the strike rotation correct.

Official scorers make those calls, and their decisions fix the data feed. Broadcast graphics and online scorecards both ultimately use information from the same human hand, often at different times and in different revisions. Where a correction follows, two feeds disagree for minutes; anyone who screenshots that moment and posts it makes the wrong number permanent.

Plain-Language Summary Box

• Ball-by-ball ledger: a separate record of every delivery, from which runs, wickets and overs are built.
• NRR (net run rate): runs scored per over minus runs conceded per over; the group-table tie-breaker.
• Blockchain: a record held by many parties, where changing one entry changes every later hash, so the change is visible.
• Smart contract: a contract that executes itself when conditions are met, such as a fee released after a set number of matches.
• Oracle: the door through which outside information enters the chain; the biggest weakness.

My Method

I began cricket writing in 2026 covering the Wills Cup in Dhaka, and my habit came from football: build the xG, shots-on-target and PPDA table first, write second. In cricket that habit became the ball-by-ball log. From Chattogram I have kept logs of limited-overs matches for four years, comparing multiple feeds and noting every discrepancy separately.

— Root: Experience 2 and xG dissection for a first paid column

Core Analysis: Four Data Layers, and Where Blockchain Sits

Layer One — The Ball-by-Ball Ledger

Every cricket number rests on one layer: the ball-by-ball ledger. Each event carries four compulsory elements: ball number, bowler, batter, and outcome. If one value here is wrong, everything above it is wrong.

Take a straightforward chase. Suppose a side makes 171 in 19.2 overs.

• 19.2 overs = 116 balls; run rate = 171 × 6 ÷ 116 = 8.845
• If one feed counts an additional delivery as a legal ball, the count becomes 117, giving 171 × 6 ÷ 117 = 8.769
• Difference: 0.076 runs per over

Across one match, 0.076 is nothing. But in Asia Cup group tables, the NRR gap between first and third has repeatedly fallen between 0.05 and 0.15. A disputed ball count can reorder a group.

A single uncertainty in the ledger can change a tournament's outcome — that sentence is not new to cricket, but nobody audits it.

Layer Two — The Event Layer

This is tracking: ball speed, line, spin revolutions, footwork. The problem here is not technical but proprietary. Who owns this information — the board, the broadcaster, or the technology supplier? When the Bundesliga returned to empty stadiums in May 2026, distance covered became a new benchmark: Bayern 118.6 km against Schalke's 112.3, and a PPDA of 6.2 against 14.8. Cricket had its equivalent crisis when matches continued without crowds; boards held the keys to tracking data, and the metrics that now define player marketing were built then.

— Root: Experience 3 and empty-stadium metric work

Layer Three — The Broadcast Layer

Broadcast graphics exist to entertain, not to audit. Numbers are rounded, time is saved, decisions are made quickly. Treating this as a data source is a mistake, yet fantasy leagues and auction valuations lift numbers straight from it.

Layer Four — The Commercial Layer

This is where cricket data has genuinely met blockchain: fan tokens, digital collectibles, ticketing, contracts. In November 2026, a licensed digital collectibles partnership with the International Cricket Council was announced, covering tournament-based digital items. Cricket Australia announced a similar collectibles partnership in 2026. These ventures convert fan emotion into an asset.

Blockchain's first brilliance and its first trap sit here together. If a token is written on-chain, ownership, supply and transfer become verifiable — a genuine benefit. But the operative truth of cricket, who scored how many, is not verified there.

The Ledger Inside the Tie-Breaker

Asia Cup group qualification rests on three rules: points, then NRR, then head-to-head. The first two sit directly on the ball-by-ball ledger.

An example. A side's group scores: 162/6 (20), 148/8 (20), 171/4 (19.2).

• Match one: 162 ÷ 20 = 8.100
• Match two: 148 ÷ 20 = 7.400
• Match three: 171 ÷ 19.333 = 8.845
• Aggregate: 481 ÷ 59.333 overs = 8.107

If the disputed delivery in match three is counted as a legal ball rather than a wide, the aggregate becomes 481 ÷ 59.5 = 8.084. The difference is 0.023. When two teams are separated by 0.02 on the group table, that 0.023 is not a number — it is a semi-final ticket, resting on one person's pen with no independent audit.

What Blockchain Can Actually Do Here

Three limited but important things.

First, a tamper-evident audit trail. If every entry is hashed with a timestamp and each entry carries the previous hash, changing one value breaks the chain. Correction remains possible; quiet alteration does not.

Second, multi-party consensus. If boards, broadcasters, scorers and match referees write to one ledger, two feeds diverging becomes less likely. Differences that remain are recorded, not hidden.

Third, conditional contracts. Payment delays in domestic franchise leagues are a years-old complaint. If a contract's terms are coded — a fee released on a set date after a set number of matches — the need for an intermediary falls. Two conditions apply: the escrow trustee must be a real bank, and no single party should hold the power to edit the ledger.

— Root: ESTJ rigour and Data Monk discipline

Methodology Caveat

I am not claiming blockchain solves scoring. I am claiming that a simple problem — singular uncertainty, unaudited — which affects both tournament outcomes and player incomes, has a viable partial fix within reach. The rest is governance.

Auctions, Valuation and Dressing-Room Numbers

Franchise auctions now price players on strike rate, economy, powerplay runs and death-over boundary percentage. Those numbers come from the ball-by-ball ledger. If the ledger is wrong, the price is wrong, and the price sets a three-year contract ceiling.

One misallocation is visible: auction models overpay for youth potential and price dressing-room chemistry at zero. A 22-year-old with a powerplay strike rate of 142 gets a rating; the senior who has coached younger players for 50 matches and makes calm decisions in the last over has no column. In Bangladesh this is obvious: our biggest matches are usually decided by experienced hands, not by novelty in the numbers.

That is not a case for anti-metric romanticism. It is a case for adding dressing-room variables — continuity, language, decision rate under pressure, bowling economy after a dropped catch.

Bangladesh's Case From Chattogram

I have watched domestic cricket's data disappear. In club matches, two teams keep two sets of books; the next day a newspaper prints one number, and that becomes history. A player cannot prove the correct ball count or strike rate of his best innings, because the proof was on a thermal printout that was thrown away.

Two consequences follow. First, domestic players never build a proper market value. International auctions see them only through televised matches — a tiny, biased sample that sets their rating and therefore their income. Second, suspicion becomes unverifiable. Where scoring is uncertain, fixing cannot be proven and dishonesty cannot be caught. Both are damaging: the innocent are easy to suspect, and the guilty are easy to protect.

Fan Tokens, Women's Cricket and the ESG Shell

Fan tokens and collectibles are sold under the language of inclusion — the fan as stakeholder. The arithmetic shows a token holder typically receives no revenue share. He buys a verifiable slice of sentiment that creates no leverage over a franchise's assets.

Women's cricket shows this model most clearly. In some cases the women's league is used as proof of corporate social responsibility — filling a page in an annual report while broadcast standards, pay structures and ground facilities never reach parity. Here the problem is not the token but the person. When inclusion becomes decoration, every digital initiative becomes a dressed-up slogan. The question to ask is simple: what percentage of revenue returns to players and coaching staff? If the answer is not in numbers, the exercise is a technology veneer.

The Empty-Stadium Lesson

During the pandemic I learned something that applies directly to cricket's blockchain debate. With stadiums empty, whatever could be measured gained importance: distance, sprints, PPDA, ball reset time. What could not be measured — atmosphere, pressure, boardroom decisions — vanished from view.

Blockchain risks the same trap. What is easy to record will be recorded; what is hard but more important — the reasoning behind a purchase, the balance of a selection — will stay outside the ledger. We will then hold a perfectly verified, incomplete picture, and everyone will call it truth.

Exception Log

Exception one — Rain and DLS. Blockchain can verify scoring, not weather. Rain-affected chases use the Duckworth-Lewis-Stern method; revisions to the resource tables are not logged anywhere. A ledger can only record which version was applied, and when.

Exception two — Ground-specific runs. Small grounds produce more boundaries; hill winds move the ball more. A strike rate in Chattogram and one in Dharamsala do not mean the same thing. A ledger can record geography; turning that into a model correction is separate work.

Exception three — Un-televised matches. No broadcast means no tracking; no tracking means handwritten entries only. The ledger's reliability is tied directly to broadcast contracts, which is a brutal truth about cricket's economy.

Contrarian Angle: Verified Is Not True

Blockchain proves a number was not changed; it does not prove the number is right. This is the verified-error problem. A wrong entry written to the chain is permanently wrong, and now looks more credible because it is "verified". A verified error is more dangerous than a plain one, because it closes the space for doubt.

Second: garbage in, hash out. The data enters from a human pen through an oracle. However good the ledger and the hash, discretion at the entry point sits inside the ledger wearing the mask of truth. The real reform is at the door: two independent scorers, a visible discrepancy report, a public correction log.

Third — and most important in Asia — administrative capture. Who runs the ledger? If one board or one company controls the nodes, whoever cannot change the system owns the system. "Decentralised" becomes decoration.

Fourth: commercial incentives. Where revenue depends on audience numbers, there is an incentive to inflate metrics. If the ledger verifies those too, fine; if not, it will protect scores while the business side stays unaudited.

One more point, stated plainly: technology has long arrived in South Asian cricket as an instrument of hierarchy — DRS, tracking, sensors have gone first to those who later sit in decision rooms. If the ledger entrenches inequality with proof attached, we get more numbers and less reform.

Blockchain is not a solution to cricket's problems. It is an audit tool, and audit tools work only when the auditor is independent.

Takeaway

In the next Asia Cup cycle I will watch three numbers, not as predictions but as thresholds. First, Bangladesh's NRR-dependent qualification margin — if the gap is under 0.05 before the last group match, the ledger question stops being theory. Second, how many days domestic contract delays take to fall, because however modern the token, the player's bank statement is the real truth. Third, how many boards open their ball-by-ball data publicly. Whoever does it first becomes auditable first.

The rest of the numbers arrive after the cricket. Who wrote the scorecard remains the real question.

— Root: Chattogram xG blog after Burnley