A Blockchain Ledger Won't Fix Cricket's Scorebook While the Bottleneck Sits in the Scorer's Hand

Start at the scorer's table

BKSP Ground Three, Savar. A 50-over Dhaka Premier League match, half past two in the afternoon, the pitch baked to gold. Two men sit at the scorer's table: one with a paper scorebook, a bowling-chart app open on his phone; the other in front of a laptop with no camera. In the 29th over a low catch at midwicket hits the turf. The fielder does not hold it. The scorebook records one word: drop. On the same ball the striker had left his crease; two coaches on the back bench were describing two different games in two different languages.

After the match a sponsor sent me a deck: ball-by-ball data written straight onto a blockchain, no party able to alter a number, every delivery carrying a hash that stays identical forever.

I closed the deck and looked back at the scorer's table. If the man who wrote drop had mistakenly written caught, the blockchain would have made that error permanent — with no path to correction. That is the centre of cricket's data argument today: we are debating the immutability of records we cannot yet verify.

Where blockchain has actually reached in cricket

Three doors. First, collectibles and fan tokens. FanCraze announced an ICC-licensed cricket NFT deal in 2026, and in April 2026 India's Rario raised a $120 million Series A led by Dream Capital. That same year the global NFT market began contracting, and by 2026 the collectibles door had largely cooled. Second, rights and consent records — which contract holds a player's image, name, footage and bio-data, for how long, and for whom — still scattered across email and spreadsheets. Third, the integrity ledger: hashing ball-by-ball records to freeze them in the name of anti-corruption work. That third door is the least discussed and the most useful, and the most misunderstood.

Asia's domestic reality sits in layers. International matches carry ball-tracking, six to eight cameras, dedicated data operators. A domestic 50-over league often has one scorer, one fixed camera, one phone app. Age-group cricket has paper. We call all three ball-by-ball data. A ledger does not understand that gap; it only knows what was written at that moment.

Definitions are not stored on the chain

In 2026, aged 24, from my flat in Rajshahi, I coded 1,248 shots from the Bangladesh Premier League football season for a Dhaka new-media outlet. The output: Abahani Limited Dhaka scored 34 goals from 27.6 xG; Sheikh Jamal Dhanmondi scored 29 from 31.2 xG. The series ran in twelve parts and the table became a weekly fixture.

Then I ran a test. I tightened the definition of a big chance — shots taken inside the box, from positions with at least two defenders in front. The numbers moved; five to seven percent of shots shifted category.

The ledger did not change. The definition changed. In Bangladesh I taught a league to see its own xG, but that mirror was built from coding definitions, not from a chain.

The cricket translation is direct. What is a dot ball? A dot ball against a set batter in the 14th over on a Mirpur turner is not worth what a dot ball against a new batter at the death is worth. The ledger records zero in both cases. The fact is intact; the meaning is gone. Closing that gap requires context fields — over number, field restrictions, ball age, pitch behaviour — added at coding time, never afterwards.

Data density is large; verification is small

A T20 innings is roughly 120 balls; each ball carries ten to fifteen fields — bowler, batter, runs, extras, fielding position, delivery type, line and length, shot type. Two innings give roughly three thousand fields per match. A hundred-match domestic season reaches roughly three million data points.

Now assume a two percent error rate in domestic scoring conditions. That is not extravagant: leg-bye against bye, catch against drop, wide against legal, all decided by one person's instant judgement. Two percent means roughly sixty-six thousand false entries in a season. Blockchain will not erase them; it will make them permanent, and every future analysis will stand on them.

Is immutability the fix, or the most expensive way of hiding the problem?

In 2026, at the Russia World Cup, I logged Germany against Mexico as an event-data analyst. Germany's 26 shots produced 1.3 xG; Mexico's 12 produced 1.1. Germany's PPDA was 6.9 — they allowed very few passes per defensive action — so the press looked fierce on paper while the transitions opened eighteen chances in reality. PPDA showed me Germany, and I shipped the model before the final whistle: Germany would not escape Group F. They finished bottom.

The lesson I brought back: the number that changes a decision comes from definition and context, not from the recording medium. The ledger fixes the medium, not the context. That gap is wider in cricket, because a football pass is an objective event and a cricket dot ball is not.

Building cricket's own pressing number

PPDA works in football because the event — the opponent's pass — is countable and can be paired with your own defensive actions. Any cricket equivalent requires deciding what pressure means. My template carries three numbers: powerplay dot-pressure (balls that forced a defensive response, not merely empty deliveries), a wicket-probability index built on line, length and shot type, and a fielding-conversion rate for difficult chances. All three rest on coding decisions. Who rules whether a low catch is a drop or a hard chance? The scorer, the coach, or an analyst re-coding from video? In Asian leagues those three answers still differ. A ledger does not remove that disagreement; it preserves it permanently, because the correction path disappears.

Where a ledger genuinely earns its price

Three places. Multi-party agreement: when board, broadcaster, data supplier and betting-monitoring firm see one hash, the excuse that we hold a different number dies. In Asian domestic leagues that excuse is expensive, because a disputed run-out can change a result. Second, rights and consent records: one ledger for which player's footage went into which deal reduces contract disputes. Third, an audit trail for amendments. Here I want an addition — an amendment protocol. If an entry must change, the change is appended with reason, timestamp and approver, while the original stays. That design saves immutability from foolishness. A ledger with no constructive path to correction is not a custodian of data; it is a museum of it.

Correlation is not causation

Most leagues adopting ledgers also hold television money, multiple cameras and salaried scorers. Data quality is rising alongside the ledger, not because of it. Decide without base rates and we repeat the mistake I have avoided since Germany-Mexico: the right answer to the wrong question.

Second risk: ownership of player data. If a cricketer's ball-by-ball record is locked inside a token, that is not ownership — it is a closed room with the key held elsewhere. The ball-by-ball records of long-career players such as Tamim Iqbal, Mushfiqur Rahim, Mahmudullah Riyad and Shakib Al Hasan are Asia's most valuable analytical assets. If they cannot be verified and accessed, the ledger's beauty stays decorative.

Third risk: proving the wrong thing. Detecting abnormal betting movement is probabilistic modelling work, not ledger work. Suspicious in-over betting shows up in pattern analysis, not in hash verification. A ledger preserves evidence; it does not generate suspicion.

Empty stadiums taught me that home advantage is a variable, not a law. Data quality behaves the same way — it shifts by match, venue and light. A model that treats it as a constant pays the price in a season like 2026.

An ESTJ builds the pipeline first and the poetry second. The ledger is poetry; the scoring pipeline, scorer training and independent re-coding are the pipeline. An analyst who does not chase revelations calibrates until they appear.

The signal for the next cycle

Sponsors will sell ledgers and boards will announce them. Before placing any order, ask three questions: how many independent scorers worked each match, what percentage agreement two analysts reach on re-coding, and where amended entries are logged. Then price the ledger. Without those answers you are buying the most expensive sheet of paper ever printed — and it will last forever.