Cleared on Paper, Missing in the Account: Cricket's Contract Ledgers and the Limits of Blockchain

July 2026, BKSP. Eleven at night on the dormitory veranda of the bio-secure camp. A player turned his phone screen toward me. The banking app showed 14,200 taka. The club's wage ledger for the same month recorded that the first instalment of his five-month arrears had been 'paid'. The paper cleared; the account did not. That night one thing became obvious: cricket's accounting crisis is not a shortage of accounting. Records are kept — the ledger simply does not sit in the player's hands. Across five months of talking to 23 players and staff, cross-checking contracts against payment dates, the central question was always the same: which ledger is true, and who owns it? That question has now returned in new clothes, with a name on it: blockchain.

Its return is not strange. During the 87 days I spent inside Mohammedan SC's camp after the Bangladesh Premier League was suspended, I saw the same scene daily: a manager pulling a contract copy out of a folder while a player could not find his own. As an economics graduate my habit is singular — not claims, dates. Who is owed what, when, under which clause, which clause legalises delay, and who announced that clause. Only when those four answers existed in writing did the story become publishable. Within two weeks the club paid 40 percent of what it owed. Notice: no new technology was involved. There was a deadline, a document, and a visible account. This is precisely what blockchain talk skips.

Cricket actually runs three separate ledgers, owned in three separate places.

The first is registration: which player at which club, in which season, on which contract, under which transfer terms. Boards and franchises hold that record. The second is money: salaries, match fees, signing bonuses, agent commissions, sponsor obligations. Most of it sits in bank statements; the conditions sit in paper contracts. The third is the body — and this one is the least written down and the most tamper-prone. Who bowled how many overs, absorbed how much sprint load, reported hamstring tightness when, and received return-to-play clearance on which date. Most of that lives in a coach's or physio's head, perhaps in a spreadsheet. If two of those three ledgers were centrally immutable, proof of unpaid wages and proof of burning out a teenage fast bowler would become visible at the same moment.

Now, what a blockchain actually does — stated precisely, because in Bangladeshi sports discussion the word has become almost liturgical. A distributed ledger does three things: entries can be appended but not deleted; each entry carries a timestamp; multiple parties read the same ledger, so no single party can quietly rewrite the account. Note that none of this is a 'crypto revolution'. It is an accounting principle. Anyone claiming blockchain will solve all of cricket's problems either does not understand the technology or is selling it.

Where it genuinely helps, the use case is usually less exciting. Suppose a match-fee condition were written into every contract: funds release from a designated escrow account within 24 hours of the scheduled start of play, on instruction recorded by a signed match-official entry. Here blockchain is not deciding anything — it is keeping an undeletable record of who gave the instruction, when, and what the balance became after release. The real change is not technological but contractual: the money stops sitting in the club's discretion and sits in escrow. The ledger only preserves proof that a condition was broken.

In 2026, the mechanism that worked was not escrow. It was a reporter's deadline. Twenty-three interviews exposed the gap between contract dates and bank statements. But the limits of that method are obvious: it works when someone looks. On the day nobody looks, the ledger goes invisible again. Technology's offer sits exactly in that gap — a permanent, public, always-present look.

So which ledger should be digitised first? My experience says not wages, but age-group workload. In 2026, sent to standardise Abahani Limited Dhaka's training ground, I went to standardise a training ground and found the club — 46 sessions observed with the fitness coach, a 'Session Intensity Card' built for 24 players logging RPE and sprint load. One of those 18 training diaries recorded winger Nabib Newaj Jibon's 1,042 high-intensity metres. When that number published, many read it as praise. It was a warning.

Because if session-load records sit with the club, they are preserved in the club's own interest. If a teenage quick is being played three times a week, and his load data lives in the club's own spreadsheet, nothing obliges that data to leave the building. But once a load registry is multi-party — player, physio, board, and players' association all reading the same entry — overuse stops being invisible. This is blockchain's most useful cricket application, and because it is less dramatic than unpaid wages, it makes fewer headlines.

