Chapter 35 Key Takeaways

The 10-Point Evaluation Framework

  1. What problem does it solve? A project must address a real, specific, measurable problem that identifiable users have today. Vague problem statements ("fixing finance," "decentralizing everything") are not sufficient. Apply the "show me the user" test: can you point to a specific person or organization actively seeking this solution?

  2. Does it need a blockchain? The "would a database work?" test separates projects that genuinely require decentralized consensus, censorship resistance, and trustless operation from projects that use blockchain as a fundraising mechanism. If all parties trust a single operator, a database suffices.

  3. What is the consensus mechanism and security model? Evaluate the technical architecture for its specific trade-offs. PoW security depends on hash rate; PoS security depends on stake distribution. Every blockchain makes trade-offs between security, decentralization, and throughput. The relevant question is whether the trade-offs match the use case.

  4. Who controls governance? Determine where decision-making power actually resides, regardless of marketing claims. Watch for "decentralization theater" — projects that claim decentralization while one entity controls admin keys, validators, or upgrade paths.

  5. What are the tokenomics? Analyze token utility, supply dynamics, vesting schedules, and the ratio of circulating supply to total supply. The fully diluted valuation (FDV) is more relevant than market cap for evaluating whether a token is overpriced. Unrealistic APY (above 50% sustained) is almost always unsustainable.

  6. Who funded it and what are their incentives? Follow the money. Evaluate team doxxing, VC allocation percentages, unlock schedules, and whether insiders' incentives align with long-term project health. Short vesting with large allocations incentivizes pump-and-dump behavior.

  7. Has the code been audited? Audits are necessary but not sufficient. They are time-limited, scope-limited, and do not guarantee bug-free code. Look for multiple audits from reputable firms, active bug bounties, and defense-in-depth (monitoring, insurance, timelocked admin functions).

  8. What is the track record? Years of secure operation with real value at stake is the strongest evidence a project works. The Lindy effect applies: longevity correlates with continued survival. Delivery against roadmap promises is a secondary but important signal.

  9. What does the regulatory landscape look like? Assess whether the token might be classified as a security, whether the project's activities require licensing, and whether the project operates in regulatory-friendly jurisdictions with competent legal counsel.

  10. What would have to be true for this to succeed? Articulate the full assumption chain and evaluate each assumption independently. Calculate compound probabilities. Perform a "pre-mortem" exercise to identify likely failure modes.

Scam Detection Essentials

  • Rug pulls involve the team draining the liquidity pool. Hard rug pulls use contract manipulation; soft rug pulls involve gradual abandonment.
  • Honeypots allow buying but prevent selling for all non-deployer addresses. Detectable by checking on-chain sell history or using scanning tools.
  • The "absolute deal-breaker" combination: Anonymous team + unverified contracts + unrealistic yields = assume scam until proven otherwise.
  • The "15-minute check" can eliminate most scams quickly: verify contract source, check holder concentration, verify team identities, confirm audit existence, check TVL trends.

Core Principles

  • Default to skepticism. More than 90% of crypto projects fail. The burden of proof is on the project, not on you.
  • Follow the money, not the narrative. On-chain data, token distribution, and unlock schedules are facts. Whitepapers, roadmaps, and community sentiment are stories.
  • Track record beats promises. Functioning systems with years of operation outweigh any whitepaper, endorsement, or audit.
  • Challenge your own conclusions. Steel-man the opposing view. The contrarian check protects against confirmation bias, FOMO, and social proof.
  • Price action is not evidence of quality. Rising prices do not validate a project. In a honeypot or low-liquidity environment, prices can rise purely from one-directional flow.
  • Use tools, not vibes. Block explorers, analytics dashboards, and contract scanners provide objective data. Community sentiment and influencer opinions do not.