From Age Verification to NOCs: Where Blockchain Actually Fits in Asian Cricket

9 February 2026, Senwes Park, Potchefstroom. Bangladesh beat India in the final of the Under-19 World Cup. I watched it on recorded footage from a room in Dhaka, not live, because I did not have ground access at the time. When the match ended I did not close the notebook. I copied the eleven names off the scorecard and added a new column beside them: what is the proof behind the birth date on this name? The column stayed empty.

Six years later that empty column is still the largest question in front of me. Cricket has been hearing the word blockchain with increasing frequency, fan tokens, NFT tickets, digital collectibles, on-chain player passports. Every time I read one of those announcements I end up at the same place. The hardest part of the problem blockchain claims to solve was never written in that column. Who enters the information, and whether that person tells the truth while entering it, is not a question a hash function answers.

I opened the first notebook and the 2026 noise went quiet. I was a kinesiology student in Mymensingh then, logging Kylian Mbappe's 63 positional data points across France's seven World Cup matches in a three-column template: raw number, video timestamp, context. That template became my profession. The problem is that I write the timestamp by hand. Anyone can claim their clip is from that day. If proof is demanded, all I can produce is my own notebook.

This is where the blockchain question genuinely begins, and where most of the conversation takes the wrong turn.

In Asian cricket the blockchain question is not a technology question. It is a question of administrative truth. Who files what, who verifies it, and who keeps the record of that verification. Technology can only touch the last step.

The empty stadium archive still has a pulse if you listen. When the Bangladesh Premier League was suspended after five rounds in 2026, I rewatched 120 matches and built a database of 200 players. That was when I understood that the value of information lies not in its volume but in its certification. A club director once asked me how I could prove a clip was from last season, from that venue. I could not. I could only say the date was written this way in my notebook.

That question now sits at the centre of Asian cricket's Under-19, Under-16 and domestic age-group structures.

Asian cricket's supply chain is split into two layers. One layer holds the ICC Under-19 World Cup, Asian Cricket Council tournaments, and the domestic age-group circuits of Bangladesh, India, Sri Lanka, Pakistan, Afghanistan and Nepal. The other layer holds the expansion of franchise cricket, where a 19-year-old can be juggling four contracts across three countries in a single season. Between the two layers sits paperwork: birth registration, age-verification reports, NOCs, clearance letters, agent agreements.

Much of that paperwork is still on paper. Some of it is in PDFs that anyone can edit without leaving a trace. If an Under-16 age-verification file is lost, it does not come back. And if someone quietly changes it, there is almost no way to catch it.

What blockchain can supply here is a layer of immutability. Once an entry is written to a ledger it cannot be secretly altered later; it can only be corrected through a new entry, and that correction stays visible. In cricket administration that is an audit trail, which today every board keeps separately in its own files, with no way to reconcile one against another.

First practical area: the age-verification audit trail.

Birth registration gaps across South Asia are an old administrative problem. Where registration is weak, cricket boards lean on bone-age testing, dental examination or medical opinion. Those methods produce contested results, and each board stores them differently.

Blockchain cannot make the test accurate, but it can do three things. It can record the date, method, examining doctor and outcome of every verification on a single ledger that survives a change of board officials. It can chain a player's progression from age-group sides to the national team into one continuous record, reducing the risk of a lost file. And it can give the player a verifiable copy of his or her own record, which is not possible in an agent-controlled system.

That third point is the least discussed in Asian cricket. For a 16-year-old, holding his own age-verification document means holding partial control of his own career.

Second practical area: NOCs and releases.

This is where the most usable application hides, and it is the least glamorous. When a board permits a player to appear in a foreign franchise league, an NOC is issued with a validity period, conditions and sometimes a recall clause. If the same player is contracted to two leagues at once, priority is decided by the dates and terms on that document.

Today each board keeps this account in its own way. When a dispute arises, proof depends on emails, WhatsApp messages and internal files that no party can verify neutrally. A shared ledger where boards, league operators and player representatives see the same entry will not eliminate disputes, but it will sharply cut the time they take to resolve.

Football does this through FIFA's Transfer Matching System, mandatory since 2026. Two clubs must submit matching information or the transfer does not complete. Cricket has no central equivalent.

Third practical area: certification of scouting archives.

Here is the weakness in my own method. I have worked in three columns since 2026: raw number, video timestamp, context. The problem is that the timestamp is under my control. If the video is later edited, the timestamp becomes a lie.

A capture-time hash, a cryptographic fingerprint written to a ledger at the moment of recording, can reduce that weakness. It does not mean the video is true. It means the video existed in that state at that time and was not altered afterwards. In a scouting report that distinction is enormous.

