Last Tuesday, a colleague forwarded me a research packet on a project that had just closed a $100 million round. Nine analytical dimensions. Forty-one fields. Technical architecture, token supply structure, unlock schedules, team verification, Howey exposure, on-chain activity, competitive landscape.
Every field read N/A.
Not because the analyst was lazy. Because the analyst was honest. There was no architecture document. No audit. No allocation table. No named team. The packet was a meticulously formatted void β and it was, without competition, the most truthful thing I have read in six months of a bull market.
I sat with it for a long time. We are told that the job of a crypto analyst is to manufacture conviction. But what if the job, at least sometimes, is to manufacture the absence of it?
That page of N/A told me more than any forty-slide deck I have opened this year. It told me precisely where the information stopped. And in a market where everyone is being paid to keep talking, knowing where the sentence ends is a form of alpha.
Bull markets don't produce more information. They produce more formatting.
I have watched this happen from the inside. In 2024, I ran a project called Ethical Bridge out of a Layer-2 team here in Seattle β a glossary and value-mapping exercise designed to translate rollup validity proofs into something a regional bank's risk committee could actually sign. Fifteen institutional partners. Two million dollars in pilot funding. The whole point of that work was to compress complexity into a shape a compliance officer could hold in one hand.
It worked. And I have been slightly suspicious of my own craft ever since. Because the same technique that makes a good idea legible to a risk committee also makes an empty idea legible to a risk committee. Compression does not discriminate. A template is morally neutral. It will happily describe a zkEVM with a real proof system, and it will happily describe a Telegram channel with a whitepaper and a market maker.
That is the mechanism behind what I've started calling narrative laundering: taking a project with no verifiable substance, running it through a professional-looking analytical frame, and emerging with something that reads like due diligence. The output has the texture of rigor. It has none of the content.
The N/A page was the antidote. It refused to launder.
Here is the technical point most people miss. N/A is not a neutral value. In risk analysis, absence of data is not absence of risk β it is the opposite. When a field cannot be filled, the correct prior is not "unknown, therefore neutral." It is "unknown, therefore assume the worst until proven otherwise." That isn't cynicism. It's the standard treatment of information asymmetry, the same reason an auditor flags an unexplained journal entry instead of shrugging at it.
I learned this the expensive way. In the DeFi summer of 2020 I forked three yield strategies across Uniswap and SushiSwap, treating five thousand dollars of savings as a laboratory. I was fast, and I was loud on Twitter about governance theater. What I did not do β what I could not be bothered to do β was trace where the yield actually came from. Fee revenue? Emission subsidy? I never asked. Forty percent of my capital evaporated into impermanent loss and token inflation, and the lesson wasn't "don't farm." The lesson was that a yield number without a provenance is not data. It's a mood.
Every APR is a claim. The only question worth asking is: paid by whom, from what?
The same discipline applies to the architecture claims that dominate this cycle. I've spent the last year watching Layer-2 teams argue OP Stack versus ZK Stack as if it were a cryptography debate. It isn't. The technical differences are real but converging. What actually decides the outcome is which team can convince more projects to deploy a chain first. Distribution, not proofs. Yet the marketing materials all describe a technical race, because a technical race is legible and a distribution race is not.
And I've watched a wave of "Bitcoin Layer 2s" launch with EVM-compatible bridges, Ethereum-style token standards, and almost no relationship to Bitcoin's actual trust model. The Bitcoin community notices. The template does not.
I keep coming back to a claim I make often and can defend only partially: that orderbook DEXs will never beat centralized exchanges, because no market maker will leave a resting quote on-chain where it can be picked off. That's a latency argument, and latency arguments are unfalsifiable in the abstract. So I did the boring thing and looked at where the quotes actually sit during volatile hours. They thin out. They don't vanish. The honest version of my position is narrower than the slogan β and narrower is the entire point. A claim you can narrow is a claim backed by data. A claim that only gets louder is a claim backed by a template.
Notice the pattern. In every case, the gap between the label and the mechanism is exactly where the N/A lives. Fill that gap with data and you have a thesis. Fill it with adjectives and you have a position.
Now the part I have to be honest about, because a contrarian who only points outward is just a critic.
There is a failure mode on my side of this argument too. Demanding completeness can become its own kind of cowardice. If I insist on a fully disclosed allocation table, a named team, three audits and twelve months of on-chain history before forming any view, I will never form a view on anything early. Early is, by definition, the state in which the information does not yet exist. If I wait for the N/A fields to fill, I am not being rigorous. I am being late.
I sat with that tension for six months in 2022, alone in a Seattle apartment, reading zero-knowledge papers and drafting a manifesto about privacy because the market had taken everything else away. What that silence taught me is that the discipline is not "refuse to act without data." The discipline is knowing which missing field is fatal and which is merely early.
A missing audit on a protocol holding nine figures of TVL is fatal. A missing audit on a testnet is just Tuesday. A missing team identity on an infrastructure project courting institutional custody is fatal. A pseudonymous team shipping open-source code anyone can verify is a different risk entirely β sometimes a lower one. The skill is triage, not paralysis.
And here is the sharpest version of the contrarian point: sometimes the information vacuum is manufactured on purpose. A project that raises nine figures without publishing an allocation table has made a decision. It has decided opacity is worth more to it than credibility. That is information. It may be the only real data point in the packet.
The uncomfortable corollary is that a large share of this cycle's growth has gone to teams that learned to fill templates faster than they learned to fill fields. I don't say that as a moral judgment. I say it as a structural observation about incentives: in a bull market, the marginal return to better formatting exceeds the marginal return to better engineering β until it doesn't. That inversion is temporary. It is always temporary. The bill arrives as an exploit, an unlock nobody modeled, or a governance vote that reveals who actually holds the keys.
Which brings me back to that page of N/A, and to why it matters beyond one project.
The industry has spent a decade arguing that decentralization is a property β something you achieve, certify, then possess. I've never believed that. Decentralization is a verb, not a noun. It is the continuous practice of making information available to people who have no obligation to trust you. A protocol that publishes its allocation schedule, names its sequencer operators, and documents its upgrade keys is decentralizing. A protocol that does none of that is not "early." It is centralizing, quietly, and using the analytical apparatus of the industry as cover.
Institutions understand this instinctively, which is why the Ethical Bridge conversations went the way they did. The bank did not care about the elegance of the proof system. It cared whether it could explain the trust assumptions to a regulator in one paragraph. That is the N/A question asked in a different dialect: what do you actually know, and what are you hoping?
So here is what I want to leave you with, in the middle of a market that rewards confidence and punishes hesitation.
The next time someone hands you a forty-page report on a nine-figure valuation, count the N/A fields. Not the ones filled with estimates β the ones left blank. Those blanks are the actual map. They tell you where the diligence would have to happen, and whether anyone has bothered.
The most valuable line in crypto research is not a price target. It's an honest "we don't know yet."
The question is whether you're disciplined enough to write it down before the round closes β or whether you'll let the template write something more comfortable in its place.