HomeAsian CricketCricket Written on the Blockchain: That Night at Chinnaswamy and the Immutable History of One Run
Asian Cricket
Cricket Written on the Blockchain: That Night at Chinnaswamy and the Immutable History of One Run
**মূল উত্তর**: ২০১৬ সালের ২৩ মার্চ, ব্যাঙ্গালোরের চিন্নাস্বামী Stadiumে আইসিসি ওয়ার্ল্ড টি-টোয়েন্টির ম্যাচে ভারত ১৪৬/৭-এর জবাবে বাংলাদেশ ১৪৫/৯-এ থামে; শেষ বলে মুশফিকুর রহিম রান-আউট হওয়ায় ভারত ১ রানে জয়লাভ করে। **মূল তথ্য**: - ম্যাচটি অনুষ্ঠিত হয় ২০১৬ সালের ২৩ মার্চ, এম. চিন্নাস্বামী Stadium, ব্যাঙ্গালোরে। - ভারত ১৪৬/৭; বাংলাদেশ ১৪৫/৯; ফল: ভারত ১ রানে জয়ী। - বাংলাদেশের প্রয়োজন ছিল শেষ ৬ বলে ১১ রান; শেষ বলে ১ রান দরকার থাকা Statusয় মুশফিকুর রান-আউট। - ২০১৮ নিদাহাস ট্রফি ফাইনালে (১৮ মার্চ, কলম্বো) দিনেশ কার্তিকের শেষ বলে ছক্কায় বাংলাদেশ আবার হারে। **উৎস**: আইসিসি ম্যাচ রেকর্ড, ইএসপিএনক্রিকইনফো; ২৩ মার্চ ২০১৬ | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর**: প্রশ্ন: ২০১৬ ম্যাচে শেষ ওভার কে Bowling করেছিলেন? উত্তর: ভারতের হার্দিক পাণ্ড্য। প্রশ্ন: মুশফিকুর রহিমের রান-আউটে উইকেটরক্ষকের Role কী ছিল? উত্তর: মহেন্দ্র সিং ধোনি দ্রুত স্টাম্প ভেঙে রান-আউট সম্পন্ন করেন। প্রশ্ন: এই ম্যাচটি বাংলাদেশের সেমিফাইনাল সম্ভাবনায় কী প্রভাব ফেলে? উত্তর: হারের ফলে বাংলাদেশ টুর্নামেন্ট থেকে বিদায় নেয়, ভারত সেমিফাইনালে ওঠে।
I filed my first World Cup story from the stands, with rain on the page and 14 percent battery on my phone. That first file was less report than prayer. Rostov-on-Don later taught me that fourteen seconds can erase a printing press. But cricket had taught me this lesson long before—on March 23, 2026, at the M. Chinnaswamy Stadium in Bangalore, when Bangladesh needed 11 runs off the last six balls. Mahmudullah Riyad hit a six off the first ball of the nineteenth over—five needed off five. Then came a wicket, then another. The equation shrank to two off three, then one off one. And on that final ball, Mushfiqur Rahim ran for the winning run, and MS Dhoni's lightning hands broke the stumps. The scorecard recorded: India 146/7, Bangladesh 145/9, a one-run defeat. That night I wrote a line in my rain-stained notebook: 'Cricket's history is actually a blockchain.' Every ball is a block, and once written, it cannot be changed.
This was the 2026 ICC World T20, Super Ten stage, Group Two. India entered the final group game with a semifinal spot secured; Bangladesh faced a win-or-go-home equation. The Chinnaswamy gallery split into blue and green, but both sides were one in emotion. India batted first and scored 146/7, with Virat Kohli's 24 and Rohit Sharma's 18. Bangladesh's response began dreamlike—Tamim Iqbal's 35, Soumya Sarkar's 17. But the run rate hardened into stone through the middle overs. Mashrafe Mortaza's side reached the final-over equation at 11 off 6.
These 'almosts' are the real ledger of Bangladesh's cricket identity. A one-run loss, a two-run loss, a last-ball loss in successive tournaments. Barely two years later—on March 18, 2026, at Colombo's R. Premadasa Stadium in the Nidahas Trophy final—the same picture returned. Bangladesh made 166/8, and India needed 5 off the last ball. Dinesh Karthik's six broke Bangladesh's heart again. A nation's cricket emotion is built from the accumulation of these 'almosts.' Each defeat is a block, mathematically chained to the defeat before it. That is how an emotional, immutable chain is built—what we call Bangladesh's cricket history.
What is blockchain's promise? A decentralized ledger—each transaction a block, each block sealed to the previous one by a cryptographic hash; once written, no single powerful person or institution can alter it. Trust is unnecessary because every node holds a copy of the same ledger. Now look at cricket. Cricket invented its own blockchain in the nineteenth century—the scorecard. Every ball is a transaction, every over a block, every wicket an immutable entry. The umpire is the consensus node: his raised finger means the block is committed forever. No match reporter, no editor, no board president can delete a single entry. Blockchain tells a story of decentralized trust; cricket's scorecard is older and harder—here, instead of trust, stands the iron of the rules.
Read that 2026 final over as a blockchain. Every ball has a hash—time, place, result. The first block is beautiful: Mahmudullah's six, perfect timing, the gallery's roar. Verified, written in the ledger, a story forever. The second block is heavy: Mahmudullah's wicket. It records the end of a hope, the death of an innings. The third and fourth blocks dance with runs and wickets—a breathless arithmetic, each ball sending waves through the gallery. And the last block, the final ball of the nineteenth over, is the chain's most precise entry: Mushfiqur's run-out. Here, 'time' was the hash protocol. The gap between Dhoni's stumping and Mushfiqur's grounding was less than one blink. TV replays, the third umpire's zoom, thousands of live-score refreshes—none of it could delete that block. Because that is the ledger's core law: once written, it stays written. Anyone can fork, anyone can keep a different account on their own node—but in the match referee's official register, that entry is immortal.
For years, I have sat in grounds and learned that the gallery's memory is a more reliable ledger than the scorecard. In the Mirpur gallery, I understood that a city's cricket emotion is not measured by stadium capacity but by the force of its voice and the depth of its silences. On that 2026 night, in the northern gallery at Chinnaswamy, I saw a strange sight: even amid the wave of despair, some people were smiling. It was not sorrow—it was a kind of recognition that this defeat was a block that would stitch Bangladesh's cricket story more tightly together. The next generation will not see this match on a scorecard; they will hear it as a story—from grandmothers, on friends' terraces, behind Dhaka's rickshaws. These memories are the real decentralized ledger—stored in thousands of heads, impossible to erase.
But not every layer of the blockchain metaphor is just. In the age of DRS and Hawk-Eye, we thought error-blocks would no longer join the chain. What actually happened was the opposite: controversy did not decrease, it relocated—from the field to the review room, from the umpire's finger to the gray zones of the rulebook. 'Umpire's Call' is this ledger's greatest paradox: the register claims to be infallible, yet inside it a space remains for 'guesswork.' The technology that came to erase human error now must submit to the limits of human perception. I have seen countless matches where two umpires reached different decisions from deceptively identical ball-tracking images. An immutable ledger is not necessarily a just ledger—that is a false belief. What technology has done is change the hash of the controversy; the core debate, that eternal 'what if,' still lives inside the chain.
In the future, artificial intelligence may sit in the umpire's chair; the scorecard may be written by perfect algorithms. But that Chinnaswamy night, that run-out, that one-run arithmetic—no algorithm could make it more real than it already is in the gallery's eyes. Fourteen seconds can halt a printing press, but not a single block can be cut from the gallery's memory. The question remains: do we want a perfect, cold, lifeless ledger—or do we want this chain, built from human error but filled with love? I know my answer. It is my gallery's memory.


