What is the difference between a whitepaper and a lightpaper, and which should I read?
Crypto projects typically publish two types of documents. A whitepaper is the complete technical and business specification — detailed problem description, solution, technical architecture, and token mechanics. A lightpaper is a condensed version for general readers who don't want technical depth, usually just a few pages focused on the big picture and marketing narrative. For evaluating a project's investment value, read the whitepaper, not the lightpaper. Lightpapers are carefully crafted marketing materials presenting the project from the best angle, with incomplete detail and risk disclosure. If a project only has a lightpaper and no full whitepaper, that itself is a skepticism-worthy signal.
If I can't understand the technical sections, can I still get useful things from a whitepaper?
Yes, and much of the useful information isn't even in the technical sections. Token allocation and vesting schedules, problem statements, competitive analysis, target market, and use cases are sections that require almost no technical background. The technical section of a whitepaper is primarily for developers and auditors; people evaluating investment value should focus on the business logic and token mechanics. A whitepaper with deeply technical details but vague business problem statements is actually a potential red flag — using technical complexity to confuse non-technical investors is a common obfuscation strategy.
Should I only look at the official whitepaper or also third-party analysis reports?
Both, but understand their different purposes. The whitepaper is primary source material: written by the project team, reflecting their definition and commitments to themselves. Apply your evaluation frameworks to the whitepaper, not to someone else's analysis. Third-party analysis (research reports, KOLs, media coverage) is useful for: quickly understanding the domain background, finding market data you couldn't get from the whitepaper alone, and comparing different perspectives. The problem is that third-party analysis carries conflict-of-interest risk (many KOLs are paid to promote projects) and can contain errors. The healthiest approach: read the whitepaper yourself first to form an initial judgment, then check whether third-party analysis helps you find things you missed or challenges your judgment — rather than letting third parties substitute for your own judgment.
If a project passes all 5 frameworks, does that mean it's definitely worth investing in?
No — these 5 frameworks are a filter for whether to do further research, not a final conclusion on whether to invest. Passing them means: the project's foundational thesis is rational, the token design has no obvious pitfalls, the team background is verifiable, and the problem is real — all warranting more time for deeper research. Investment decisions also need to consider: how large is this sector's market? Does the execution team have the capability to deliver on whitepaper promises? Is the valuation (FDV, market cap) reasonable relative to current fundamentals? What is the market timing and macro environment? Use the 5 frameworks as a passing grade threshold, not a buy signal.
The whitepaper is a crypto project's most important primary source, yet the place where most investors spend the least time. Most people buy a coin based on other people's analyses, KOL recommendations, or community vibes — not by returning to the whitepaper and asking basic questions. These 5 evaluation frameworks let you extract an initial judgment from a whitepaper and public documents in 15 minutes: is this project worth researching further? It's not foolproof, but it filters out a large number of hollow projects.
Open the whitepaper and find the Problem Statement. Ask one question: how was this problem solved before blockchain existed? If the answer is there was no one actually bothered by this problem or the traditional solution is good enough, the project very likely invented the problem to justify the token, not vice versa. Good projects clearly state who the specific target users are, what pain point they face today, and why blockchain is necessary (not just a nice-to-have). Be suspicious of whitepapers that use heavy jargon and grand visions to mask the core fact that blockchain isn't really needed.
This is the most frequently overlooked and most effective question for exposing hollow projects. Find the token utility section and ask: if this token disappeared today, could the protocol still function? If the answer is yes, because the token is just for governance voting, then demand for this token is essentially manufactured with no fundamental business driver. Genuinely useful tokens are required to use or are consumed by the protocol itself — like ETH (paying Gas), BNB (fee discounts), or LINK (oracle node staking and payment). Some governance tokens have evolved real yield-sharing mechanisms, but judge the current reality, not the potential.
Find the token allocation and vesting schedule in the whitepaper or official documents. Evaluate with this core question: whose interests does this distribution protect? Warning signals: team allocation over 20% (industry norm is 10–15%); large private investor allocation with fast unlocks (6-month cliff then linear means high-profit early investors can exit quickly); public sale under 5% (most tokens reserved for insiders); and no verifiable on-chain lock contract (only whitepaper promises). Conversely, on-chain verifiable lock contracts, long enough vesting (at least 2–3 years), and reasonable public sale proportions are healthier signals.
Crypto has many anonymous or semi-anonymous projects; evaluating anonymous teams is especially important. Check a few angles: LinkedIn / personal pages: are core members' work histories real, without fabrication or exaggeration; GitHub commit history: does commit frequency and contributor count match the dozens of engineers advertised; past projects: have these people built other crypto or Web2 projects and what was the outcome; investor backers: tier-1 VC backing (a16z, Paradigm, Sequoia) doesn't guarantee success but suggests due diligence was done. Fully anonymous teams aren't necessarily bad (Satoshi was anonymous), but verifiable identities provide better accountability for ordinary investors.
Find the whitepaper's competitive analysis section — or more directly, ask yourself: if this project disappeared, what competitor could users switch to tomorrow? If there are ten completely similar projects with easy switching, this project has nearly zero moat. Projects with genuine moats typically have at least one of: network effects (more users = more value, like Ethereum mainnet); unique technical barriers (patents, unique algorithms, hard-to-replicate engineering advantages); regulatory or license advantages (licensed, compliant asset channels); or lock-in effects (high switching costs for users, like deep liquidity).
Running these 5 frameworks through a whitepaper and public materials puts your project judgment well above most people who only read KOL analysis — not because you have secret knowledge, but because you've returned to the most basic questions: does this thing serve a real purpose? is anyone actually using it? are earnings distributed to token holders in a fair way? These questions are easily buried under bull market profit-taking momentum, but in bear markets they determine which projects survive and which are one-cycle hypes. Making the whitepaper a required read before any trade is the first step from pure momentum-following to active research.