Nine Layers of Esports Analysis: From an Empty Dataset to Blockchain-Verified Evidence

Last month, in an esports scrim room in Sylhet, I opened a spreadsheet and stopped. The left column held patch numbers, the right column held round finish times, and between them sat a wide, empty column. The coach who handed me the file said flatly, "There's video of the match, there's a score, but there's no log of why that round was lost." That empty column is the central crisis of esports analysis today—we archive results and lose the reasons.

In August 2026, watching the men's 100m final at the London World Championships on a buffering stream, I nearly made exactly this mistake. Usain Bolt finished third in 9.95 seconds, behind Justin Gatlin (9.92) and Christian Coleman (9.94). The reaction times were Bolt 0.183, Gatlin 0.138, Coleman 0.123. The medal was decided in the first ten metres, not the last forty. From that night I stopped writing emotional recaps and began every piece with a split table, a reaction-time column, and one causal question. In esports I look for that same discipline—and stumble in exactly the same place.

Context: analysis is not reading a scoreboard

A match result is never decided by a single cause. A patch changes who is strong, a format changes who survives, a visa deadline changes who reaches the stage, and a sponsor's hand changes who keeps their roster next season. Without separating these causes, analysis becomes a chase after results, where every explanation flips overnight.

International esports desks now work in two stages. Stage one pulls information points, core viewpoints, and relevant entities from the source material—the raw ingredients. Stage two lays a nine-dimension framework over those ingredients to produce professional analysis. The relationship is like a kitchen: stage one brings vegetables from the market, stage two cooks them. If the market comes back empty, there is no answer to what goes in the pan. The day I saw that empty spreadsheet column, I understood that many esports desks suffer from this empty-market problem daily—the data exists, but it is not traceable, verifiable, or reusable.

Core analysis: nine layers, one question—where is the evidence?

1. Patch and meta. This is esports' most dynamic layer. A patch note may run a few hundred words, but its impact lasts a season. An analyst must first know which character or weapon became strong, who gained and who lost. The problem: claims about patch impact are easy, proof is hard. A Bangladeshi mobile esports team once showed me how a small update suddenly killed their most reliable strategy. But they had no full data on the change—only a feeling. Feeling is the first step in reading a meta, but it cannot be the basis of a decision.

2. Tournament system and format. Single elimination, double elimination, Swiss, league points—each format demands a different skill. In single elimination a bad day means exit; in league points, patience pays. How format reshapes team building, rest days, and map ban-pick is the core question. Many analysts treat format as mere scheduling. Format is like heat seeding in track and field—who runs in which lane already shifts the likely outcome.

3. Team and player. A strong team on paper is not a strong team on the server. Role fit, chemistry, and bench depth must be read separately. A player's form curve, KDA or rating, and risk must be judged at the table, not from a highlight reel. Whenever I get news of a roster change, I first ask—will the new player fill the old role, or will the whole system change? Without an answer, the news stays incomplete to me.

4. Regional landscape. The same region can be superb in one title and weak in another. How deep South Asia's mobile esports talent pool runs, how steadily academies produce players, and how wide the gap to international results is—without these three questions, a regional report becomes a chant of patriotism. A region cannot be identified without international results, and cannot be seen the same way across titles, because a region's real strength shifts by game.

5. Club finance and business. Sponsorship revenue, league or publisher distributions, salary expenses, capital injection—without the state of these four pillars, no roster change makes sense. Why a team let its best player go is often not inside the game but inside the cost sheet. Many analyses skip this layer because the numbers are hard to gather. But an analysis that avoids the money has really understood only half of roster policy.

6. Rules and governance. Publisher, league, and national federation—three different rule systems operate at once. Match-fixing, boosting, contract disputes, minor protection—these issues carry precedents, and precedent is the yardstick for future risk. When I write about governance, I never write only an accusation; I write which rule broke, who is investigating, and what punishment followed a past case.

7. Risk profile. Competitive, financial, personnel, rules, public opinion, and systemic—these six risks sit in a matrix showing how likely each is and how large its impact. Risk analysis is not prediction; it is a map of possibility. Prediction says what will happen; a risk map says what could happen and how ready you are.

8. Public narrative. The heat of public opinion and the foundation on the field are not always the same. When a team's win is being trumpeted to the extreme, ask—does that heat rest on consistent results, or on a sample of two or three matches? Measuring the ratio of social-media intensity to real skill is this layer's job.

9. Industry transmission. Upstream, a publisher's decision travels through clubs, tournaments, and streaming platforms to sponsors, derivative markets, and the mainstream. Without understanding this chain, a small change looks like a huge crisis, and a huge crisis looks small.

Contrarian angle: the enemy of analysis is not bad analysis, it is unverifiable data

The comfortable assumption is that the problem with esports analysis is wrong interpretation. My experience differs. The problem is data whose birth, path, and edits no one can verify. Who created a scrim log, when was it updated, who later altered a number—without answers, analysis however refined stands on sand.

This is where blockchain becomes relevant. I do not look at blockchain through a cryptocurrency lens; I see a tamper-evident ledger—a book where, once an entry is made, it cannot be secretly changed later. In esports this applies in three places. First, hashing scrim and practice logs onto a chain, so no team can later deny how many hours it practised on which patch. Second, permanently recording tournament match data and version numbers, so a mismatch between practice server and tournament server surfaces. Third, keeping contracts and transfers transparent, so smaller teams' voices are not lost to bigger teams' bargaining.

My own experience says, the stopwatch is a witness, not a verdict. It measures time, but it never says why this time. Blockchain is the same—it preserves evidence, it does not explain. The analyst must explain, but now holds evidence they can present without doubt. Had the empty spreadsheet I began with been stored on a chain, we would at least know which column was emptied, when, and by whom.

In Bangladesh this discussion is not theoretical. Here many teams keep practice records on paper, many tournament results live only in Facebook posts, and many player contracts are verbal. In this situation an analyst must verify every number before trusting it—how new it is, its source, and who benefits. When I write a transfer fee or a head-to-head record, I make its source and timing clear, because a sourceless number turns analysis into decoration, not argument.

One caution must be added. With a small sample, a clean causal chain appears that is actually coincidence. Two or three matches cannot prove a strategy works. So I set a minimum sample threshold, write alternative explanations, and do not hide limitations. Blockchain raises the integrity of data, not its volume—a small sample stays small.

Takeaway: the language of the game and the language of data are not the same

Returning to esports from international Olympic coverage, I understood one thing. In track and field, time is a neutral language—everyone measures in the same second. In esports that neutrality does not yet exist, because every patch, every server, every version makes a number relative. An analyst who forgets this difference sits a track split table inside esports and gets confused.

In the next two years, I hope major tournament organisers make verifiable records mandatory for match data, and smaller teams make practice-log preservation routine. The day that empty column in a Sylhet scrim room stays empty no longer, esports analysis will plant a full foot from emotion into argument. The game always tells a story; the analyst's job is to verify whether the story is true.