The Blockchain Ledger and the Academy Ledger: When Cricket's Youth Is Told to Move On-Chain

There are two ledgers on my desk.

One is paper — a running file kept since 2026. Trial lists from London Colney, Halesowen, Bradford, Mirpur, Sylhet. Which boy joined at what age, what his father does for a living, who pays the monthly fee, who is on scholarship, who is released inside six months. The other is digital — an on-chain register glowing in green and black, where an entry, once written, cannot be rubbed out, cannot be altered without everyone's permission.

Last November a coach phoned me from Mirpur. "Sir, everyone says it now — if the age is written on the blockchain, there's no trouble left." He was talking about 2026. A boy from an Under-19 World Cup-winning side was later banned over an age-fraud finding; the Delhi cricket association's decision effectively erased his name from the paper ledger. Seven years on, that name still surfaces in academy corridors, because the ledger lied in one column and nobody caught it.

Beside that boy's name in my file, in small letters, I once wrote: "Age verification — impossible." Blockchain's promise is that the impossible becomes routine. The question, then, is not about technology. It is about power.

Context: where the money came in, and where the boys stayed

After 2026, crypto money began entering cricket. First on sponsorship boards, then in fan tokens, finally in NFTs. Across 2026 and 2026, two cricket-facing platforms made the loudest noise in the market — FanCraze and Rario. FanCraze signed on as the International Cricket Council's official NFT partner, and in March 2026 raised a $100 million Series A led by Insight Partners. Rario struck a deal with Cricket Australia and, in April 2026, raised $120 million led by Dream Capital.

Those numbers changed the language of investment overnight. Suddenly a cricketer was not only a run-scorer but an "asset". A young cricketer became an "early-stage asset".

Then came 2026. A crypto-market slump, a collapse in NFT valuations, and reports of layoffs and uncertainty at both platforms. Marketplaces effectively stalled; buyers began asking what the tokens they had bought were actually worth. People who had purchased "digital collectibles" on faith learned a simple distinction: permanence lives in the blockchain, value does not.

On the ground at academies, the problem is entirely different. The fight there is about age, about registration, and about which family's son has the right to play for which country. Sitting in London, I watch week after week as a family in Sylhet or Mirpur does the arithmetic of sending a boy into English club cricket — visa, school, lodging, and the unspoken condition: he must reach a county academy's door inside the qualifying window, or he becomes "overseas", a foreigner, an outsider.

Between those two worlds sits a simple question nobody asks: whose ledger is it?

Core: what the technology answers, and what it does not

Age fraud is nothing new in South Asian cricket. Boards have spent decades trying to verify ages through paper birth certificates, school records and bone-age testing — the TW3 method. The method is expensive, slow, and not always accurate. Every age-group squad means a cutoff date, and every cutoff date means an opportunity for thousands of families — one that slips away if a boy's birth shifts by a few months. For a household counting two meals a day, a six-month date is never innocent.

This is where the blockchain pitch sounds most seductive: birth certificates registered on-chain at the moment of birth, unalterable by anyone. No board-level universal system exists in international cricket yet, but the idea circulates in planning rooms, and the word is now familiar in agent conversations.

The trouble is that the ledger's weakness was never that entries could be changed. The weakness was who writes the first entry, and who verifies it. Blockchain answers the second question — anyone can verify. It does not answer the first. In a village where a birth certificate is issued twice, an on-chain ledger makes the falsehood immortal: impossible to erase, impossible to correct. Call it the immutable error. Cricket has a long, if not always honourable, tradition of correcting errors; no board will want to give that up.

There is another dimension where blockchain could have been cricket's most practical application: training compensation and transfer accounting. A boy moves from a Sylhet academy to Dhaka, from Dhaka to the county circuit, from county to the national side — and along that path sit dozens of coaches, several families, and real money. Smart contracts could automate the terms of a deal, the sell-on clauses, the future transfer fees. Solidarity payments are far less developed in cricket than in football; here technology could genuinely add something.

But what is actually being built runs the other way.