Related Players
Recommended
Empty Seats, Burning Screens: Where Asian Cricket's Money Sleeps Now2026-09-25
Tournament Premium: Why Asian Stars' Value Shifts in a Single Franchise Season2026-09-24
Old Pitch, Dew and the Fixture List: What Dubai's Night Really Decided in Asia's Final2026-09-24
The Silence of the Middle Overs: Bangladesh's Two-Run Gap in Asian Tournament Cricket2026-09-24
Recommended
The Auction Window: Money, Bodies and Time in Asian Franchise Cricket2026-09-25
The Auction Hammer and the Wound of the 79th Minute: How Asia's Transfer Window Rewrites a City2026-09-25
448/6 Declared: Pakistan's Error in Rawalpindi Was Not the Declaration2026-09-24
T20 World Cups in Asia: The Host Has Gone Home Empty-Handed Three Times — An Audited Ledger2026-09-24
Not the Token, the Contract: Blockchain's Quiet Entry into Gulf Cricket2026-09-24
Recommended
Asian Test Cricket: What the Home Scoreline Hides, and What the Review Clock Confesses2026-09-25
The Gulf Ledger: Asian Cricket, the Franchise Market, and the Blockchain Money That Vanished2026-09-24
Cricket Written on the Blockchain: That Night at Chinnaswamy and the Immutable History of One Run2026-09-24
From Sylhet's Logbook to Rawalpindi's Ledger: The Quiet Shift Inside Bangladesh's Test Side2026-09-24
Recommended
Auction Prices and NOC Strings: Asia Cricket's New Transfer Window2026-09-25
Cricket Written on the Blockchain: That Night at Chinnaswamy and the Immutable History of One Run2026-09-24
The Gulf Ledger: Asian Cricket, the Franchise Market, and the Blockchain Money That Vanished2026-09-24
448/6 Declared: Pakistan's Error in Rawalpindi Was Not the Declaration2026-09-24
Old Pitch, Dew and the Fixture List: What Dubai's Night Really Decided in Asia's Final2026-09-24
