Over the past seven days, I reviewed 23 project analysis reports published across major crypto research platforms. Sixteen of them followed the exact same nine-section template. Eleven had more fields marked N/A than filled with actual data. Three had entire sections copied verbatim from a different project's report, the template name accidentally left in the header. This is not analysis. This is cargo-cult diligence performed by people who have confused structure with understanding.
I have been building in this industry since 2017. I audited over 50 whitepapers during the ICO boom, co-founded a DAO education initiative during DeFi Summer, and spent the 2022 bear market holding community members together when the floor fell out. I say this not to flex credentials, but to establish a baseline: I know the difference between a framework used as a thinking tool and a framework used as a thinking substitute. Right now, the industry is drowning in the latter.
Let me walk you through what I found when I traced the origin of this specific nine-section template. It started as an internal checklist used by a boutique crypto fund in early 2023. A junior analyst shared it on a Discord server for research writers. It spread like a memetic virus. By mid-2024, it had been forked, adapted, and rebranded by at least seven different research platforms. By 2026, it has become the de facto standard for how projects are analyzed in bear market conditions. The problem is not the template itself. The template is actually quite good as a starting point. The problem is that people have stopped doing the work the template was designed to scaffold.
People first, protocol second. Always. This principle applies not just to governance design, but to how we produce knowledge about crypto projects. When I see a report with N/A in the security assumptions field, what I am really seeing is a person who did not bother to read the smart contract, check the audit reports, or run a simple trust-minimization analysis. When I see N/A in the incentive sustainability section, I am seeing someone who did not calculate the ratio of real yield to inflationary emissions. The N/A is not a data gap. It is a confession.
Based on my audit experience from the 2017 ICO era, I can tell you that the most dangerous projects were never the ones with obviously bad tokenomics. They were the ones where analysts filled in plausible-sounding numbers without actually verifying the claims. A template with fake data is worse than a template with N/A, because the N/A at least signals intellectual honesty. The fake data signals either incompetence or deliberate deception, and in this industry, I have learned to assume the latter until proven otherwise.
Let me drill into the specific failure modes I have identified across the nine dimensions of this template, based on my five years of governance architecture work and the 50-page Institutional-Community Interface Protocol I co-authored in 2024.
Technology Analysis. The template asks for innovation assessment, maturity stage, security assumptions, and performance metrics. These are not independent variables. A project that claims high innovation with unproven maturity is a research project, not a production system. A project that lists N/A for security assumptions is either hiding a centralized sequencer or has not thought about trust minimization at all. In my work auditing Layer 2 solutions, I have found that the single most revealing question is not about TPS or finality time. It is: who can halt the system? If the answer is a multi-sig of three people, everything else is marketing. I have seen projects with 10,000 TPS benchmark numbers collapse because the sequencer was a single AWS instance in us-east-1. The technology section is not about specs. It is about finding the hidden points of failure.
Tokenomics Analysis. The template divides supply into team, investors, community, and treasury. This is useful, but it misses the most important dynamic: the relationship between token distribution and governance power. I have analyzed over 30 DAO treasuries since 2020. The projects that fail are almost never the ones with bad tokenomics on paper. They are the ones where the tokenomics create perverse incentives. A vesting schedule that unlocks 80% of tokens to investors in year one while the community gets 20% over four years is not a distribution model. It is a liquidation schedule disguised as a token economy. The template needs to ask not just what the percentages are, but who controls the governance when those percentages shift. Trust is earned in bear markets. Tokenomics is tested when prices drop and unlocks accelerate.
Market Analysis. The current bear market has exposed the hollowness of most market analysis sections. I have seen reports that list TVL without noting that 70% of that TVL is the project's own token paired with a stablecoin in a liquidity pool that the team controls. I have seen price impact assessments that treat every announcement as bullish without checking whether the market has already priced in the expectation. In the 2022 bear market, I learned that the most valuable market analysis is not about predicting price direction. It is about identifying which projects have enough runway to survive 18 more months of declining revenues. The template asks for market sentiment and funding rates. It should also ask: how many months of operations does the treasury cover at current burn rates? That single number has predicted more project failures than any technical analysis indicator.
Ecosystem Analysis. This is where the N/A problem becomes most visible. A project's ecosystem position cannot be assessed by looking at the project alone. It requires mapping dependencies, identifying moats, and understanding switching costs. In 2024, when I was drafting the governance blueprint for institutional-community integration, I spent two weeks just mapping the dependency graph of the protocols involved. The template asks for developer signals and user signals. These are lagging indicators. The leading indicators are: how hard would it be for a user to leave? How much value is locked in composability relationships? What happens if the upstream infrastructure changes its fee model? If these questions are N/A, the ecosystem analysis is incomplete.
Regulatory Analysis. The Howey test analysis is a good starting point, but it is increasingly insufficient. We are in 2026. The regulatory landscape has shifted dramatically since the ETF approvals in 2024. The question is no longer just whether a token is a security. The question is: which jurisdiction's securities laws apply, and does the project have the operational capacity to comply with all of them? I have seen projects that passed the Howey test with flying colors but were effectively illegal in three major markets because of licensing requirements for the underlying business model. The template needs to add a dimension for operational compliance, not just token classification.
Team and Governance Analysis. This section is where my personal experience intersects most directly with the template's limitations. I have spent years designing and evaluating DAO governance structures. The template asks about team background, voting participation, and investor quality. These are surface-level metrics. The real questions are: who holds the multi-sig keys? What is the upgrade mechanism for the core smart contracts? Can the community override a team decision? I have seen projects with world-class team bios and 90% voting participation that were effectively controlled by a single person through a proxy governance mechanism. The template should include a governance centralization index that goes beyond token distribution to cover administrative control points.
Risk Analysis. The risk matrix in the template covers technology, market, operations, regulation, competition, and narrative risk. This is comprehensive, but the N/A entries reveal a deeper problem: analysts are not doing the cross-correlation work. The biggest risks in crypto are not single-point failures. They are cascading failures. A regulatory action in one jurisdiction triggers a stablecoin depeg, which triggers a liquidation cascade in a lending protocol, which forces a project to sell its treasury holdings at a loss. The template treats risks as independent categories. They are not. The most valuable risk analysis I have ever done was a correlation matrix of risk factors across all nine dimensions.
Narrative Analysis. This section is the most subjective and the most important in a bear market. The template asks about narrative sustainability and expectation gaps. The truth is that narratives in crypto have a half-life of about three months in a bull market and six months in a bear market. The projects that survive are the ones whose narratives are grounded in measurable progress. When I co-founded GoverningDAO in 2020, the narrative was about financial sovereignty. We backed it up with 12 workshops and 1,500 onboarded users. The narrative held because it was tethered to real outcomes. In the 2026 bear market, I am seeing narratives that are built entirely on future promises with no current delivery. The template should require at least one verifiable metric per narrative claim.
Industry Chain Analysis. This is the newest section and the least developed in most template-based reports. It attempts to map upstream and downstream impacts across the crypto ecosystem. The N/A entries here are particularly dangerous because they indicate that analysts are not considering second-order effects. A change in Bitcoin mining economics affects Layer 2 security budgets, which affects DeFi composability, which affects NFT floor prices, which affects GameFi tokenomics. The template needs to include at least one explicit second-order effect analysis per section.
Empathy is the ultimate security layer. I have been saying this since 2022, and I mean it literally in the context of analysis. When you read a report filled with N/A entries, what you are reading is a failure of empathy. The analyst did not empathize with the user who needs to know if their funds are safe. They did not empathize with the developer who needs to understand the technical risks. They did not empathize with the investor who is trying to make a rational decision in an irrational market. They filled in a template and moved on.
The contrarian angle that few want to admit: templates are making crypto analysis worse, not better. They create an illusion of rigor that substitutes for actual thinking. I have seen fund managers make multi-million dollar decisions based on reports that were essentially Mad Libs with crypto terminology. The template is not the solution. The template is the problem when it replaces judgment.
What should we do instead? I have three proposals based on my experience building governance systems that actually work.
First, every analysis report should start with a single sentence that captures the project's core thesis in plain English. If you cannot explain what a project does in one sentence that a non-technical person can understand, you do not understand the project well enough to analyze it. The template comes after the thesis, not before it.
Second, every N/A entry should be treated as a red flag, not a neutral placeholder. If an analyst cannot assess a dimension, that should trigger a warning, not a pass. The template should have a mandatory explanation field for every N/A: why is this information unavailable, and what would it take to fill the gap?
Third, analysis should be opinionated. The template format encourages false neutrality. It presents all dimensions as equally important and all findings as equally valid. Real analysis requires weighting. In a bear market, liquidity analysis matters more than narrative analysis. In a bull market, security analysis matters more than tokenomics. The template should include a weighting mechanism that adjusts to market conditions.
The future of crypto analysis is not better templates. It is better analysts who use templates as tools rather than crutches. The Conscious Code manifesto I initiated in 2026 was about AI alignment in decentralized systems, but its core lesson applies here: we cannot automate judgment. We can only scaffold it. The template is the scaffold. The analysis is the building. Too many people are mistaking the scaffold for the building itself.
I look back at the 50 whitepapers I audited in 2017. I did not use a template. I read each one cover to cover, built a mental model of the system, and then tested that model against edge cases. I made mistakes. I missed things. But I never once wrote N/A and called it a day. The projects that failed were not the ones I analyzed poorly. They were the ones I did not analyze at all because the whitepaper was too thin to engage with.
We are in a bear market. Survival matters more than gains. The protocols that will survive are the ones that pass the scrutiny of analysts who do the work. The templates will not save us. The frameworks will not save us. Only honest, rigorous, empathetic analysis will save us.
People first, protocol second. Always.
Trust is earned in bear markets. It starts with the courage to admit what we do not know, and the discipline to find out.