The second half of the body ledger is more sensitive: return-to-play clearance after cruciate ligament surgery. For years I have watched players rushed back lose their second act, and the problem is more mental than ligamentous. If every clearance decision were written down — who signed, on which scan report, on what date, under what conditions — nobody could later say 'I was fit, I played under board pressure'. Nor could anyone quietly get away with it. An immutable clearance ledger does not breach medical confidentiality; it closes the exit from accountability. This is where zero-knowledge proofs matter, letting 'fit or not' be verified, or identity be confirmed without exposing a name.

The third ledger is contracts and commissions. The International Cricket Council has banned third-party ownership, but a ban on paper is not an enforced ban; enforcement happens when every agent payment is visible. In Bangladeshi and South Asian franchise markets, agent fees are routinely outside the conversation. A registered commission ledger would stop any party claiming, 'I did not know who was paid what in this transfer'.

Sponsor obligations follow the same logic. If a tournament title sponsor's fee schedule and deadlines sat in a public ledger, a club's excuse for delayed payment — 'the sponsor did not pay' — would become verifiable. Today it is unverifiable, and therefore permanently suspect.

Now honesty is required: smart contracts cannot handle every cricket obligation, because many obligations are matters of judgement. A smart contract can say with precision, 'the match took place, release the fee'. It cannot say, 'the player was fit, release the fee'. Fitness is a verdict, not a number. Where there is a verdict, there is an oracle problem — who feeds the data, and what if the feeder is itself a party? This is why permissioned, tokenless, plain-framework ledgers are more realistic in Bangladesh. No crypto volatility, just a rules-based database where many may write and none may erase.

The remote-command lesson from the 2026 Russia World Cup is directly relevant. Thirty-two days, accreditation for 21 matches in Moscow, Saransk and Nizhny Novgorod, a shared 64-match pressing database, 3.4 million pageviews — all templated into pre-match data packs, in-game tactical logs and post-match quote sheets. Yet that template never told me who had gone silent in the dressing room. A ledger can tell me when an entry was made; it cannot tell me whether a decision was right. Evidence and performance — confusing the two is the deepest trap in technology talk.

Who wants this ledger, and who does not, deserves plain statement. Players want it, because proof of arrears would sit with them. The parent of a young player wants it, because his son's workload would become knowable. Part of any board wants it, because credibility is its greatest asset, and repeated arrears stories erode it. Those who resist usually raise two objections: cost, and privacy. The first is wrong — a permissioned ledger costs no more than a modern scoring system. The second is serious, and it is the real design question.

Because total transparency is not harmless. Public wages invite tax disputes, family pressure, and rivals reading a player's weakness. The lowest-paid player's number is the one that should be least public. The answer is layered transparency: payment timing and conditions public, amounts hashed or visible only to the parties. Proof is needed that money moved; proof is not needed that everyone knows the figure. A system that exposes the player while shielding the club is not transparency; it is a new form of pressure.

One more uncomfortable truth. What worked in 2026 was a public account, but it was not volunteered — it was extracted by asking, requesting documents, holding a deadline. Blockchain does not supply that will. A ledger kept perfectly, but never opened, is merely a well-preserved secret. Its value depends on third-party scrutiny — a players' association, independent media, and an adjudication process with teeth. Technology supplies resources; it does not supply power.

The reverse also holds. Many assume on-ground reporting always beats remote data. That is false too. Without my 2026 session card, I could have watched 46 sessions and still not said which week's load was abnormal. And that same card could not tell me why a player's face was heavy that week. Local knowledge and measurement correct each other rather than replace each other. A ledger is one half of that pair — the measurement half. The rest belongs to the people on the ground.

So what is the next internal signal in Bangladeshi cricket? I will watch two places. First, whether the next franchise agreement contains an escrow clause with an actual date — '24 hours from match day' rather than 'as soon as possible'. The wording is everything. Second, whether a players' association representative gets a seat in governing the ledger. If so, that is not a feature; it is a shift in the balance of power.

I still remember that phone screen in July 2026. On the day a club publishes its own payment dates and nobody protests, I will know the change has happened. The absence of protest — that is the only metric a ledger can achieve. Technology will not stop arrears; it will only record proof so cleanly that denial becomes impossible. The rest is ours, for those who have learned to ask.