Blockchain and Cricket's Age Verification: Pencil Marks Erase, Blocks Do Not

On October 8, 2026, at the D.Y. Patil Stadium in Navi Mumbai, the floodlights came on as a group-stage match of the FIFA U-17 World Cup had just ended. I was a 26-year-old prospect scout, sitting in a lower tier filling a ledger. Forty-two wingers were in that ledger, each with scan frequency, weak-foot passes, recovery runs. England's Jadon Sancho completed nineteen take-ons across four matches; Rhian Brewster scored eight goals. Everything coded, dated, itemised. Yet one name in that ledger was written in pencil. It was not a star's name. It belonged to a boy whose age carried a question mark on paper. After the match he stood at the edge of the pitch showing a journalist a photograph of his birth certificate, as if that single slip of paper were the only evidence of who he was. That night I did not understand that the weight of that slip would one day become the whole industry's question. Since that night one sentence has circled in my head: if a piece of paper can lie, where is the truth actually written? I was born in Bangladesh and have spent most of my working life in India covering cricket. The youth pathways of both countries run almost identically: from Dhaka's age-group circuits to Kolkata trials, then on to the turf of Navi Mumbai or Bengaluru. On that path a boy's greatest asset is not his talent but his age. Age decides which team he plays for, which under-16 or under-19 side calls him, and which trial suddenly rules him too old. I have seen the same boy play under-14 one year, change form, and return to under-14 the next. His age does not grow; only the date on paper shifts. This is not a story about morality. It is a story about a system in which the verification machinery is weak and the profit arithmetic is perfectly clear. Today's age-verification methods stand on three layers: birth certificates and school records, board registration, and radiological bone-age tests — an X-ray of the wrist analysed by the TW3 or Greulich-Pyle method. Every one of those three layers shares a common weakness. Each is centralised. Each depends on paper. And each can be changed by one person's decision. In a system where entered data sits in one place and one person holds the power to alter it, the truth survives on goodwill, not on technology. This is where blockchain enters. It is worth defining what blockchain actually is. It is a distributed ledger. Every entry is stored as a block; every block carries a timestamp and the cryptographic hash of the previous block. To alter one block you must alter every block after it, and that change registers across every node in the network. In plain terms: once written, a blockchain entry cannot be erased, only appended to. Imagine that structure applied to cricket's age verification. A boy's first registration becomes a genesis block — the hash of his birth certificate, the hash of his school admission record, the date of his first club registration. Every age-group match, every trial, every board approval then attaches to the next block. If someone later claims he is two years younger, every node in the network says the same thing: your genesis block recorded a different date. The biggest shift here is not technological but structural — power moves away from the centre. Today a clerk, a board official, or an agent can alter a document and rewrite an entire career. On a blockchain that individual no longer holds that power, because every change is visible on a public ledger. Let me give a small example of my own. At the 2026 Navi Mumbai tournament I built a Youth Pressure Index across forty-two wingers — scan frequency, weak-foot passes, recovery runs combined. Three club analysts eventually requested my ledger. But the problem was this: the ledger lived with me, in my handwriting, at my discretion. Anyone could later claim I had added Sancho's name after the match. There was no timestamp, no signature. This is precisely where blockchain matters. Had the ledger sat on a public chain, Sancho's nineteen take-ons or Brewster's eight goals would have been bound to a timestamp — no one could backdate them. For scouting reports this is no small thing; a prospect report's credibility depends heavily on when it was written. Before the 2026 World Cup in Russia I built a 22-player under-20 board. France's Kylian Mbappe ranked first on my weighted model. He scored four goals in seven matches, scored in the final, and won Best Young Player. I tracked thirty-one sprint recoveries and twelve shot involvements. My employer later sold three club briefs off that board. The question here is simple: had my board lived on a blockchain, my claim that Mbappe was number one before the tournament would carry immutable proof. Today someone could argue I entered it later, with hindsight. Only a system in which forecasts cannot be backdated delivers real transparency. Applied to age verification, the framework is even more direct. Imagine that the moment a birth certificate is issued, a hash of it is written to a block. Then school admission, then the first district trial, then the state side — each step appends an age timestamp. If a boy tries to return to under-14 a year later, the gap between his genesis block date and his latest entry exposes him. One point must be clear. Blockchain does not raise or lower a boy's age; it only guarantees what a specific piece of information was on a specific date — and that it can no longer be changed. At the centre of cricket's age debates sits exactly this question: who said what on which date, and has it since been altered? In 2026, during the coronavirus hiatus, I worked remotely from Goa. Hyderabad FC's Rohit Danu, eighteen, became one of the youngest scorers in ISL history. The stadium was empty; no crowd noise. Only the coach's instructions and the sound of feet carried through. Across three matches I logged twenty-three off-ball runs and six pressing triggers and filed a fourteen-page report recommending him for a national youth camp watchlist. The weakest point of that report was one thing — anyone could question its date. 'When did you write this, before or after watching?' To answer that I had only my own assertion. In a blockchain-based system the report's file hash and timestamp would both sit in a block. In 2026 I built a load ledger on Spain's Pedri. Six Euro matches and six Tokyo Olympic matches — 629 passes at the Euro, a silver medal in Tokyo. Seventy-three club-and-country appearances that season. I built a muscle-injury probability model; two clubs requested my fatigue appendix. For a load ledger, blockchain has a clear use: if every match minute, every travel date, every recovery session were immutably recorded, no club could later say it did not know how heavily he was burdened. The real problem in workload management is not a lack of data but the opacity of data. This is where cricket's commercial layer enters. To many, blockchain today means fan tokens or NFT collectibles — digital tokens for fan affiliation, or digital editions of iconic moments. That market is large, loud, and I am sceptical of it. In my view, blockchain's real value in cricket is not in the fan market but inside the system. Fan tokens rest on fan enthusiasm; a youth registration ledger rests on truth. The first is a bicycle; the second is a foundation. The louder the commercial glitter, the less visible the quiet work beneath. Now the other side. My profession is prediction, but treating blockchain as a guaranteed fix is a mistake. The first problem is conceptual, not technical: blockchain only verifies what was written beforehand. If the very first block is false, blockchain seals that falsehood for a lifetime. Call it garbage in, certified garbage out. An agent who forges a document today, if he can insert a fake birth certificate at registration, has not been caught — he has been made permanent. The second problem is one of power. Who writes the genesis block? If the board writes it, and the board also verifies it, this is not a decentralised system — merely a digital ledger instead of a paper one. Technology does not change the distribution of power unless the answer to who writes and who verifies changes. The third problem is practical. Rural academies in Bangladesh or India still run on paper and pen. A blockchain node, internet access, trained operators — these are luxuries there. If the system works only for boys at large city academies, then the boys most exposed to fraud are the ones left out. The fourth problem is ethical, and I consider it the most important. Blockchain entries cannot be erased. If a teenager's birth certificate, his family's financial status, his school record all sit on an immutable public ledger, that raises the question of his consent. A technology that says 'nothing will be forgotten' must answer one question: whose data, whose permission, and who wants to forget? The final problem is the most merciless. The underlying incentive to cheat cannot be erased. If the reward for a place in an under-16 side is large enough that a family will forge a document, they will also seek ways around blockchain — hash swaps, false identities, node capture. Every new verification layer creates a new gap; that is a permanent stratum in the archaeology of youth cricket. So what is the path? I am not dismissing blockchain; I am placing it. It is not alone the solution to age verification; it is a layer of proof. Bone-age tests, birth certificates, school records — if their results are written block by block, an immutable timeline forms. When a boy's age is questioned, the question is no longer what the paper says but what the ledger says. To me the resemblance between blockchain and cricket runs deeper. My profession is a specific kind of archaeology — I dig the strata beneath the pitch: unverified pre-board coordinates, academy migration, the gaps in age verification. Every boy's career is really data layered in strata. The resemblance between blockchain and the archaeology of age verification is this: both want a ledger whose lower layers no one can quietly alter. I keep two boards. One for the market, one for the museum — a collection of the signals the market misses. If blockchain truly works, the museum board will shrink, because fewer signals will be lost. And my ledger of forty-two names? It is still with me, and the pencil mark is still there. I have not erased it. Because that single mark reminds me daily that the weakest name in a system is often the most important one. Whether blockchain arrives is the board's decision. But my question does not change: do we truly want a system in which no one can erase the pencil mark in the ledger? Or do we want to keep the pencil in hand, merely digitised?