A $100 million raise closed last month. The technical due diligence memo that cleared it ran forty pages. Thirty-one of its risk fields were marked "N/A."
I read it twice. Not because it was dense โ because it was hollow. Same structure, page after page: technical maturity, N/A. Supply schedule, N/A. Jurisdictional exposure, N/A. Treasury controls, N/A. No fabrication. No concealment. A template, an auditor, a signature block, and zero information.
The book priced the raise as a positive. That is the systematic error, and it is worth auditing properly, because the same empty scaffolding shows up in nearly every diligence packet that crosses my desk this cycle.
The template became the product
Diligence frameworks were built for a specific asset class: companies with revenue, employees, and a legal domicile. Crypto protocols are not that. So the industry did what it always does when a category does not fit a form โ it kept the form and let the fields rot.
The mechanics are simple. A fund receives a memo. The memo has a fixed schema. An analyst is paid to populate the schema. When the source material is genuinely absent โ the code is unaudited, the token has no vesting contract deployed, the entity has no registration โ the analyst has two options. Write "not determinable" thirty-one times and look incompetent, or write "N/A" thirty-one times and look thorough.
N/A reads like a boundary condition. It reads like the field does not apply. It does not read like an unanswered question. That is a formatting decision with seven figures of consequence attached to it.
The vacancy premium is the most mispriced instrument in this market. An unfilled diligence field is not neutral. It is a free option written by the reader to the issuer. The reader absorbs all downside; the issuer collects the premium in the form of a cleared round.
What an empty field actually tells you
Consider the ledger. When a counterparty hands you a schedule with blanks in it, you do not assume the blanks are zero. You assume the counterparty has not decided what the number should be โ or has decided, and prefers you not to know.
Ledger books, not feelings, settle the debt. So audit the blank rather than react to it.
Three diagnostics separate an honest gap from a manufactured one.
Cluster location. Genuine gaps scatter. A seed-stage protocol may legitimately have no revenue, no token, no jurisdictional footprint โ those absences are consistent with youth. But a protocol that has shipped a mainnet, raised a Series A, and launched a governance token has no excuse for an empty supply schedule. Gaps that cluster in exactly one dimension โ usually the one that would kill the round โ are not youth. They are selection.
Fill rate over time. In the memos my desk reviewed across the last eighteen months, the same projects reappear with the same blanks. A field empty in Q1 and empty in Q3 is not awaiting information. It is a permanent feature of the disclosure posture. Permanence is the tell.
Asymmetry of the blank. Ask who benefits if the field stays empty. If the answer is the issuer, the field stays empty. If the answer is the buyer, the field gets filled within a week.
Audit the code, then audit the intent
I learned this in 2018, auditing fifteen early ERC20 contracts ahead of a testnet migration. One of them โ confident whitepaper, confident founder โ carried a standard integer overflow in the transfer path. The exploit was not subtle. It was a missing SafeMath in a function every user touched.
The team had roughly $40,000 of exposure. I filed the report. The founders rejected it as "too aggressive." I published it on GitHub instead; three security researchers cited it within the month.
The lesson was not that founders lie. The lesson was that a document's confidence tells you nothing about its contents. The whitepaper was well written. The bytecode was broken. Only one of those artifacts is load-bearing.
So when I open a memo and find thirty-one blanks, I do not ask whether the team is honest. I ask something narrower: what did the analyst verify against a primary source? Not interview notes. Not a founder's Telegram message. Not a deck. Verified artifacts โ deployed bytecode, on-chain supply contracts, signed legal opinions, executed audits with reproducible findings.
Most memos carry a verification column. Most verification columns contain assertions dressed as citations.
The routing problem nobody wants to fill in
Here is where the blanks get expensive, and where this cycle has a structural blind spot.
Suppose the memo's settlement assumptions are marked N/A. In practice that means the protocol has not specified how value moves between its execution environment and everywhere else it claims to integrate. That is not a documentation gap. That is the product.
Every new interoperability route fragments the book. Liquidity does not aggregate across bridges; it splits, gets re-quoted, and re-priced by a different market maker carrying different inventory. Ten bridges do not give you ten times the depth. They give you ten shallow venues and one arbitrage bot harvesting the spread between them.
I have watched this at the routing layer for years. The Lightning Network remains the cleanest example precisely because the problem was never solved. Capacity is public, but the useful metric โ the probability that a payment of size X finds a path at time T โ is published nowhere, because publishing it would require admitting how often it fails. Channel management overhead is a full-time operational cost. Routing success degrades exactly when you need it, during congestion.
A field marked N/A on payment reliability is not a missing data point. It is the answer, written in the only format the issuer could tolerate.
The same logic governs settlement layers. The OP Stack versus ZK Stack debate gets framed as a proving-system argument. It is not. The measurable difference is distribution: which stack convinces more teams to deploy a chain first, and inherits their liquidity, their sequencer revenue, and their failure modes. A project with an empty technical spec sheet can still win that race, because the race is not technical. That should make you uncomfortable. It should also tell you what to underwrite.
The options desk view
At the desk, we strip noise. My current reporting template for institutional clients carries two columns: Vega and Theta. Directional commentary is removed, because directional commentary is a story, and a story cannot be hedged.
Apply the same discipline to diligence. What is the implied volatility on an ambiguity?
An N/A field has no realized value. It has only an implied distribution โ and that distribution is wide, because the issuer controls when, or whether, it resolves. Concretely: a blank supply schedule means the reader is short a call on dilution with an unlimited strike range. A blank treasury-control field means the reader is short a call on governance capture. These are not metaphors. They are exposures, and they can be priced.
Rough framing from my own book: a memo with a high fill rate supports a tighter expected-value band because the tail scenarios are bounded. A memo with high blank density widens that band asymmetrically โ the downside tail is long, the upside is capped by the raise price. You are not buying a lottery ticket. You are selling one.
The hedge is not "don't invest." The hedge is position sizing that treats the blank as an unknown rather than a zero. If the supply schedule is N/A, underwrite as though fully diluted valuation equals current valuation. If treasury controls are N/A, underwrite as though no timelock exists. Assume the worst case is live, then decide whether the trade still clears.
The contrarian read
The obvious take is that empty memos signal fraud. That take is wrong often enough to be dangerous.
There is a real category of asset genuinely younger than its template. A three-person team with an unaudited proof-of-concept and no token has nothing to put in a supply schedule. Forcing it to answer a Series C checklist manufactures a false negative, and false negatives carry a cost: you pass on the thing that later shows no blanks because it never had a form to fill.
The distinction that matters is not presence versus absence of information. It is consistency of disclosure relative to stage. A pre-token protocol with fourteen blanks can be honest. A post-token protocol with fourteen blanks cannot be, because the token exists โ the supply schedule is a deployed contract that anyone can read in a block explorer in ninety seconds.
The blank is never the crime. The blank where the artifact is public is the crime.
Liquidity dries up when confidence breaks. Confidence breaks the moment a field that should have been filled is found empty. That is the re-rating event to track โ not the raise announcement, but the instant a previously empty field gets an answer, and the answer is not what the round was priced on.
What to watch
Watch fill rates, not narratives. Track which diligence fields flip from N/A to a number, and how long that took. Watch for blanks that cluster in settlement, supply, and control โ the three that determine what you actually own. And watch the projects that publish the ugly fields voluntarily.
The question is not whether a protocol will eventually disclose its routing assumptions. The question is whether you will still be holding the position when it does.