Nobody Kept the Record: Bangladesh's Athletics Archive and Its Uneven Fight with Blockchain

I went looking for a file. Every 100m time from Bangladesh's supposed 2026–2026 sprint window, each one carrying a stamp saying how it was measured. What came back was a blank sheet, two torn typescripts stuck to microfilm at the National Library, and two contradictory numbers for the same race: 10.4 and 10.47. One hand-timed, one electronic. Nobody had ever reconciled them. That was the first red flag, and the archive nobody kept is where this story begins. For more than two years I have been building a single spreadsheet of 140 Bangladeshi 100m results, each tagged with timing method, source and my own confidence level. Everyone else was cutting Facebook highlight reels; I was digging through old meet programmes and newspaper microfilm. That sheet is my real reporter's notebook. I do not trust the highlight reel; I trust the frame before it — and I want to know whose hand was on the number printed beneath it. A couple of years ago, when lockdown emptied the stadiums, I turned to paper: annual reports, ministry grants, federation election notices. What surfaced was not a scandal but something worse. None of the eight divisional headquarters has a synthetic track. The entire operating cost of the national championships sits below a single cricket star's season fee. And out-of-competition doping tests appear nowhere in the athletics budget at all. I went looking for a missing budget line and found a stadium of silence — and that silence is not a crime, just a gap I can document by name. So here is the real question. If the federation ran a blockchain-based results ledger, what would actually change? The technology is not complicated, and it does not need mystique. On a consortium chain every result can be written as three layers: the data (time, wind, device), the metadata (who measured, with what method, which transponder or photo-finish camera, on what date at which stadium), and a cryptographic hash that stitches the record to the next block. Anyone who later tries to turn 10.47 into 10.4 gets no consent from the chain. Electronic timing systems should write straight to the ledger; anyone hand-timing a race must enter on a separate badge that can never be erased. That is the core gain: every number carries an immutable provenance, exactly as a blockchain transaction does. The numbers are clean; the people who keep them are not. Two years ago a sprinter ran 10.29 seconds for the national record. It was documented electronically, and that is precisely why we still have it. Much of the four decades before him survives only on hearsay. The difference is not technology; it is habit. Here is a small scene that sticks with me. On a Dhaka track I watch the electronic board capture the finish-line touch in the final second. But when the TV cameras move away, where does that data live? Usually on someone's desk, in an Excel file, or nowhere. A blockchain works like a recording node here: data enters the ledger while the meet is running and remains as a verifiable timeline long after it ends. Several uses matter more than the hype. First, doping control: sample chain-of-custody, lab codes and transport timestamps can all live in an auditable ledger, so a sample that goes missing leaves a mark in an earlier block. Second, qualification mechanics: for three decades Bangladesh's Olympic athletics entries have been clouded — how much was qualifying standard, how much a universality wildcard? A ledger makes each path explicit: who selected, on what basis, on what date. Third, budgets: if every grant and every expense voucher sits in a distributed ledger, the question of where the money went does not end at a press conference. Fourth, the pipeline: with three domestic meets a year and an Army–Navy–BKSP stranglehold on the podium, where does new talent come from? A searchable youth registry would let district-level times accumulate, and let us test whether a 10.29-second sprinter stands on a thousand domestic marks or on none. All of it depends on one condition — the data has to enter. What specialists call the oracle problem sits at the centre: how does off-chain reality get into the chain reliably? A hand-timed mark written to a chain is a lie that has merely become immortal. Now the part the blockchain festival crowd skips. A ledger prevents forgery; it does not manufacture truth. If a federation does not want to keep records, if data never reaches the server, what does the chain pull from? Nothing beyond an empty block. What my 140-row sheet has said from day one still holds: the biggest gaps are not theft stories but stories of minutes that were never taken. Where a document was never created, blockchain immortalises an empty room. More importantly, blockchain does not make an institution transparent; it merely makes silently rewriting the past impossible. The question remains: who controls the immutable ledger? If the federation runs the nodes itself and keeps the private keys, we walk straight back into the same dependency trap we tried to escape. Decentralisation bolted on as a banner buys no transparency. My oldest line applies here too: I followed the paperwork until the paperwork started following me. One closing image. On a Dhaka track I start my stopwatch exactly in sync with the last television lens. Where the camera stops, the data stops. So the blockchain question is not a technology question; it is a question of will. Do we lay the chain first, or do we first admit the archive was never kept? If we decide neither, the next decade will still show 10.4 and 10.47 sitting side by side.