We didn't read the whitepaper. We skimmed it — 47 pages, glossy diagrams, three buzzwords per paragraph, and not a single line of pseudocode. By page six, I was already on Twitter arguing with strangers about whether this project would flip Ethereum. By page twelve, my feed was full of people who'd "done their research" by watching a single three-minute YouTube summary. The project raised $80 million within forty-eight hours. I lost $4,200 riding the wave. I learned something else instead.
The empty document in front of me wasn't an oversight. It was the product.
This is the bull market disease. Not the obvious kind — the rug pulls and the obvious scams have decent counter-defenses now. The dangerous kind is subtler: protocols that raise nine figures on narratives so thin you could read through them, governance proposals that pass because nobody bothers to read the diff, audit reports that ship without verifying the commit hash. The information asymmetry has always existed in crypto. What changed in this cycle is that both sides have stopped pretending to care.
I track roughly thirty DeFi protocols as part of my work — call it obsessive, call it professional self-harm. During the last bear market, I could spend two hours auditing a governance forum and find substantive technical objections on every major proposal. People cited EIPs by number. They pasted contract addresses into Etherscan and argued about storage slot collisions. Last week, I reviewed a $200 million treasury proposal where the top reply was a single emoji. The proposal passed with 94% approval.
The empty narrative doesn't announce itself. It looks like every other announcement — clean graphic, founder thread, a "Why We're Building" substack. The only difference is the ratio of adjectives to specifications. In 2021, that ratio was maybe 3:1. In this cycle, I've seen pitch decks where it climbs past 12:1. The document is optimized not to inform, but to signal the appearance of having informed.
Here's what an empty narrative actually looks like when you audit it — Root: The first tell is the absence of specificity. Real protocols have opinions about state expiry. Empty ones have opinions about "Web3 vision." Real teams will argue about the gas cost of a Merkle proof insertion versus a SNARK verification at a specific block depth. Empty teams will tell you their chain will "process millions of TPS" without naming the consensus mechanism, the data availability layer, or the sequencer topology.
I spent three hours last month reading the codebase of a "decentralized" sequencer that turned out to be a single AWS region with one admin key. The marketing site said "fully distributed sequencing infrastructure." The CONFIG file said "us-east-1." This is what I mean by the empty document being the product: the audience isn't buying technology, they're buying the feeling of having evaluated technology. The marketing machine is calibrated to produce that feeling efficiently.
The second tell is governance theater. Vote counts without quorum thresholds that match the actual stake distribution. "Community-led" treasuries where sixty percent of voting power sits in three multisigs the team controls. Proposals that pass because the token-weighted voting structure makes dissent economically irrational. I reviewed one protocol's snapshot space last quarter: twenty-two active voters across four proposals, controlling $140 million in treasury decisions. Twenty-two humans, $140 million, and a one-week voting window each. The decentralization narrative required no further elaboration.
The third tell — Root: The cleanest one — is when the team's "technical FAQ" answers no technical questions. You ask about validator slashing conditions. They tell you about the validator vision. You ask about MEV extraction paths. They tell you about MEV protection. I have a folder of fourteen FAQ documents where every technical question gets a sentence of jargon and three paragraphs of mission statement. The folder is named "Missionaries Without Math."
Here's where I have to push back on my own tribe. The crypto community has decided that empty narratives are a moral failing, and I'm not sure that's right. Some of the most consequential protocols in this space started with vague whitepapers. Ethereum's original yellow paper had gaps that took years to resolve. Bitcoin's whitepaper was four pages and answered maybe sixty percent of the questions its first critics asked. The empty narrative isn't always a red flag — sometimes it's a founding document.
The harder question is whether the bull market's tolerance for emptiness is actually allocating capital correctly. Maybe it is. Maybe the hundreds of millions flowing into protocols without substance represent efficient price discovery for the idea of the protocol, which is what gets refined later. Venture capital has always worked this way — most bets fail, a few pay out, the variance funds the next cycle. Crypto just turned the same mechanism into a public market, with all the retail pain that implies.
But here's where the contrarian breaks: public markets have disclosure requirements for a reason. When a VC firm writes a $5 million check into a vague whitepaper, that's a calculated risk by professionals with information asymmetries in their favor. When a retail investor puts $4,200 into the same thing because a Twitter thread told them to "ape in," that's something else. The bull market has blurred this line so thoroughly that even the professionals have started behaving like the retail. I watched two funds I respect allocate $20 million combined into a protocol last month because "the team is strong" — neither asked to read the codebase.
We didn't lose the technical culture of crypto to the bears. The bears were just the cover. We lost it the moment the empty document became more valuable than the full one — the moment the marketing machine outperformed the engineering machine in dollar terms. The question for this cycle isn't whether the narratives will get better. They won't. The question is whether the people who can still read code will still be here when the next bear market arrives and someone finally needs them.
So what do we do when the documents are empty? Not "should we do something" — the documents will keep being empty, the cycles will keep rewarding emptiness, and the empty narratives will keep raising. The question is what we owe each other in the meantime.
I keep one rule from 2017: read the actual diff before the proposal. Not the executive summary. Not the founder thread. The diff. If you can't read the diff, you don't have an opinion on the proposal. If you can't find the diff, that's the answer.
In a market that rewards the feeling of research over the practice of it, that single habit is starting to feel like an act of resistance. The question is whether it's enough.
