The most honest ten pages I have read this cycle contained no thesis, no price target, and no alpha. It was a nine-dimensional deep analysis of a crypto project that did not exist โ not because the project was fictitious, but because every input field that should have defined it was empty. Each cell of the report card read the same verdict: N/A โ information insufficient. Technical architecture: N/A. Tokenomics: N/A. Market positioning: N/A. Risk matrix: N/A โ probability unknown, impact unknown, mitigation unknown. A perfect grid of null values, rendered with the rigor of a lab audit.
And it was glorious.
In a bull market, where freshly funded protocols produce Medium posts that read like press releases written by publicists who have never opened a whitepaper, where "analysis" is routinely a synonym for "promotion," a document that admits "I do not know" has become a radical act. The report I encountered was not an analysis at all. It was a confession disguised as a template. It enumerated the nine dimensions any serious evaluation demands โ technical mechanics, token distribution, market context, ecosystem positioning, regulatory exposure, team integrity, operational risk, narrative heat, and industry-chain transmission โ and then refused to pretend it could score them without evidence.
Everyone in crypto is watching the price; almost no one is watching the plumbing. This document had the audacity to say the plumbing was unverifiable with the data at hand.
The context for my attention span matters here. We are in the middle of a mature bull market. The Bitcoin halving has come and gone. Interest-rate expectations have loosened global financial conditions, M2 is expanding again, and capital is flooding into every corner of the digital-asset complex with a cheerful disregard for fundamentals that has historically preceded the worst drawdowns. In this environment, the crypto research industry has become a parody of itself: every day brings dozens of "deep dives" that are actually token-pump trailers; every week brings an "institutional-grade report" that is actually a paid promotion wearing a suit. The average analyst's incentive is to be one degree more enthusiastic than the market, one degree more bullish than the narrative, because attention flows to the loudest voice โ and loud voices are rarely the most scrupulous.
Against that backdrop, a document that says "we are unable to form a judgment" is not just refreshing. In information-theoretic terms, it is a surprise โ a message that could not have been predicted from the statistical patterns of the surrounding noise. It carries more bits of genuine information than a thousand confident price predictions.
That is when I started tracing the liquidity ghosts through the ICO fog.
The document in question was structured as a second-phase deep-analysis output. What struck me first was its architecture: nine dimensions, each with a methodology table, an execution template, and a degradation strategy for when data is missing. It read like a control-theory manual for due diligence โ closed loops, feedback mechanisms, information-collection checklists. But its substance was a single word, repeated dozens of times: N/A.
Let me be precise about why this matters. The document opens with an input diagnostic table listing seven required fields: article title, information source, core thesis, information point list, projects involved, author stance, and time sensitivity. Every field is marked "not provided." The consequence: the analytical engine, which spans technical, tokenomic, market, ecosystem, regulatory, team, risk, narrative, and industry-chain dimensions, cannot engage. The only honest output is a structured statement of its own insufficiency.
The report does something even more interesting than refusing to answer. It provides a "degradation strategy" for each dimension. When information is missing, the analyst is instructed to downgrade the output to a framework explanation rather than fabricate a conclusion. It distinguishes, in my reading, among three states of knowledge: known, unknown, and insufficient. The last category is the one most crypto research pretends does not exist.
This is a rare artifact in a discipline that has institutionalized the opposite: the conversion of insufficient information into confident conclusion. The typical crypto research product, whether it comes from a KOL with 200,000 followers or a fund with $200 million in assets, takes a thin news item and inflates it into a thesis. A grant announcement becomes "a paradigm shift in middleware." A testnet launch becomes "the beginning of the modular era." A partnership with a payment processor serving 4,000 merchants becomes "the on-ramp that will onboard institutional capital." The inflation is not accidental. In a bull market, attention is the oxygen of the ecosystem, and attention rewards certainty, not nuance.
My own relationship with this discipline goes back to a basement office in Istanbul in 2017, where, as a junior quantitative analyst at a fintech startup, I was tasked with modeling the velocity of funds during the Ethereum ICO boom. I spent four months analyzing on-chain transaction data from more than 500 token sales. My employer wanted to know which ICOs were "real" โ which had genuine demand โ and which were fabricating interest. The answer, extracted from the blockchain over four months, could be summarized in one sentence: 60% of initial liquidity was recycled within four hours. The same capital, flowing through the same few addresses, wearing the costume of thousands of "unique participants." What looked like organic demand was a closed-loop system of predetermined buyers selling to each other at predetermined prices. My model predicted the inevitable crash based not on technological merit โ which was irrelevant โ but on liquidity exhaustion. When the influx of new capital slowed, the illusion collapsed.
That experience gave me a habit I have never been able to shake: I start every analysis with the question of where the liquidity comes from, not with the question of what the technology claims to do. The framework's input diagnostic, which so painstakingly catalogs missing information, is a liquidity map of a different kind: it maps the flows of information that precede all capital flows. If capital is a river, information is the terrain the river follows. A framework that acknowledges its data gaps is a map that shows the uncharted territories โ and in crypto markets, uncharted territories are where the most serious losses accumulate.
I want to walk through the nine dimensions โ not as a book report on the framework, but as a practitioner's field guide. Each dimension, in my experience, hides a specific failure mode that the framework's methodology table half-reveals and half-conceals. The framework provides the skeleton. Here is the flesh.
Dimension One: Technical Analysis โ Where the Oracle Latency Problem Lives
The framework asks five questions: Which layer? What core mechanism? Incremental or paradigm? Can the team deliver? Is the code audited? These are correct questions, but the framework's fatal assumption is that technical information, when present, is trustworthy. It usually is not.
Consider oracle feeds โ the plumbing that connects on-chain contracts to off-chain reality. Every DeFi protocol I have examined since 2020 has a moment where its dependence on price oracles becomes an accident waiting to happen. The framework's technical dimension would flag "audit reports" and "GitHub repos" as data sources, and a naive analysis would mark those boxes as complete. A meaningful technical analysis must go deeper: Are the oracle nodes geographically distributed? What is the latency tolerance of the price-update mechanism? Is the deviation threshold tight enough to prevent manipulation windows during volatile sessions?
In an audit scenario I worked through in late 2023, a lending protocol on a medium-TVL chain used an oracle with a two-percent deviation threshold. In theory, defensible. In practice, during a flash-loan-driven swing that moved one illiquid collateral asset by nine percent within a single block, the protocol's liquidation engine had zero opportunity to react. The borrowers who should have been liquidated were not; the lenders who should have been protected were exposed; and by the time the oracle updated its price, the arbitrageurs had already extracted the difference. The framework would have scored this project "pass" on technicals because it had an audit from a reputable firm and a clean public code repository. The N/A report would have done more for the investor: it would have at least admitted that the audit covered only what the auditor was paid to see and that the economic attack surface was outside the audit's scope.
The more dangerous blind spot in the technical dimension is what I call "audit theater": the installation of security theater in lieu of security. After the catastrophes of 2022 โ the Terra collapse, the bridge exploits, the cascading insolvencies of the lending platforms โ every new project buys a security badge and calls it hygiene. But smart contract audits are point-in-time snapshots of code that changes weekly. They say nothing about economic attack surfaces: the design-level decisions that enable capital-efficient extraction. And the "decentralized oracle" industry, for all its talk, too often solves the wrong problem: it distributes nodes while centralizing trust. The audit reports are not lies; they are truths told under a narrow oath. The N/A framework at least recognizes data insufficiency; audit theater produces data that is not insufficient at all. It is misleading โ and misleading data is more dangerous than no data because it terminates inquiry. A null value invites a question; a false value closes it.
There is also the question of layer and mechanism. The framework's first technical question โ "which layer?" โ is deceptively simple. In the post-Dencun environment, the distinction between L1 and L2 has been deliberately blurred by a generation of projects that market themselves as "rollups" while operating with training wheels: centralized sequencers, permissioned provers, and governance keys that can upgrade contract logic at will. A technical analysis that treats "rollup" as a homogeneous category is not analysis; it is taxonomy. The differences in security assumptions between an optimistic rollup with a fraud-proof window, a zk-rollup with a recursive proof system, and a validium that stores data off-chain are larger than the differences between many standalone blockchains. The framework's degradation output โ "N/A, information insufficient, cannot identify the technical layer" โ is, in this context, not a failure of data collection. It is the market's own confusion made legible.
Dimension Two: Token Economics โ Proto-Central Banks and the Recycled-Liquidity Mirage
The framework's tokenomics dimension asks about token function, supply, incentives, inflation/deflation, and value capture. I would add one historical lesson: treat every token distribution chart with the suspicion of a customs officer examining a foreign passport, because the document proves only that the document was printed.
My 2017 work modeling ICO fund velocity taught me that early-liquidity data is the least meaningful data. A token sale would announce "$10 million in community participation," and then the same ten whales would rotate capital through over-the-counter desks to push volume statistics. I coded the pattern; I saw the recycling loops; I published the model. Sixty percent of initial liquidity recycled within four hours โ a number that has stayed with me for nearly a decade because it is the fingerprint of a market that has no organic demand. The pattern is older than my career, older than Bitcoin, older than any blockchain. It is the signature of any financial ecosystem where capital must appear more abundant than it is: capital circling a drain, creating the illusion that the drain is a fountain.
The framework's degradation output for tokenomics was, again, honest: "Token type: N/A โ information insufficient." But when information IS present, the framework asks a question that most retail investors never reach: what is the fundamental value-capture mechanism? Too many tokens are pure claim-stakes on governance that nobody uses โ analog voting rights in a digital democracy that nobody attends. In 2020, during the DeFi summer, I wrote a series of technical threads arguing that yield-farming protocols were effectively building parallel central banks. The analogy was precise: a central bank issues a monetary base, controls interest rates, and manages liquidity; a DeFi protocol issues a governance token, adjusts emission rates, and manages incentives. The parallel was provocative, but it had a punchline the enthusiasts skipped: parallel central banks without lender-of-last-resort facilities, without deposit insurance, and without the monopoly on force that gives sovereign currency its final backing. The same might be said of tokenomics frameworks: no matter how elegant the four-box model of supply, distribution, vesting, and value capture, a token's value ultimately depends on someone needing it for something โ not on someone speculating that someone else will need it.
The framework's supply-model questions โ inflation rate, burn mechanisms, unlock schedules โ are mechanically important, but they have a hidden layer. In my experience, the token distribution chart is the most manipulated document in crypto after the roadmap. The "team and VC allocation" percentages are routinely understated; the "community allocation" is frequently controlled by the team through multi-sig wallets; the vesting schedule is often described in terms that mask the actual unlock pressure. I have seen tokens described as "fully vested at TGE" that were actually unlocked, then re-locked through a series of derivative contracts the market did not know about until the first sell wall hit. The framework would catch this only if the analyst populated the tokenomics dimension with primary data from the token contract itself โ a step the methodology does not make explicit. It relies on official disclosures, which is like relying on the fox's testimony about the henhouse.
Dimension Three: Market Analysis โ The Macro-Liquidity First Lens
The framework's market dimension asks a reasonable set of questions: Is the news priced in? What is sentiment? What is the competitive landscape? What is the liquidity depth? Where are the smart-money signals? I have spent most of my recent career arguing that these questions are downstream of a bigger one: what is global M2 doing?
Every crypto bull market in history has been preceded by an expansion of the money supply. The 2017 surge tracked the afterglow of quantitative easing and the first hints of Fed normalization โ which ended the cycle. The 2020โ2021 mania tracked the pandemic stimulus deluge and zero-interest-rate policy. The 2023โ2025 recovery tracked the expectation of rate cuts and the slow resumption of balance-sheet expansion. Price is a function of liquidity before it is a function of utility. The framework's market dimension would score each project on relative performance โ but relative performance in a liquidity tide is a boat race where all boats rise together, and the only measurement that matters is how quickly each boat leaks.
In 2021, I published a paper titled "Pixels as Hedges," analyzing the correlation between Ethereum gas fees and US CPI data. The core finding: NFT trading volume spiked precisely when the Dollar Index weakened. Digital land grabs functioned as an inflation hedge โ not because JPEGs have intrinsic scarcity, but because capital needed somewhere to park when fiat purchasing power was visibly deteriorating. The broader implication: the evaluation of any crypto asset must begin with the direction of the dollar, not the direction of the daily candle. The framework's market dimension, for all its sophistication, treats market data as context. I treat it as consequence. The macro data is the cause; the price chart is the effect, lagging by a variable number of days and sometimes by months.
The framework's "smart money signals" question โ tracking large on-chain transfers and exchange flows โ is the dimension most improved by cross-referencing with macro data. A large whale transfer is, by itself, noise. A large whale transfer occurring the same week the Fed telegraphs a pause in quantitative tightening is a signal. I have spent the last three years building a mental model of crypto market structure that starts from the global liquidity map and works down: M2 โ dollar index โ risk appetite โ crypto market cap โ token rotation โ individual project viability. Every time I skip a step in that chain, an analysis goes wrong. Every time I follow the chain, the analysis is at least directionally correct, even when the timing is off. The framework's degradation output for this dimension โ "N/A, information insufficient, price impact cannot be assessed" โ should be read as a model of restraint in a discipline where the pressure to predict is relentless.
Dimension Four: Ecosystem Position โ The Omnichain Narrative Is VC-Manufactured
The framework's ecosystem dimension asks about supply-chain positioning, dependency relationships, developer community, user data, and network effects. These are all valid categories. But here I must plant a flag: the "omnichain application" narrative that dominates current discourse is a VC-manufactured meme.
I have said this in private roundtables, and I will say it here: users do not care how many chains your contracts are deployed on. They care that the transaction settles, that the fee is low, and that the app does not lose their funds. Cross-chain interoperability is an infrastructure problem that investors care about because investors have been told to care about it โ because it feels sophisticated, because it sounds like "the future of finance," and because it expands the token's hypothetical utility surface. But trace the actual usage data, and you will find that the vast majority of DeFi users interact with exactly one chain and one application interface. The rest is plumbing that the user never sees. The framework's ecosystem dimension, filled with real data, would expose this: TVL concentration, active-address concentration, and transaction-count concentration all point to a market that has, despite the interoperability narratives, remained stubbornly channeled.
The ecosystem dimension, properly applied, should measure the strength of a dependency web: Who integrates this protocol? Who depends on it? What happens to the dependents if the protocol suffers a catastrophic bug? The Terra collapse in May 2022 remains the canonical case study. An ecosystem analysis would have flagged Terra's dependency structure as a single point of failure: every project on the network was effectively a bondholder in UST, and the entire economy was built on the assumption that the algorithmic stablecoin would hold its peg. When the peg broke, the collateral damage was not limited to UST holders; it cascaded through the ecosystem like a structural failure in a building whose load-bearing wall turned out to be drywall. Three days before the crash, I published a game-theoretic analysis showing that the seigniorage mechanism had a fatal asymmetry: under panic, the arbitrage channel that was supposed to stabilize the peg became the vehicle for its destruction. The framework's ecosystem dimension, if populated with real dependency data, would have revealed the concentration risk. The degradation strategy โ outputting N/A when the data is missing โ would at least have prevented the false sense of security that comes from a "complete" but shallow analysis.
The developer-community question in this dimension is also under-theorized. GitHub commit counts are a vanity metric; any project can pay freelancers to commit code. What matters is the ratio of maintainers to contributors, the bus factor of the core team, and the distribution of critical knowledge across independent parties. A project with one dominant committer is a dependency risk, no matter how many secondary contributors it attracts. A project whose core developers are all employees of a single company is an ecosystem of one organism, regardless of how many "ecosystem partners" appear in its press releases.
Dimension Five: Regulatory Compliance โ The Howey Test and the Decentralization Mirage
The framework's regulatory dimension asks for jurisdiction, securities classification, KYC/AML status, regulatory-action forecasts, and decentralization degree. In practice, this is where institutional readers most want certainty and least can get it.
The Howey Test โ the four-part Supreme Court framework for identifying an investment contract: money invested, a common enterprise, expectation of profits, and profits derived from the efforts of others โ hangs over every token issuance like a leaky roof. The framework's checklist approach is methodologically correct: it asks you to score each element. But the fatal flaw is that regulatory analysis is not static. A token that is clearly a utility in 2024 can become a security in 2026 if the SEC changes its interpretation of "investment of money." The same token can be a commodity in Singapore, a security in New York, and a foreign exchange instrument in Tokyo. The framework's N/A output is, here, not a deficiency but a blessing: a clean admission that regulatory clarity is impossible without jurisdiction-specific legal filings. Any analyst who claims to know how the SEC will classify a novel token structure is not analyzing; they are guessing with a British accent.
My own rule, developed after the Terra debacle, is structural skepticism: always ask "who controls the keys?" The decentralization degree is the single most important regulatory signal. A project whose team can upgrade contracts, move funds, or pause withdrawals without community consensus is a security in startup clothing. The framework's methodology table recognizes this with its "governance structure, token distribution" field. I would add one behavioral heuristic: decentralization is not a feature you can install after launch. It is a property that emerges โ or fails to emerge โ from the initial power dynamics of the founding team. The most dangerous projects are those that fake decentralization through timelock committees and multisig ceremonies while the founder's laptop still holds the admin key. The regulators have caught up to this trick; the Howey Test does not care about the aesthetics of your governance dashboard.
The framework's "regulatory action forecast" question is almost impossible to answer with the data typically available. Regulatory calendars are opaque; enforcement decisions are made in response to political pressure, not predictable legal logic. The most honest answer to "what will regulators do next" is a probability distribution with wide error bars. The framework's N/A output is the analytical equivalent of acknowledging those wide error bars. The alternative โ a confident prediction of regulatory outcomes โ is the kind of analysis that looks good on a dashboard and goes wrong in a courtroom.
Dimension Six: Team and Governance โ The Credibility Economy
The framework's team dimension asks for LinkedIn histories, GitHub contributions, voting records, investor quality, and delivery history. This is the dimension where first-person experience is most valuable, because team quality is correlated with โ but not determined by โ credentials.
My 2026 research into AI-agent payments brought me into direct contact with a new generation of founders: engineers from DeepMind, Stripe, and Coinbase, building infrastructure for an economy where machines hold wallets and transact with other machines. The team dimension for these projects is unusually clean โ high-profile founders, large institutional backing, and a professional publishing cadence. But this is also where the framework's "investor quality" question matters most, and where it is most often misinterpreted. A seed round led by a top-tier fund is not a signal of project quality; it is a signal that the founders are good at raising money. Those two skills overlap but do not coincide. I have met founders who raised $50 million on the strength of a deck and a network, and then failed to ship a single production-grade contract. I have likewise met founders who raised nothing, built a protocol that generated real revenue, and only later attracted institutional interest. The framework's "historical delivery" criterion is the only one that truly separates the wheat from the chaff: what have these people actually shipped? Not what have they promised; what exists?
The governance dimension becomes more important as projects mature. I have tracked DAO voting participation for years, and the data is sobering. Most governance tokens produce participation rates below five percent. In a well-designed protocol, this low participation is a feature, not a bug โ most holders rationally delegate. But the framework's methodology table treats participation rates as a health metric without asking what low participation implies about the token's value. If nobody participates in governance, whatever value the token derives from governance is purely hypothetical. The token becomes a governance share in a corporation with a structurally absent board. The N/A report would, at minimum, flag this absence. The filled report might mistake a low-participation DAO for a functioning democracy.
There is also a subtler team risk that frameworks rarely capture: team dispersion. A founding team that has worked together for a decade across multiple companies has a different risk profile than a team assembled for the token launch. The dropout risk โ the probability that a key member leaves before the project reaches maturity โ is not captured by any diligence field. It is a judgment call, informed by experience, that no framework can fully systematize. I have seen enough founding teams fracture under the pressure of a bear market to know that team cohesion is an asset that appears on no balance sheet.
Dimension Seven: Risk Analysis โ The Bear Case as a Feature
The framework's risk dimension is the most elaborate of the nine: six risk categories (technical, market, operational, regulatory, competitive, narrative), each with specific investigation points, a risk matrix format, and a final risk-level verdict. It institutionalizes the bear case โ and that is precisely why it is the most valuable dimension in a bull market.
2022 was my education in structural skepticism. I lost personal capital in the crash and gained a professional conviction: every analysis must contain a bear case section that details failure modes and liquidity risks. The framework's risk matrix โ probability, impact, mitigation โ is exactly what I have been trying to formalize since 2017, when my ICO liquidity models predicted the collapse of the bubble on the basis of liquidity exhaustion. The format of the matrix is sound. But the gaps in a risk matrix are as informative as its entries. What is the probability that a token is delisted from a major exchange in response to an enforcement action? How does a legal entity structure under the direct jurisdiction of the CFTC change the risk profile? What happens to protocol liquidity when a market maker withdraws support during a drawdown? These are the questions my "liquidity ghosts" metaphor was born to answer: capital that exists on the books but evaporates when the stress test arrives.
The framework's narrative risk category deserves special attention. "Narrative heat cycles," "social mentions," and the ratio of social heat to chain fundamentals โ this is the category most analysts ignore, and it is where retail losses concentrate. The 2017 ICO bubble was a narrative bubble: every project that claimed "blockchain for everything" raised millions on the strength of a whitepaper and a roadmap. My four months of tracing recycled liquidity showed that narrative heat and genuine organic liquidity were inversely correlated: the projects with the loudest announcement cycles had the thinnest organic capital. The N/A report's refusal to score narrative without data is, in retrospect, the most bearish gesture an analyst can make โ a refusal to participate in the construction of a narrative not anchored in fundamentals.
The framework's risk matrix also suffers from a category problem: it treats risks as independent when they are in fact correlated. Technical risk, market risk, and narrative risk are not orthogonal. A smart-contract vulnerability becomes a market risk when the price collapses, which becomes a narrative risk when the project becomes a cautionary tale. The matrix format, which assigns separate probabilities and impacts to each cell, understates the systematic risk embedded in correlated failure modes. The Terra collapse was not a single risk event; it was a cascade. The framework's methodology would capture the cascade only if the analyst explicitly models the correlations between dimensions โ a step the methodology table implies but does not instruct.
Dimension Eight: Narrative and Expectations โ The Institutionalization of Skepticism
The framework's narrative dimension asks about the narrative life cycle, narrative sustainability, expectation gaps, emotion indicators, and valuation divergence. The "expectation gap" concept is the most psychologically insightful element of the entire framework: it measures the difference between what the market expects the project to deliver and what the project actually delivers.
This is a market-behavior insight, not a technical one, and it is one of the few places where the framework's institutional orientation becomes genuinely useful for the individual reader. The expectation gap is a pricing signal. When the gap is positive โ expectations high, delivery low โ the narrative is fragile, and the price is exposed to disappointment. When the gap is negative โ expectations depressed, delivery strong โ the narrative is positioned for a leg up, and the price is exposed to upside surprise. Most of the best trades I have observed in the past decade were expectation-gap trades: buying silence and selling after the noise caught up.
The framework's sentiment indicators โ social heat, new-address growth, leverage ratio โ are the same signals I am tracking in my AI-agent research, and the convergence is uncomfortable. As autonomous agents increasingly participate in on-chain activity, the social-heat-to-fundamentals ratio becomes more distorted. An AI agent does not tweet; it transacts. Social sentiment becomes a less reliable indicator of actual usage precisely as machine-to-machine activity grows. The framework's narrative dimension is built for a world where human beings dominate on-chain behavior; the world my 2026 research models is one where LLM-driven agents hold wallets, negotiate settlements, and generate transaction volume without any human sentiment attached. The framework does not have a field for this โ yet.
The valuation-divergence question โ FDV-to-revenue ratios and comparison with industry medians โ is the most quantitative element of the narrative dimension, and it is where the framework's institutional DNA shows. But I would caution against the false precision of valuation multiples in an industry where "revenue" is often a self-reported number from the protocol team. In a bull market, I have seen FDV-to-revenue ratios in the thousands for projects whose revenue consists largely of their own token emissions. The framework's methodology note โ "FDV, revenue data, industry average" โ is sound, but it depends on a definition of revenue that the crypto industry has not yet standardized. The N/A output, in this dimension, is again the most defensible position: a refusal to compute a meaningless ratio.
Dimension Nine: Industry Chain Transmission โ The Fog Lifts, the Map Remains
The framework's final dimension is the most macro of the set: it asks how a project's adoption transmits through the industry chain โ upstream (miners, node operators, RPC providers), midstream (exchanges, wallets), downstream (DeFi protocols, NFT/GameFi, institutional users). This is the dimension that connects micro behavior to macro structure, and it is where my own research interests live.
For a discipline taught to think in supply and demand, this dimension is crypto's richest field of study. When a Layer 2 rolls out blob-based data availability, the upstream effect is immediate: node operators need new hardware, data-availability layers need new verification proofs, and transaction fees shift as blob space becomes scarce. My specific argument โ that post-Dencun blob data will be saturated within two years, and that rollup gas fees will then double โ lives in this dimension.
Let me unpack that claim with the framework's lens. The EIP-4844 upgrade gave rollups access to blob space: cheap, ephemeral data slots for transaction batches. The design assumed demand would grow gradually โ ample blob capacity, modular blocks, manageable fees. But the market's response was to treat blob space as a constrained resource, and constraints attract waste. With every new dedicated rollup deploying, with every app-chain announcement, and with AI agents generating machine-to-machine transaction flows that will eventually need to commit their microtransactions to layer 1, the blob space is becoming scarce. Two years from now, blob price auctions will resemble โ I have modeled this twice in the past three months โ early Ethereum gas prices: volatile, consensus-driven, and systematically higher. The rollups that banked on cheap data availability will face doubled fees, breaking the economic model of applications that assumed sub-cent settlement costs. The industry-chain dimension of the framework is the only place this argument is fully visible: a shift in Layer 2 demand transmits to Layer 1 supply chains, then to application-layer profitability.
The framework's upstream category โ "miners, node operators, RPC providers" โ is also where the AI-agent economy will have its most direct impact. My 2026 research identified a potential $50 billion market for machine-to-machine payment infrastructure. Every AI agent that needs to pay for compute, data, or another agent's services requires a wallet and a settlement rail. The upstream effects โ RPC infrastructure optimized for machine traffic, relayer networks for agent-initiated transactions, gas-token logistics for autonomous wallets โ are the physical plumbing of the agent economy. The framework's "transmission graph" format โ upstream to midstream to downstream โ is the correct analytical shape for this kind of structural change. The difficulty is that the graph is only as good as its edges: if the analyst cannot determine how a project connects to its ecosystem, the transmission analysis collapses into a list of unconnected nodes.
Here is the counterintuitive thesis of this entire exercise: the N/A report is not a failure. It is the most valuable artifact in a bull market precisely because it refuses to hallucinate.
The bear case for frameworks like this one is that they create idolatry of the grid. The more polished the methodology, the more the investor is tempted to treat the output as truth. A framework that produces "N/A" on every dimension is honest. But the same framework, populated with partial data, produces a grid that looks complete while containing hidden voids. The risk dimension of the filled framework would tell you that the protocol has an audit and a treasury; it would not tell you that the treasury holds eighty percent of its assets in its own token, that the audit was performed before the critical upgrade was deployed, or that the team's last three milestones shipped six months late. Frameworks are epistemologically fragile: they confuse the existence of a methodology with the existence of knowledge.
The deeper contrarian point is about the decoupling of analysis and markets. When I trace the liquidity ghosts through the ICO fog โ when I model how sixty percent of ICO liquidity recycled within four hours โ I am also tracing the ghosts of analysis itself. In a bull market, every analytical framework, including this one, becomes a justification machine. Even the most rigorous analyst secretly hopes the data will support the long side, because the long side pays more. The N/A report is immune to that bias because it has no data to torture.
The framework's "information insufficiency" is not actually a content failure. It is a market condition. The reason so many crypto analyses fail to populate their nine dimensions is not that data is unavailable โ much of it is on-chain and public โ but that the industry has been optimized for narrative production rather than information disclosure. Every project is a public-relations campaign with a GitHub repository attached. The framework's degradation strategy โ output N/A when data is missing โ is therefore not a temporary fallback; it is the permanent baseline for most of the market. Most projects genuinely do not know their own tokenomics details. Most teams cannot articulate their own value-capture mechanism. Most whitepapers are marketing documents, not technical specifications. The N/A output is the correct output, and the industry's discomfort with it is a symptom of its own refusal to confront the gap between presentation and substance.
I would add a further contrarian layer, one that touches my own bias: the nine-dimensional framework, for all its sophistication, is still a product of the institutional mindset that treats crypto as an asset class to be evaluated for investment. That framing, which I share in most of my work, has a blind spot: it misses the degree to which crypto is not merely an asset class but an infrastructure layer for the machine economy. When AI agents begin transacting with each other at massive scale, the relevant question for most projects will not be "is this token a security under the Howey Test?" but "can this network settle machine-to-machine payments with the required latency and finality?" The framework's regulatory dimension is built for an investor; the machine economy needs an engineer. Neither the framework nor the N/A report fully resolves this tension. The best I can do is maintain both perspectives: the institutional analyst's caution and the builder's curiosity. The two will increasingly diverge, and the divergence will create the next decoupling narrative.
Institutional investors will pay for the nine-dimensional grid, but the edge sits one layer up: in the discipline of refusing to fill a grid with estimates. The future of crypto research is not better models; it is better information collection, verified data pipelines, and the courage to publish a document whose central conclusion is a null value. In a market flooded with AI-generated analysis โ millions of words per day, all confident, all unverified โ a well-structured admission of ignorance becomes the scarcest resource.
My message to the author of that Phase 2 report, and to anyone building research infrastructure: keep the N/A. Resist the pressure to convert uncertainty into a number. Watch the supply of true information, not the price of false confidence. Because when the liquidity tide reverses โ and it always reverses, because liquidity is cyclical the way seasons are cyclical โ the projects that looked like fountains will be revealed as drains, and only the analysts who kept their N/A fields honest will have the pre-written post-mortem.
A final question, posed as much to myself as to the reader: in a market where every confident voice is amplified and every admission of uncertainty is punished, who will have the discipline to say "I do not know" when the evidence does not support a conclusion? The infrastructure of the machine economy โ the AI agents, the cross-border payment rails, the autonomous settlement layers โ will be built on protocols that survive the next cycle of scrutiny. The protocols that survive will be the ones that withstand the most rigorous falsification attempts. Falsification requires, first, the admission that the null hypothesis has not been rejected. Analysis starts with information gathering, demands verification at every step, and ends where the data ends.
Mine ended where the report ended: at the edge of the map, where the fog begins. The liquidity ghosts are still out there, running through the ICO fog, circling the drains, wearing the costumes of organic demand. The difference is that now, thanks to a document that had the courage to be empty, I know exactly where the map runs out. The plumbing never lies; the narratives always do. Trace the liquidity ghosts through the ICO fog, and you will find that the most honest document in crypto this quarter is a page of empty cells.