From a Mislabel to the Blockchain: How an Actor's Ashes Exposed the Source-Verification Crisis

I began with a shot log in Rangpur; now the feed reads me back. In 2026, at 39, after a lower-league playing career, I stood on the touchline at Rangpur Stadium and logged every shot in the Bangladesh Premier League. Abahani Limited Dhaka striker Sunday Chizoba scored 18 goals from 12.4 xG — that single number brought 40,000 views to my first Facebook thread. Back then my belief was simple: data never lies. But this week, an article that slipped into my analysis pipeline shook that belief for the first time. The article carried a label: football. Inside, there was not a trace of football. Its subject was the death of Cuban-Mexican actor Otto Sirgo, his family's funeral arrangements, and their plan to take his ashes to the Popocatépetl volcano. No team, no player, no tactics, no transfer, no xG. A celebrity obituary that walked into a sports feed. That single mislabel opened a question that matters as much as football analysis does today. When we say data never lies, what do we actually mean? Data does not arrive on its own. Every piece of data carries a source, a label, a timestamp. If the label is wrong, the data is not automatically false — but every decision built on top of it becomes false. I am not writing about the blockchain for fun. I am writing because over the past decade, the same disease has spread from football analytics into news delivery: the loss of source identity. Who attaches a football label to an obituary? Who decides which information enters which file? And when that decision is wrong, where does the damage land? Chasing these questions took me to the blockchain's door — and I found that the door is much smaller than I imagined, but its handle is much stronger. Context: how an obituary enters a sports feed Let me lay out the structure of the event. At the centre is Otto Sirgo, a Cuban-Mexican actor. Among his family members is his daughter, Valerie Sirgo. The actor's final wish was that his ashes be taken to Mexico's Popocatépetl volcano, because he loved volcanoes very much. The family first considered using a helicopter to bring the ashes close to the volcano. Facing reality, they later shifted toward a plan to approach on foot. A Mexico City funeral home is also mentioned. And as an institutional source, there is ANDA — Mexico's National Association of Actors, which here is a labour union, not a football governing body. Notice: not one word of football in that paragraph. Yet the article entered a football-analysis pipeline. The likely explanation is a single one — automated keyword or source-feed misclassification. On some general sports portal, the article picked up a sports tag, and from there the error spread. I refuse to look at this through a sporting lens, because there is no sport here to look at. I want to look at it as a sample of classification failure. Because the same pipeline that made this error processes thousands of football articles, transfer rumours, injury updates, and match previews every day. If an obituary can pick up a football label, who will stop a fabricated transfer rumour? Who will avoid mistaking a press release for analysis? That question took me toward the blockchain, because the blockchain's core promise sits exactly here — removing any room for doubt about a piece of information's origin, time, and integrity. My Rangpur experience is useful here. In 2026, when I counted and logged every shot myself, my source was clear — the touchline at Rangpur Stadium, my own eyes, my own notebook. In 2026, standing in Saransk at the World Cup, I logged Croatia's 3-0 win over Argentina with a PPDA of 8.9 and counted Luka Modric's 11.2 km of coverage myself. Then, source and analyst were the same person. Today, when I write analysis from a feed, source and analyst are separate. And that gap is what produces mislabels. I have said many times that Croatia's 2026 run was not luck; it was a code I had to decode. In the same way, this mislabel was not chaos; it was a code I had to decode — because inside it lay a serious weakness in news technology. Core analysis: the missing source is the real crisis Now to where the real information-integrity accounting happens. Of that article's fifteen information points, twelve carried a source field reading: none. In other words, almost every claim inside — the actor's death, the family's plan, the volcano story, the funeral home — came from a completely unnamed source. The core claims rest on two things: one named individual (daughter Valerie Sirgo), and one institutional confirmation (ANDA). This is the most important fact of all. The quality of a news item is not in the beauty of its sentences but in the reliability of its sources. Where twelve information points are unsourced, journalistic standards say that article cannot be treated as ready for republication or citation. Without a named source, the reader holds no tool for verification. Now imagine that same weakness entering football analysis. Suppose an injury update arrives with no source. Suppose a release-clause story comes from a single agent. Suppose a transfer fee comes from an anonymous tweet. As a data analyst, what is my position? My role is the filter. I begin every preview with one xG contradiction, because numbers tell me where the gap lies between popular belief and reality. But if the source of that number is itself suspect, my filter is itself useless. This is where the blockchain's proposal becomes attractive. Imagine every news article, every data file, every transfer claim carries a cryptographic hash. That hash is written to a public ledger, with a timestamp. If anyone alters a single word, the hash changes, and the ledger catches it. If anyone claims to have broken a story first, the ledger shows who was earlier and who was later. Origin, time, integrity — all three bound together in one place. This is the blockchain's most realistic, least noisy use: not money, not tokens — a timeline of truth. In news delivery, many already see this application as a future standard. Content Credentials have already launched, embedding hidden metadata inside images and video to record origin and edit history. The blockchain can offer an even stricter version of that idea — fully immutable, fully public. But here my analyst's mind tells me to stop. Because in Rangpur I learned that data and truth are not the same thing. Data is a record; truth is the meaning of that record. What the blockchain can prove, and what it cannot Here I want to draw the most important distinction. The blockchain can prove that a piece of information was published at a certain time, in a certain form, from a certain source, and that its form was not altered afterwards. Call this proof of existence and proof of integrity. But the blockchain cannot prove that the information is true. If I write to the ledger that it rained in Rangpur today when the sun was shining, the ledger will make my falsehood permanent, but it will not make it true. Immutability immortalises falsehood too. That is the biggest trap. In the same way, the blockchain cannot decide whether an article's subject is football. Classification is a semantic task — it is done by language, context, and judgement. A hash can never say that the story of Otto Sirgo's ashes is not football. If the system that attached the wrong football label is written to a blockchain, the error becomes immutable — and harder to fix. Here I warn against feed worship. Dashboards, models, algorithms can tell me where an article came from. But they cannot tell me what the article actually is. The final judgement must be made by a human who has stood on the Rangpur touchline and seen with their own eyes. So is the blockchain useless? No. It is a tool, not a solution. It adds a proof layer, not a meaning layer. In the news world, the real skill is keeping those two layers apart. And here football helps me. In the transfer market, the difference between those two layers shows up every day. A club says it will sign a player. A tweet says the fee is enormous. An agent says talks are ongoing. The existence of these three claims can be proven; which one is true must be proven separately — by checking the contract structure, the wage bill, the release-clause figure. The blockchain makes the first task easier; it does not make the second task easier. The contrarian angle: the blockchain is not the cure for the crisis Now to where I want to stand against the received optimism. In the source-integrity crisis, many treat the blockchain as a silver bullet. I think that view looks at the problem from the wrong side. First, the core problem is not technological but cultural. A system that leaves twelve information points unsourced does not lack truth-verification — it lacks the habit of source citation. If a club writes false information to the ledger, the ledger will not stop it; it cannot, because the ledger does not know which claim is false. For an outlet reluctant to name its sources, the blockchain creates no accountability. Technology is not a substitute for responsibility; responsibility is a human decision. Second, the blockchain's immutability is itself a risk here. Classification errors exist precisely to be corrected. But if a wrong label is written to a permanent ledger, the path to correction is blocked. We want a system where a source stays immutable but its classification stays correctable. That fine balance does not sit easily inside the blockchain's rigid structure. Third, cost and complexity. Writing every shot log, every small news item, every regional update to a chain is not economically realistic. Who will write a small-league match in Rangpur to a chain? How will an immutable ledger reach those who lack resources? Fourth — and this matters most — the blockchain does not stop people from lying. An agent can write a half-true claim to the ledger. The chain will not verify it. So the duty of verification returns to humans — journalists, analysts, readers. So where is the solution? I think it sits between the two layers. Proof layer: the blockchain. Meaning layer: human judgement. That is, where information came from and who changed it is a machine's task. Whether that information is football, whether it is true, whether it is relevant is a human's task. Blending these two tasks is the biggest mistake of our time. My Rangpur experience offers a test, which I call the Rangpur test. Every model, every label, every claim — I check it against two questions. One: could I have seen this information myself, standing on the touchline? Two: if I am wrong, can I correct it? The first tells me whether the information is real or feed-manufactured. The second tells me whether it is flexible or frozen. The blockchain helps with the first question and can obstruct the second. The Otto Sirgo case fails this test. Because here the football label could never be verified on a touchline. It was a desk decision, not a pitch decision. Reading the media narrative: how an obituary lives, and how fast it dies Beyond the information-integrity question, this event has another layer that I recognise as a football journalist — the life cycle of a narrative. Otto Sirgo's obituary is straightforward and tender. Its tone is respectful. The article's stance is explicitly informative. There is no melodrama here. The most dramatic hook is the wish to bring the ashes to the volcano by helicopter — but the family itself has brought it down to a realistic alternative (approaching on foot). That saves the story from sensationalism. I recognise this structure because it happens in football too. A transfer rumour is born suddenly, rises to the top in hours, then dies under fresh news. An obituary follows the same rule — a small burst at the death announcement, then a rapid decay. Without something new, it cools within days or weeks. The cleverest narrative device here is the mention that the actor loved volcanoes. That small detail converts an unusual request into an understandable, sympathetic story. That is the scaffolding of narrative — editorial framing that makes the story reasonable in the reader's mind. I also notice a subtle signal. The article consciously avoids linking the actor's death to his previously mentioned ailments. That is a familiar editorial caution in obituary reporting. Where the source is weak, the editor at least held firm on one judgement — because nothing could be assumed. That caution is admirable, and it is a lesson for me: where there is no source, not assumption but silence. Here my football mind wants to draw a parallel. With injury reports, I follow the same rule. Whether a player has returned to the pitch, I do not announce until the club or a reliable source confirms it. Because I have seen how fast a wrong injury item spreads in the football market. The blockchain can immortalise that wrong injury item; it cannot replace it with the right one. There is another layer that makes this event more instructive — geographic context. The centre of the event is Mexico, Mexico City, Popocatépetl. That geographic location is tied to no football league. But if someone mistakenly takes it for a football story, they will blend it with Mexico's football identity, club structure, or tournament context. A wrong label does not just misplace one article; it also misrepresents a country's football reality. This is why I say source verification is not only a task of text but of context. A name, a city, an organisation — unless these three align, the label is not reliable. ANDA is a perfect example. It is an actors' labour union, not a football governing body. But if an automated classifier sees the words actor and association and drops it into the sports section, the error is inevitable. A new insight emerges here. To correct classification errors, adding entity rules is more urgent than adding source lineage. That is, on seeing certain names — actors, volcanoes, labour unions — the football label should be automatically withdrawn. This is a mechanical fix, and it has no direct relation to the blockchain. But it is a realistic remedy for one of the biggest weaknesses of feed-based analysis. I also admit my own error here. For years I leaned on the feed. I said data never lies. But I forgot that data carries a label, and that label is written by human hands. Data never lies — true. But a label can lie. And when the label is wrong, the data too lands in the wrong place. The market value of information integrity Now I want to see the matter through the market's eyes, because I am also a transfer-market analyst. Source verification is not only a moral question but an economic one. Imagine a sports data market. Clubs, agents, journalists, bookmakers — all buy and sell information. If, in that market, information's source is not verifiable, every transaction carries a hidden risk. A wrong injury item can move prices. A wrong transfer claim can move share values. In this situation, source verification is an asset — because verifiable information is worth more. The blockchain can give that asset a structure. An immutable record means a history of information that is hard to forge. If agents, clubs, and journalists all write to the same ledger, there will be an account of who said what and when. This can raise market confidence. But — and here is my biggest caution — raising confidence is not the same as securing truth. A ledger creates confidence because it is unalterable. But a ledger does not secure truth because it cannot judge. If market confidence rests on immutability, then false information will sit in the market, unalterable too. Here I want to pull in a real example from the football market. In 2026, when stadiums emptied because of Covid, I tracked 92 Bundesliga matches. The home win rate fell from 43.2% to 33.7%, and home xG per match dropped 0.21. I shared that number with a Rangpur betting group. But that number worked because its source was clear — specific matches from May to July, a specific season, a specific method. If that same number had come from an unsourced feed, I doubt the group would have trusted it. This comparison shows the blockchain's real value. The blockchain does not make a number true; it makes a number verifiable. The difference seems small but is enormous. A verifiable falsehood is less dangerous than an unsourced truth, because a verifiable falsehood can be caught. The systemic risk of misclassification Now I want to mark the risk level clearly, because my work is learning to map risk. The biggest risk in this event is not a football risk; it is a systemic risk — model contamination. If a football model accepts this obituary as training data, the model will learn something wrong. It will learn that an actor's death, a volcano, and a labour union are football context. In later analysis, that contamination will spread. A wrong label is thus like a virus, passing from one dataset to another. The second risk is source fragility. Twelve information points are unsourced, and the core claims rest on one individual and one institution. No decision can stand on such a fragile foundation. Verification needs a named, reliable outlet. The third risk is inference about the cause of death. The article consciously did not state a cause. That uncertainty should be respected, not filled with inference. An analyst who passes inference off as data is their own worst enemy. These three risks lead me to one conclusion. This article should be moved out of the football dataset, and preserved as a sample of classification error. As a sample it is valuable, because it shows us where the feed goes wrong. I also see a positive possibility. This event is a clean, reliable example that analysis without source verification is incomplete. Blockchain advocates can use it as a tool — to show how vital timestamps and source records are. But I would caution them too. Immortalising a wrong label does not bring a solution; the solution comes from keeping the label correctable. That is, we need a balance between the blockchain's rigid immutability and classification's flexibility. A system that preserves information but forbids correcting errors is a museum, not a newsroom. One lesson is clear in my Rangpur classroom. Logging every shot means verifying every shot. When I checked Chizoba's 18 goals against 12.4 xG, I did not just reconcile numbers — I asked, why this gap? Asking that question is analysis. A label is not analysis; a question is. The blockchain can give me numbers. But it does not teach me to question numbers. That I must learn — either on the touchline, or in the search for a source. Tribute and the limits of memory I am writing this article about an actor's death, though I am a football analyst. This is uncomfortable, and I do not want to avoid that discomfort. Because that discomfort teaches me where analysis ends. Otto Sirgo's family is going through a difficult time. Their decisions, their grief, their plans — at the centre of all this is a human being, a family. No ledger, no hash, no timestamp can hold that grief. Technology preserves information; technology does not preserve meaning. In Rangpur I learned that writing about data requires setting emotion aside. But I also learned that writing about data must not forget people. An actor's ashes, a volcano, a family's last wish — these are not rows in a dataset. They are the final chapter of a life. So my position in this article is dual. As an analyst I say, this article is not football, and it should not sit in a football dataset. As a human I say, this story is bigger than a football dataset. It belongs where lessons of news integrity are drawn. Here the blockchain's limit is clearest. The blockchain can make the existence of information permanent. But a family's grief, an actor's final wish, a love of a volcano — these need no technology to be made permanent. They live in human memory, and there they should stay. My work is about data; my duty is about truth. Standing between the two, I make one simple decision today — I will not call this article football. Because in Rangpur I learned that a wrong name is no less dangerous than wrong information. Final thought: the signal for the next round So what signal do I take from this? First, source verification is now part of analysis, not decoration. Every data analyst should attach a source to each claim, and say clearly when there is none. My Rangpur test works exactly here — can the information be seen on the touchline, and can it be corrected if wrong. Second, the blockchain is a tool for news integrity, but it is not the cure for the crisis. It adds a proof layer, not a meaning layer. The analyst who blends these two layers will fall into a new kind of blindness — where everything is verifiable and nothing is understood. Third, the most realistic path to correcting classification errors is not technological but institutional — entity rules, source citation, and human judgement. A feed never knows on its own that Otto Sirgo is not football. A human must know that. Fourth, a verifiable falsehood is less dangerous than an unsourced truth. That single sentence is my biggest lesson today. Because a verifiable falsehood can be caught, corrected, and assigned responsibility. But an unsourced truth is only a belief, and analysis cannot stand on belief. I began my journey on the Rangpur touchline on the faith that data never lies. Today I write with a corrected faith — data never lies, but a label can lie. And when the label is wrong, the honesty of the data does not save us. Only one habit saves us — asking questions. Asking questions is now the scarcest form of information security. I began with a shot log in Rangpur; now the feed reads me back. What the feed showed me was an actor's ashes, a wrong label, and a room with no source. My signal for the next round is one thing — from any feed that claims to give you a truth, demand one question: where is the source? And if it cannot answer, remember that an unsourced truth is really a story, and trusting a story is the reader's job, not the analyst's.