First, tokenisation has arrived on the spectator's side, not the player's. Fan tokens, digital cards, ownership of video moments — all of it monetises the fan's feeling. The boy himself earns almost nothing from it. Ownership of the digital assets generated by his performance passes to platforms, license-holders and investors.

Second, this money does not reach academy ground level. Look at my 2026 entries: at one London academy, monthly fees, travel, kit, nutrition advice and physio bills add up to several thousand pounds a year. That same year, at one Sylhet academy, the total cost of boarding, kit and training for a group of boys was far lower — and most of it came from family income, remittances from a relative abroad, or the patronage of a local businessman. The NFT millions do not appear in a single line of that arithmetic.

Third, if on-chain registration does arrive, its first user will be the board, not the player. A board will be able to display the "transparency" of its selection process while retaining ownership of the data about which boy played where at what age. Data is power; on-chain data is permanent power.

This is where an old example from football needs translating into cricket. In 2026 I spent two weeks in the Clairefontaine archive and wrote that Mbappé was a layer, not a meteor. France's success did not come from one talent; it came from twelve regional academies, technical repetition staged carefully by age group, and a clear registration system that tracked a boy's development across twelve years.

Cricket has no such tracking. In South Asian academies a boy's record lives in a coach's head, in a WhatsApp group, or in a glossy notebook that monsoon rain destroys. Blockchain could have filled that gap — if the question had been "how do we measure this boy's development" and the answer had been "with a durable, verifiable file". But the market's question is "how do we sell this boy", and the answer is "with a token".

In 2026, during the empty pandemic season, I interviewed fourteen released academy players. Sixty-eight per cent of them described themselves as depressed; the piece was later cited in a youth-welfare review. Some of those fourteen now play club cricket, some drive cars, some coach. None of their names appear in any blockchain. Yet boys of their age were being sold as "future stars" in NFT catalogues.

I go back to my paper ledger. It has a column headed "who paid". Behind every boy's journey sits a father working two shifts, a mother who sold her own jewellery to buy kit, a coach who takes extra sessions unpaid. None of them appear in a smart contract. They are the real investors, and they have no liquidity event.

Contrarian: permanence is not truth

Blockchain is not the answer to cricket's ledger problem, because the problem was never technological. Permanence is not truth. If a false entry is written on-chain, it becomes a stronger falsehood — because now nobody dares correct it; correction means standing against the system. Age fraud stops being a game of concealment and becomes architecture.

Second, tokenising a young player means turning him into an asset. My files, spanning nearly three decades, show that many boys labelled "investable" at sixteen are on an academy release list by twenty — and nobody remembers them then. The marketplace closes; the ledger stays open, but nobody walks into it. That silence is cricket's oldest habit.

Third, the beneficiaries of this arrangement are platforms and agent networks. The companies that raised hundreds of millions in 2026 laid people off in 2026. The boy's childhood does not come back; an investor's loss is insurable, a family's is not. And one thing I have seen repeatedly: we enjoy a lower-league fairytale, then forget it — and the structural reform that would redistribute resources never follows. A token is not a substitute for that reform; often it is the veneer that hides the absence of it.

I am not dismissing the technology outright. Three uses could genuinely serve cricket: a durable age and registration file, if verification happens on the ground; automatic distribution of training compensation; and a public record of contract terms. The condition is simple: the boy must be treated as a citizen of the system, not as its asset. There is a second condition, one I see almost weekly with players returning from injury — force someone to prove they are "back" and you raise the risk of a second injury. If an on-chain role or token holding creates that pressure to prove, the technology becomes an instrument of harm.

Takeaway

I keep a ledger of every academy boy who outgrows the floodlights. At sixty-three, I dig through transfer windows for the boy beneath the fee, not the headline.

What to watch over the next two years: whether any board actually launches on-chain registration; whether the second NFT wave returns under the name "academy tokens"; and whether smart-contract money ever reaches academy ground in Sylhet or Mirpur.

What blockchain does for the boy whose birth certificate still exists in two copies — that is the real question. Technology will not answer it. The people who write the ledger will. And in my file that column stays blank, the one headed "who paid", the one whose answer is never written in code.