Cricket's Blockchain: The Chain of Timestamps Behind Every Fact

In July 2026, at the open training ground beside the Kitec Stadium in Hong Kong, Mohamed Salah had just joined Liverpool for £36.9m. Every morning my phone filled with unverified claims — that he was moving elsewhere, that a medical had failed, that the deal was dead. On the ground the reality was different: Salah completed his first three sessions, each logged with a date in my notebook, along with 27 direct quotes from club staff. The gap between the rumour outside the fence and the fact inside it is the central crisis of cricket journalism today.

By 2026, cricket's information environment has transformed. A transfer rumour spreads in seconds; a single injury update circulates in ten versions on the same day; a selection debate cites twenty unnamed internal sources, none with a date or a document. Journalism has split between speed and reliability. The fast arrive first; the reliable endure. I belong to the second group.

This is where the blockchain idea works as a metaphor. In a blockchain, each block holds the cryptographic hash of the one before it. Change an old entry and every subsequent hash breaks, and the network catches it instantly. The ledger is not held by one person but by everyone — and change means change with a witness. My cricket reporting is a plain-Bengali version of that principle: every claim backed by a timestamp, every timestamp by a witness, every witness by a verifiable document. That is my ledger.

In May 2026, in Kyiv, Sergio Ramos injured Mohamed Salah's shoulder in the 26th minute of the Champions League final. That night the information storm began: three days, three weeks, the World Cup over. None carried a document. In June I travelled to Russia for Egypt's group. Salah missed the 1-0 loss to Uruguay on June 15, scored a penalty in the 3-1 loss to Russia on June 19, and scored again in the 2-1 loss to Saudi Arabia on June 25. I interviewed two Egypt team doctors and tracked his 24-day recovery — scan to rehab to training return to squad inclusion. From then I added a dated medical timeline box to every injury story. An injury update is never a point; it is a chain.

On June 24, 2026, I was one of ten reporters allowed into an empty Anfield as Liverpool beat Crystal Palace 4-0; the title came on June 25 when Manchester City lost 2-1 to Chelsea, ending a 30-year wait with 99 points. Empty seats do not lie; they only change what the game lets you hear. But reading empty seats as a direct witness of mood is a mistake — ticketing data, acoustics and broadcast sound must be triangulated.

In 2026 I covered Euro 2026 and the Tokyo Olympics: Italy's 34-match unbeaten run, Jorginho's 92% pass completion. I never trust a tactical trend from a single tournament; I test it against three prior tournaments. Christian Eriksen's on-field cardiac arrest on June 12 showed that what was needed first was a timeline, not analysis.

The contrarian point is this: the common belief is that bad journalism comes from a lack of information. My experience says the opposite. The problem is not the volume of information but the chain of verification. It is not the abundance of information that makes analysis — it is the sequence of information. I keep two columns: what happened, and what everyone decided happened. A primary source is not a person; it is a timestamp, a document, a second witness. The notebook starts before the whistle, and the ledger starts before the rumour. The question ahead is no longer who wins at cricket, but how much of what we say about it actually survives verification.