The Ledger Opens Before the First Ball: Blockchain, Age Verification and the Rajshahi Field Notebook

In the last week of June, an under-16 trial was running on net three beside the Rajshahi Divisional Stadium. A left-arm spinner had taken four wickets in five overs in a club match in Comilla; that figure sits in my notebook because I counted the overs myself that afternoon. When the trial ended, the selector asked for a birth certificate. The union parishad register gave one date, the school certificate gave another, fourteen months later. Both carried a seal. Both contradicted each other. The boy sat on the bench, and three years of net work hung on the tip of one selector's pen.

That evening I wrote in my notebook: if the moment of entry into a register were sealed at that moment, if every entry carried witness to its own hour of birth, this question would not be able to eat a boy's career so easily. That is where I start whenever I talk about blockchain in youth cricket. I look at the first minute, not the highlight reel.

Context: how a boy becomes visible

In Bangladesh a cricketer becomes visible in stages. Street or tape-ball cricket, then school tournaments, then union and upazila under-16, then district, then divisional under-18, then the national youth side, and finally the door to the BPL or the DPL. Every stage needs a paper, and every paper sits in a different pair of hands. The birth registration stays with the union parishad, the school certificate with the education office, the trial form with the district sports association, and the match record with a scorer's handwritten book.

The ledger opens before the first match is played—but that ledger is made of paper, and paper can be edited in the dark. From my years of watching matches, I can say age disputes are not rare in youth cricket; South Asian age-group cricket has produced serious controversies from time to time, sometimes settled by bone-age testing, sometimes by leaning on national identity databases.

Rajshahi's grounds make the problem sharper. From April to June the temperature touches forty degrees, from July to September the outfield drowns in monsoon, and district politics casts a shadow over selection panels. A veteran groundsman rolls the matting wicket, and his name never reaches a report. The scorer fills his book in ballpoint, sometimes keeping two copies, because losing one book loses a whole season. These people are the real verifiers, and they never enter a byline.

In 2026 I sat through fourteen matches of the Rajshahi Divisional Under-18 League and logged twenty-seven players' minutes, positions and match actions. In Rajshahi a spreadsheet became a field notebook. That work was in football then: left-back Md. Rakib Hossain completed eleven tackles in a 2-1 win over Naogaon, and after I verified that record against two sources he earned a trial at the BFF Elite Academy. I later moved the template into cricket, because the structure of youth documentation is nearly identical in both games.

Core: the blockchain claim is a ledger, not crypto

Mention blockchain in youth cricket and people think of cryptocurrency and NFTs. What a cricket ground actually needs is far more boring: a shared ledger where every entry is cryptographically hashed the moment it is written and chained to the entry before it. Anyone wanting to alter one date must alter every earlier entry, and that cannot be done quietly in a district office after dark.

The ledger's job is not to manufacture truth; it is to hold truth unchanged. This is where the technology meets my two-source habit. I never publish a statistic without matching two places against each other—an administrative ledger and a field observation. In a blockchain, two kinds of nodes do that work: a verifying institution and an independent administrative source. What computer science calls consensus was, in my notebook, two pencil marks.

The entries can be split into six layers. A hash of the birth register page—not the paper itself, only its digital fingerprint. The school certificate. The medical report from age verification. The match log, ball by ball, in an open format like Cricsheet, so anyone can audit it later. The trial outcome. And the coach's note, which is the most useful and the most neglected.

The architecture can stay simple. One node at district level, one at divisional level, an anchor node at the national federation. Encrypted storage for video, and zero-knowledge proofs for age queries—a selector can learn whether a boy is under sixteen without seeing his birth date or his face. Protective discretion, translated into technology, is called privacy by design.

This is where the cost accounting bites. Running a node is not easy for a district academy—electricity, connectivity, a weak monsoon line, and one trained operator. The scorer has to run the node, because whoever holds the keys to the ledger holds the truth of the ledger. Technology does not create a new hero here; it hands a new duty to the old, uncounted caretakers.

The impossible side must be stated plainly: garbage in, garbage out. A blockchain cannot correct a wrong first entry, only make it permanent. In Bangladesh the first entry is the weakest link—the birth and death register at a village union parishad, where births are often recorded months late, sometimes from a date remembered by an uncle.

Ownership of the data is the largest question. Shirt sponsors are severing clubs from their local communities; they look only at exposure and return on investment. If a global brand funds the ledger, a fifteen-year-old's growth data becomes a marketing asset. If the federation and district communities fund it, it stays a community asset. The founding source decides whether the ledger protects the child or sells him.

It helps to compare other ecosystems. India's Khelo India programme has built a central database of young athletes, and the board has tightened age verification from time to time. Pakistan has tried matching ages against national identity databases. Sri Lanka and the Caribbean lean on school-based structures held by the federations, far more decentralised. In none of these three models is blockchain the core architecture—this is still experiment, not announcement.

Evidence from outside cricket is mixed. Sorare, NBA Top Shot, Socios and Chiliz turned fan sentiment into tokens; they did not raise the credibility of sports data. FIFA launched digital collectibles on the Algorand network in 2026, and that too is collection, not registration. Cricket's blockchain story so far is mostly fan monetisation. The story of protecting a teenage cricketer has not been written.

In my reading, the ledger pays off in the most boring place—the administrative step before a trial. Just as the Impact Player rule in the IPL has rewarded squad depth, ledger infrastructure will reward the big academies: whoever can afford nodes will hold the cleanest records. The rule does not change; the list of beneficiaries does.

So the pilot belongs at the lowest rung—district-level under-16 trials, where the birth register and the school certificate clash most often. One division, two districts, six months, one question: has the record been altered? Small tests before large federal announcements.

Contrarian: technology will not catch age fraud

Now the uncomfortable part. Blockchain cannot catch age fraud; it can only prove that a record has not changed since it was written. The fraud happens earlier, at the table where the union parishad register is written. The question the ledger cannot answer is whether the first entry was true.

Then comes the cruelty of permanence. If a wrongly written date for an eleven-year-old enters the ledger, that error follows him at sixteen. A meta patch can erase a dream before the crowd notices. Correction means appending a new entry, not deleting the old one—and that cultural habit does not yet exist in our administration.

There is another danger in the name of transparency. If teenagers' growth data, ages and failed trials become public, youth cricket turns into a scouting bazaar where children are the product. The reason I write profiles without a boy's name is not squeamishness; it is a design decision. A public ledger and protective discretion cannot coexist.

One more reality: technology is not the scarce thing here; trust is. In 2026 I watched all sixty-four matches of the Russia World Cup and wrote about Kylian Mbappe—a nineteen-year-old who scored four goals and brought France the title. Clairefontaine's real lesson was not technology but patience and a culture of documentation. The French federation recorded a boy's progress decade after decade, by hand, on paper, and later in software. The archive remembers what the scoreboard forgets—and what sustains an archive is administrative patience, not a blockchain.

Takeaway

A ledger is not a scout. A hash can prove a date has not been altered, but it cannot prove whether that boy can bowl six straight overs in the fourteenth over at thirty-eight degrees. That answer lives in a field notebook, in a groundsman's eye, in a coach's note. I dig through transfer windows for the child, not the headline.

The probability of success depends on who runs the first node. A sponsor-funded ledger turns a teenager into another metric. A federation- and district-operator-funded ledger, tied to the field notebook, can reduce age disputes and save careers. The biggest risk is the unregistered child, whose birth never entered any register at all. A ledger can lock that child out unless the design leaves a door for him.

Empty seats still ask who is watching the next generation. The question is not about technology; it is about guardianship. Who will run the first node—the federation, or the highlight reel?