Cricket's Scorecard Is a Distributed Ledger: Who Settles the Consensus in the Regular Season

Hook: Two Feeds, One Match, Two Truths

It is 7:40 pm on my query line. Two feeds are open side by side for the same match. On the left, the board's official scorecard. On the right, the raw file from the ball-tracking provider. The scorecard says six legal deliveries in that over. The raw file holds seven events — one extra, labelled "reviewed, retained." Both are correct. Both belong to the same match. But they are not the same ledger.

I ran the first xG audit because the eye test had no receipts. The shot map I published after Liverpool-Tottenham in October 2026 came from exactly this place — the gap between the scoreline and the underlying data. In football that gap was named xG. In cricket the gap is wider, because cricket's gap is not a number, it is a signature. Cricket's official record is not a document of truth; it is a document of consensus. The handful of nodes that sign it decide what the match actually was.

In the 2026 regular season, that consensus is under more strain than at any point I can remember. The reason is not ball-tracking. The reason is that there is now more than one of it.

Context: From the Print Desk to the Query Desk

The print desk died the day I learned to query the match. But the job the print desk did never died — it only changed hands. In the 1980s, cricket had one canonical ledger: the scorer's book. One person, one pen, one match. The board ratified it, the wire copied it, the newspaper printed it. The chain was simple, and its simplicity came from scarcity of information, not from integrity. There was no second source to disagree with.

Ball-tracking entered broadcast in 2026, and in July 2026, during the India-Sri Lanka series, the player review system arrived. From that point the ledger carried two kinds of entry. The first is declarative: what the umpire said. The second is measured: where the ball actually went. Most of the time these two agree. The occasions they do not are the raw material of my trade — and that is precisely where the politics of the ledger begins.

After 2026 my own rule was simple: no claim goes to print without a number beside it. But in June 2026, when 92 Project Restart matches were played behind closed doors, I learned the number alone is not enough. That month the crowd became a control group, and a context layer entered my model: attendance, travel miles, rest days, kickoff temperature. That was the birth of the ledger's third stratum — not just what happened, but under what conditions it happened.

In the 2026 regular season all three strata exist, but each now has multiple claimants. That is the real story.

Core Analysis

1. Who the nodes are, and who actually holds the master key

When a cricket match ends, the information passes through four hands. First the field scorer, entering live. Then the home board's match referee report, carrying discipline, over rates and pitch ratings. Then, at international level, the governing body's match centre, which keeps the format-agnostic record. Finally the commercial aggregators, who copy the scorecard into their own databases.

Here is the sentence nobody says out loud: a copied node is not a writing node. The aggregator's database is the fastest to read in the world, but it is never the primary document. When a dispute arises — was that a wide, was that run-out legitimate — the thing that gets opened is the scorer's book, not the aggregator. That is why I label source tiers in my own copy. Tier 1 is documentary: board announcements, law revisions, contract documents. Tier 2 is provider telemetry: ball-tracking, edge detection, clock data. Tier 3 is the eye test — press box, commentary box, stands. Tier 3 is not a source. It is a hypothesis.

The problem is that most cricket argument uses Tier 3 as though it were Tier 1. I watched Germany leave from the Sochi press box in 2026, and the numbers had left first. The same thing was happening there — everyone was writing eyewitness narrative while nobody was reading four years of pressing drift.

2. The oracle problem: ball-tracking was never a neutral witness

We treat ball-tracking as an impartial machine. It is not. It is a prediction engine that reads the final frames of a delivery and extrapolates the rest. Legally, that extrapolation carries a tolerance — half the width of the ball. If the predicted path passes within less than half a ball's width of the stump centre, the decision stays with the umpire.

Many people explain this tolerance as a system limitation. It is not a limitation; it is an admission of liability. A system that declares its own uncertainty is a system worth trusting. One that does not is not trustworthy, only confident.

Now imagine two providers tracking the same match, with different camera geometry and different frame rates. Two different predicted paths are entirely normal. Which is canonical? The answer is not technical, it is contractual. Whichever provider holds the broadcast deal puts its data on air. And what goes to air becomes, three days later, what the public calls true.

In blockchain language this is the oracle problem. A smart contract cannot see the outside world; someone has to tell it. Cricket's ledger works the same way. The ledger does not know where the ball went. The ledger knows only who reported it, and who countersigned.

3. The Kookaburra trial: change one input and the whole dataset moves

In the County Championship regular season, the England and Wales Cricket Board has used the Kookaburra ball instead of the Dukes in selected rounds — two rounds in 2026, and more extensively in subsequent seasons. The decision was taken for other reasons: the Dukes offers excessive seam movement in English conditions, while the Kookaburra lasts longer.

In data terms this is nothing less than a controlled experiment. Same grounds, broadly the same teams, the same umpiring panel — one physical input changed. Natural experiments of this kind are rare in cricket, because cricket's rules change slowly and unevenly.

