In the Transfer Window the Names Move; the Ledger Doesn't

The scorebook was already open when I arrived. Mumbai, 2026 — a wooden cupboard in the youth setup at Kenkre FC, and inside it the handwritten ledgers of the Mumbai Schools Sports Association under-14 and under-16 leagues, 2026 to 2026. Eleven consecutive weekends I photographed them and digitised them alone. Four thousand three hundred match entries.

I went looking for scores and found something else. A pen stroke, in the margin, beside a name: "Birth certificate to be resubmitted." No date. Who wrote it, why, what happened next — nothing.

The margin note is often the real story. Because when the transfer window roars and a new name leaks every hour, underneath that name sits exactly this kind of quiet paper stack — birth certificate, school certificate, board registration, and NOC. Four documents. Four different custodians. Nobody holding the whole picture.

The question the cricket market asks least in this window is the most basic one: who is this player, and who holds his papers?

Football has FIFA's Transfer Matching System — a central register where every step of an international transfer is time-stamped, with an audit trail of who approved what and when. Cricket has nothing equivalent. Each board keeps its own registrations. Franchise leagues sign players through boards, boards issue NOCs, and no central index of those NOCs exists. So when a paper dispute surfaces, it retreats into a file cupboard at a district association where the file number has probably changed three times.

Much of what changes hands in this window is never written into a system at all. When a franchise signs an overseas player, it needs an NOC from his home board — for a fixed term, on fixed conditions. What happens if those conditions are broken lives in a letter, not in a ledger. Everyone knows the name. Nobody knows the terms.

After I was appointed one of three advisors to the Bangladesh Cricket Board in 2026, overseeing digital and media affairs, I started looking at this from inside. What I learned was not new, only clearer: the problem is not malice, it is architecture. The information is scattered, and scattered information means nobody owns verification.

This is where blockchain enters the conversation. And this is where I want to be careful, because much of the excitement around the word in cricket is addressed to the wrong envelope.

Blockchain will not fix cricket's paper problem, because cricket's crisis was never a shortage of information — the crisis is who reads it, and who decides what to read.

Look at my own data to see the difference. After digitising those 4,300 entries I ran a count: 71 percent of boys who scored 15 or more goals in a school season never appeared on a district trial list. The information existed. The ledger existed. Nobody read it. A 15-year-old left-back from Dharavi was dropped from three consecutive lists — because of a clerical error, three times.

An immutable ledger would have made those three errors impossible to hide. That is true. But if nobody wants to put the name on the list in the first place, what exactly does the ledger do?

Still, blockchain has one honest use in cricket, and it is not in player trading hype — it is in the trail of registration and permission. Picture it. A youth player's birth certificate is filed at a district association, time-stamped. He plays under-16. Two years later he registers for under-19. If his age is ever corrected, the correction is appended as a new entry; the old entry is not deleted. Who corrected it, when, on what evidence — all of it survives. Then he signs with a franchise league; the board's NOC is written to the same ledger, and so is the recall clause.

The value here is not in the hype, it is in the friction. Today, if a player's age is questioned, answering it means opening three cupboards, burning three clerks' time, and the evidence eventually becoming word of mouth. A time-stamped trail does not make the decision faster. It makes the decision accountable.

Consider the current machinery for age verification. The BCCI used the TW3 bone-age test for years before admitting players into age-group squads. The test is expensive, invasive, and — most importantly — it does not verify a birth date, it measures skeletal maturity. A player can be 16 in bone and 14 on paper. The technology will not catch that. Paper truth and body truth are two different questions, and cricket administration has long avoided the first by treating the second as an answer.

Three limits, though, are plain to me.

The first is fundamental: a ledger cannot verify the truth of an input, only its immutability. If someone files a false birth date on day one, blockchain will preserve it flawlessly — forever, and with more confidence. It will not erase bad information. It will laminate it.

The second is ethical and legal. Data written to a chain is usually public or semi-public. Putting a minor's birth date, address and school name into a permanent, censorship-resistant record means making his childhood permanent too. Data protection law is far ahead of cricket administration on this question, and the board that understands it first will gain later.

The third is the least popular: cost and access. Who pays for a small district association to run a node, manage keys, train staff? If nobody does, the ledger will exist for four or five big city academies, and the boy on a village school ground will have no entry at all. Which is a new inequality wearing the packaging of an old one.

And one thing I know in my bones: changing the system does not change who holds the power to decide. From years of sitting at the boundary edge watching matches and reconciling the books, I can say this — the paper changes, the hand does not. In 2026, when I joined a Mumbai digital outlet as its first data columnist, the editor wanted weekly hot takes on the ISL's young Indians. I declined and did the opposite: back in 2026 I had logged 40 players who started at least five I-League or ISL matches before turning 20. By October 2026, 34 of those 40 had left professional football; six remained contracted.

That 6,000-word piece was read by fewer people than a single transfer rumour published the same afternoon. I kept the spreadsheet anyway. Because information changes nothing on its own. Information changes things only when someone is compelled to decide with it.

Now the uncomfortable part, which almost nobody in this conversation says: cricket never had a record crisis; it had a will crisis.

In 2026, at the World Cup in Russia, I worked as an accredited analyst on an Indian broadcaster's digital desk. On day one a male colleague told me I "wouldn't need the tactical feed." I spent the tournament logging the youth-academy origin of all 736 registered players against federation registration documents. Seven hundred and thirty-six rows, each one a human decision. The tally: 468 had come through just 40 academies worldwide, and France's 23-man squad contained nine graduates of Clairefontaine and its feeder network.

The broadcaster ran the table as a full-page graphic, credited. But the table discovered nothing — it simply counted a known truth out loud. Opportunity is not distributed evenly, and the distribution is decided by people.

So here is the question I put to blockchain enthusiasts: do you genuinely believe cricket's problem is that paper gets lost? Paper survives. Paper sits in district association cupboards, gathers dust, goes unread. If you build a ledger where everything is written down, but the person making the decision never opens it, you have only digitised the dust.

The real reform, then, is administrative, not technological. Who is obliged to read the ledger, whose omission of a name must be filed in writing with reasons, and within what deadline — without answers to those three questions, no chain changes anything. The name I found in that 2026 margin, the one beside "birth certificate to be resubmitted" — if a mandatory field had sat next to it, a "why" and a date, I do not know what would have become of that boy. But at least someone could have asked the question.

I started with the names nobody had followed. The habit is still there, and it is what brought me here.

My working rule is simple: I do not name a player I have not seen logged twice. Blockchain can help me do that work — if it is an accounting system and not a marketing one.

The question, then, is not technological. It is this: next season, the first board to publish its youth registration ledger — every name, every omission, every reason attached — can it survive doing so? Or will cricket dress its incomplete paperwork in a digital wrapper and repeat, once again, what it has been doing for six decades?