I spent an hour reading a so-called “comprehensive analysis” of a crypto project last week. It had nine sections, fifty sub-sections, and a risk matrix with color-coded boxes. Every field was marked “N/A – information insufficient.” The author had spent zero minutes on the chain. Zero conversations with the team. Zero code reviews. They had built a cathedral of structure on a foundation of nothing. And someone paid for that report.
We didn’t used to do this. We used to dig. We used to open Etherscan at 2 AM because we wanted to know where the liquidity really came from. Now we have frameworks. We have templates. We have AI-generated summaries that spit out “bullish” or “bearish” without ever touching the data. The market is in a bear phase, and the last thing we need is more noise dressed up as rigor.
I’m David Jackson. I run a crypto education platform in Stockholm. I’ve been in this space since 2017, when the ICO frenzy taught me one thing: the people who win are the ones who actually read the smart contract. Not the whitepaper. Not the Medium post. The actual code. And then they ask the hard questions: Who controls the upgrade key? What happens if the sequencer goes down? Where does the fee revenue go?
Today, I want to show you how to cut through the empty frameworks. I’ll use three real-world examples from my own work—DeFi Summer 2020, the Ordinals narrative on Bitcoin, and the current ZK rollup bleed—to demonstrate what actually matters. By the end, you’ll have a mental model that’s lighter, faster, and infinitely more honest than the 50-page reports that flood your inbox.
Trust is no longer a promise; it’s a protocol.
Let’s start with the biggest lie in crypto analysis: the “comprehensive” framework. Every VC, every research firm, every newsletter has a proprietary scoring system. They weigh technical innovation, tokenomics, team background, market fit, regulatory risk. They assign scores. They produce charts. And they are almost always useless—because they treat all projects as equal, as if a DeFi lending protocol and a Layer 2 scaling solution can be compared on the same spreadsheet.
In 2020, during DeFi Summer, I organized a meetup series in Stockholm called “Yield & Connect.” We had 300 attendees each session. The hottest topic wasn’t yield farming—it was trust. People had lost money in the 2018 bear market. They were skeptical of new protocols. I remember one attendee, a former banker, asking me: “How do you know Compound isn’t a scam?” I didn’t hand him a framework. I opened Etherscan, showed him the contract, and said: “Look at the total supply. Look at the team’s unlocked tokens. The code is law. You can verify it yourself.”
That moment changed how I write. I stopped preaching and started showing. Every article I’ve written since has one rule: the core insight must be something you can verify on-chain or in a GitHub repo. Not a narrative. A number.
Take the Ordinals narrative on Bitcoin. In 2023, when inscriptions first appeared, the mainstream Bitcoin community called it spam. “Block space is sacred,” they said. But I looked at the fee revenue. Before Ordinals, Bitcoin’s security model relied entirely on block subsidies. As the block reward halves, the network becomes less secure unless transaction fees rise. Ordinals injected a new fee market. In 2024, inscription fees accounted for over 30% of miner revenue at peak. Without that, Bitcoin’s security budget would be in trouble by the next halving. That’s not an opinion. That’s a math problem.
Now, the same people who dismissed Ordinals are building on Bitcoin again. The pivot was painful, but it taught me that narratives follow data, not the other way around.
The real analysis is on-chain.
Let me give you a concrete method. When I evaluate a DeFi protocol, I start with three numbers: total value locked (TVL), daily active users (DAU), and fee revenue. Not the token price. Not the market cap. The usage. If a protocol has $1B TVL but only 500 DAU, something is wrong. It’s probably a whale farm or a sybil attack. If the fee revenue is less than 10% of the token emissions, the protocol is burning cash and will eventually die.
In 2022, I watched a friend’s project collapse. They had a beautiful framework, a great team, and a $50M valuation. But their TVL was 90% from a single whale who was yield farming with borrowed money. When the whale withdrew, the project died in 48 hours. The framework didn’t catch that. The chain did.
Today, I want to apply this to the current Layer 2 landscape. Everyone is bullish on ZK rollups. They promise instant finality, lower fees, and Ethereum-level security. But the numbers tell a different story. In 2025, the average ZK proving cost per transaction is around $0.02 on Ethereum mainnet, and that’s with generous gas prices. In a bear market, where gas is under 10 gwei, the actual cost to generate a proof often exceeds the gas saved. Operators are bleeding money. The only way they survive is if Ethereum gas returns to bull-market levels. If it doesn’t, we’ll see a wave of ZK rollups either shutting down or centralizing their proving to cut costs.
I’ve been auditing ZK circuits since 2023. I can tell you: the technology is amazing. But the economics don’t work yet. The “fragmentation of liquidity” that VCs keep talking about is a manufactured narrative to sell interoperability solutions. The real problem is that most rollups are unsustainable. The ones that survive will be the ones that optimize for cost, not hype.
Code is law, but empathy is the interface.
Now, the contrarian angle. I’ve been an evangelist for decentralization since 2017. I’ve written about trustless systems, about code as law, about the moral imperative of permissionless access. But I’ve also learned that the most successful projects are the ones that balance code with community. Trustless systems require trusting relationships. You can’t automate empathy.
In 2022, I burned out. I stepped back from technical analysis and spent three months traveling Europe, attending art installations, talking to people who had never heard of blockchain. I wrote a blog series called “Finding Humanity in the Void.” It got 10,000 reads. The feedback was overwhelming. People didn’t want more analysis. They wanted connection. They wanted to know that the people building the future were still human.
That’s the blind spot of every framework I’ve seen. They treat the project as a machine, not a community. They ignore the culture. They ignore the signals: Are the developers active on Discord? Do they respond to criticism? Do they communicate clearly when things go wrong? I’ve seen protocols with flawless code fail because the team was arrogant. I’ve seen protocols with messy code succeed because the community rallied around them.
Look at Uniswap. The code is simple. The governance is messy. But the community is resilient. They’ve survived forks, attacks, and regulatory scrutiny. That’s not captured in a risk matrix.
The pivot wasn’t the technology; it was the trust.
So what does this mean for you, the reader, in this bear market? First, stop reading frameworks. Start reading the chain. Download Dune Analytics. Learn to write a basic SQL query. It’s not hard. Second, join the communities. Not the Telegram groups. The real communities—the ones that discuss code, not price. Third, ask the question: “What happens if the team disappears tomorrow?” If the answer is “the protocol stops,” it’s not decentralized enough.
I’m not saying frameworks are useless. They are useful for organizing thoughts. But they are not a substitute for direct observation. The best analysis I ever did was on a napkin in a bar in Stockholm, drawing the flow of funds through a DeFi protocol. No AI. No spreadsheet. Just a pen and a conversation with the builder.
The future will be built by those who listen.
We’re in 2026 now. AI agents are trading on-chain. The next wave of innovation will be about human agency. How do we ensure that technology serves people, not the other way around? I’ve been working on a manifesto called “The Soul of the Code,” arguing that blockchain’s true value is its ability to verify human intent. Not just transactions. Intent.
That’s the insight the empty analysis missed. The “N/A” fields were not a failure of data. They were a failure of perspective. The author didn’t look for the human element. They looked for boxes to check.
I’ll leave you with this: the next bull market won’t be won by the best analysis. It will be won by the projects that remember why we’re here. To build a system that works for people, not for analysts. Trust is no longer a promise; it’s a protocol. But the protocol is only as good as the community that runs it.
So go look at the chain. Talk to the builders. Trust the code, but never forget the human.
We didn’t.