Two observations follow. First, changing the ball does not only change swing; it changes outfield catch counts, slip catching rates, even the shape of an innings. Second, and more important: changing the ball changes nothing in the scorecard. The scorecard records 247 for 8 declared in 86 overs. Which ball was used is a metadata field — present in most archives, absent from almost all analysis.

So the input is written into the ledger, but nobody is doing the work of reading it out of the ledger. That is not a scarcity of information. It is a failure to use information. In regular-season analysis, this is the widest gap there is.

4. Private keys: workload and fitness data nobody publishes

My context layer absorbs travel miles, rest days and sleep data. A large share of that data is not available to me, and never will be — because it is not match data. It is workplace data.

This is the deepest inequality in cricket's information economy. Franchises and boards hold the sports-science files: speed-volume load, hamstring risk scores, bowling workload, biomechanical screening. Researchers and journalists hold only the outcome — who played, who was dropped, who suddenly withdrew citing "personal reasons."

So what we actually do is not data analysis; it is inference from incomplete data. Take Jofra Archer's history of stress fractures and Mark Wood's workload management. Almost everything written about either is Tier 3 inference. I have written some of it myself. Honest writing requires admitting: I do not know whether he was rested for that series. I know only that his pace dropped in the next match.

This is the private-key problem. The public ledger is verifiable but incomplete. The private ledger is complete but unverifiable. And every day we write interpretations of the first while relying on the second.

5. Proprietary functions: what we cannot read, we cannot audit

The number of metrics with a published name and an unpublished formula keeps growing. Pressure index, impact score, runs saved in the field, expected wickets. Each has an owner, a weight set, and a summation rule the user never sees.

I am not against this. I am against weighting it. The distinction is this: a metric can be used in a decision, but a metric cannot prove a decision unless its formula is public.

An example from my own trade. When a franchise says "he wasn't in our top ten," that is a contractual statement, not a ranking. Newsrooms print it as a ranking because rankings are easier to read. This is how a proprietary function smuggles a private company's opinion into the public ledger with no audit attached.

It is why my own rule holds: if I build a model, I publish its limits, and I name in advance the single variable most likely to break it. Forecasting requires the forecast to be written first, not after. Otherwise it is not a forecast, it is an explanation.

6. Settlement price: the auction is the most honest ledger

A strange fact: cricket's most auditable numbers are not on the field, they are in the market. In December 2026, Sam Curran sold for 18.5 crore rupees at the Indian Premier League auction, then a record. In December 2026, Mitchell Starc went for 24.75 crore and Heinrich Klaasen for 23 crore. In November 2026, Rishabh Pant reached 27 crore.

These numbers are honest because they cannot be rejected. Nobody can say "my model had Pant at 32 crore." The market paid what it paid. A transfer rumour is just a row waiting for a primary key. The hammer falling is the moment the primary key is set and the row becomes permanent in the ledger.

But a gap remains, and it matters. Market price does not measure ability; it measures ability crossed with demand. If a side is short of finishers, an average finisher gets overpaid. If a side is known for fast bowling, fast bowlers get overpaid. Settlement price is information, not truth. Anyone using auction figures to prove a player's quality is treating a market signal as a physical measurement.

I still trust this ledger more than the others, for one reason: nobody here can hide a mistake. In every other ledger errors persist. Here the price of an error lands in next season's team balance.

Contrarian Angle: The Problem Is Not Data Volume, It Is Data Governance

This is where a comfortable assumption has to break. We assume more data reduces disagreement. The regular season shows the opposite. More data does not end the argument; it moves the argument off the field and into the query.

Thirty years ago, two journalists arguing about a match argued about events on the grass. Today the argument is about filter definitions — who calls it a dot ball, who calls it a scoring shot, where the line and length boundary sits. Both are technically correct. Both are true in different ledgers.

One common error I see constantly: the belief that the player review system made cricket objective. It did not. It made cricket procedural. The decision used to belong to a person; now it belongs to a protocol — and inside the protocol a person's judgement still sits, with a new name. The umpire's call concept is precisely an acknowledgement of that fact.

And a second assumption needs breaking: decentralisation is not democratisation. The spread of ball-tracking did not put analysis in everyone's hands; it concentrated the master key further into a few companies' hands. Whoever holds the contract writes. Everyone else reads.

Takeaway: Which Signal to Watch in the Next Round

Three pre-registered signals for the next round. First, where the ball provider changes between rounds, whether slip-catch ratio and fine-leg boundary rate both shift in first innings. Second, in weeks carrying two competitions, how far the mean pace of quick bowlers drops by day four. Third, the fall in runs saved in the field across back-to-back fixtures.

I am keeping my ledger open, and I will reconcile it at the end of every season. If someone asks me what cricket's real crisis is, I will not say pitches, balls or bats. I will say this: who is writing, and who is only reading.