Blockchain Scorecard: A New Chapter of Cricket Transparency from the Khulna Ledger

The first column of the Khulna ledger taught me patience. Today another row has joined that column: a scorecard written on the blockchain. On March 14, 2026, the ball-by-ball data of a practice match at Sher-e-Bangla National Stadium was recorded on a public blockchain. 86 balls, 6 wickets, 142.5 runs—these numbers are no longer under the control of a single institution. In 52 years of watching cricket, I have seen for the first time a full innings of Bangladesh cricket stored in a way that no one can delete later. Bangladesh's first-class cricket has a data black hole: national team statistics are available, but ball-by-ball records from Khulna division or lower tiers often vanish in handwritten scorebooks. Blockchain creates an immutable audit trail. In the pilot, I saw three layers: a hash after every ball, an aggregate hash after every over, and a final hash after the match. The match had 44 dot balls, 12 fours, and 3 sixes. Shot maps showed right-handed batsmen played 61 percent of shots outside off stump. The France PPDA map was never a picture; it was a confession. This blockchain scorecard is also a confession that cricket data in Bangladesh was previously unreliable. But correlation is not causation: blockchain preserves data, not fairness. If a scorer enters a wrong entry, the blockchain immortalizes that error. The next signal is whether this pilot reaches the third division or remains an expensive experiment. The real question: will the Bangladesh Cricket Board treat this ledger as a policy, or simply as a test?