When a scout tells a club director that a boy played a particular shot off a particular delivery at a particular venue last October, the director's first question is how do you know. Today the answer is that it is written in my notebook. Tomorrow the answer could be that the capture hash was registered on this date in this ledger, and you can verify it yourself.

Fourth practical area: transparency in contracts and agent payments.

A young Asian cricketer's first professional contract is his least protected transaction. Agent commission, image rights, bonus conditions, release clauses, much of this never fully reaches the player's family. A smart contract cannot fix all of it, but it can make the payment stages visible, so both sides can see how much commission is being paid and to whom.

Caution is needed. The advantage of hiding contract terms sometimes belongs to the club, sometimes to the agent, sometimes to the intermediary. Whoever holds that advantage will not volunteer transparency. Technology here is not a driver, only a tool.

Fifth practical area: fan assets and ticketing.

This is the area that has generated the most noise and produced the least structural change. In 2026 the ICC announced a digital collectibles partnership with FanCraze, and Cricket Australia worked on NFT projects. The commercial logic is clear: a new layer of fan engagement and a new revenue stream for boards and clubs.

But that stream does not change the structure of the game. It is market expansion, not sporting development. And this is where my scepticism is sharpest.

The biggest weakness of blockchain in Asian cricket is the oracle problem: the human being at the point of data entry.

Hash a false birth date and it stays false, only now it is immutably false. The chain knows nothing about truth, only about who wrote what and when. If an official, a family or a club files wrong information under pressure, the ledger preserves it forever rather than correcting it.

I see a parallel in the third-umpire review system. The rule says only clear and obvious errors will be corrected. But how clear and how obvious is itself a subjective space, and a great deal of judgment hides inside it. Likewise, information written to a blockchain is verifiable, but who sets the verification standard is an entirely political question. The technology claims to remove the need for trust while merely relocating it.

The second problem is cost and access. Running blockchain infrastructure is not realistic on the budget of an associate member board unless the ICC supplies it centrally. In places where the Under-19 structure is still struggling, the prerequisite is not a ledger but a reliable connection to civil birth registration.

The third problem is incentive. Transparency arrives when transparency is more profitable than opacity. In franchise cricket nobody wants to publish the real arithmetic of player movement, because publishing it removes the negotiating advantage.

The fourth problem is the economics of fan tokens. The cricket fan-token market remains largely a brand contest rather than genuine value creation. Large clubs and boards use it to convert sentiment into revenue, and those who fall behind launch tokens because rivals did. Long-term value for the fan depends on what the club does on the field, not what it writes on a chain.

My second doubt is more fundamental. Most of the problems blockchain claims to solve in Asian cricket are not information-technology problems. They are problems of how power is distributed. Who publishes an age-verification result, who can withdraw an NOC, who gets to see an agent's commission: these are political decisions. A ledger does not make them fair automatically. It only makes them permanent.

The same scepticism I hold about the football transfer market applies here. Much of the bidding war among elite clubs is brand competition rather than sporting need. Real value is created at smaller clubs, where the arithmetic is clear and the need is concrete. Cricket's equivalent is the domestic circuit, where there is no ledger and no camera, and where the actual scouting information is produced.

So what is the most realistic path for blockchain in Asian cricket? Three stages. First, a central registry of player identity and age verification, run by the ICC or the Asian Cricket Council, with read access for member boards and write access restricted to designated authorities. Second, a simple ledger for NOCs and releases, with validity periods and conditions visible, and no board able to unilaterally erase an old entry. Third, capture-time hashes attached to domestic match video archives, strengthening the certification of scouting reports.

None of the three involves fan tokens or NFT collectibles. They are administrative, dull, and uninteresting as journalism. Yet all three look directly at that empty column.

I think about my 2026 Ounahi report. Twelve pages citing 89 percent pass accuracy and 12.3 kilometres covered per match, and the club could not meet the eight million euro fee. In January he joined Marseille. Ounahi was not a discovery. He was a confirmation of a pattern. My report proved the method worked while the budget did not.

My expectation for blockchain is similar. The technology will not discover anything new. It will only show us which pieces of information we have believed for years without keeping proof.

If a central player registry goes live in the next Under-19 cycle, if a member board agrees to publish hashes of its domestic video archive, if an NOC dispute is settled for the first time on the basis of a visible ledger, the change has begun. If the next three years bring only more fan tokens and more digital trading cards, the technology has leaned toward its weakest use.

I have added a new column to my notebook. It reads: where is the certification for this information? In most rooms the answer is still blank. The question remains, and the fact that it remains is the work.