A substantive whitepaper does four things. It states the problem in terms you could disagree with, describes the mechanism concretely enough to be criticised, admits the trade-offs the design accepts, and explains the role of its <a href="/glossary/token/">token</a> — total supply, how it was distributed, who received allocations and on what unlock schedule. That last section is usually the most informative page in the whole document, and vagueness there is the loudest signal it can send.
Polish proves nothing on its own. Anyone can hire a designer and a copywriter, and a whitepaper is not peer-reviewed by anybody. Passages copied wholesale from other papers are common. So are documents dense with formulae that map to no working code. The checks that actually help are boring ones: is there a public repository with real commit history, does the audit exist and what did it actually cover, have the named advisors publicly confirmed they are involved, and does what shipped resemble what was promised. Our guide on <a href="/toolkit/how-to-spot-crypto-scams/">how to spot crypto scams</a> walks through the same instincts.
Whitepapers also get quietly edited. Save a copy with the date you downloaded it, because what changed between versions is often more revealing than the current text. A paper promising a fixed supply while the deployed contract allows minting, or describing governance the contract never implements, tells you the document and the code have parted company — a pattern that shows up repeatedly ahead of a <a href="/glossary/rug-pull/">rug pull</a>.
Read it, by all means. Just remember the code is the thing that runs, and the paper is what somebody would like you to believe about it.
How to Evaluate a Crypto Project
Key takeaways
- The token distribution and unlock schedule are usually the most informative part of any whitepaper.
- Design quality and equation count tell you about a project's budget, not about its engineering.
- Save a dated copy, because whitepapers are edited and the changes are often the interesting part.
Whitepaper — frequently asked questions
Does every legitimate project have a whitepaper?
Not necessarily. Some serious projects publish specifications, documentation and code instead, which are harder to fake and easier to check. Others produce a glossy paper and little else. The presence of a whitepaper is neither a credential nor a red flag on its own. What matters is whether there is a verifiable description of how the system works and whether the running code matches it.
What should I look at first in a whitepaper?
Go straight to the token section. Find the total supply, how it was allocated between the team, investors and the public, and when locked allocations are released. Then look for what the document does not say: no named team, no explanation of where revenue comes from, no discussion of what could go wrong. A paper that only describes upside has told you something important about its authors.
New to crypto, or filling in the gaps? Work through the essentials in Learn, browse every term A–Z, or see live prices for the coins these concepts power.