A crypto whitepaper is the document a project publishes to explain what it is building, how the technology works, and how its token functions. Meant as the primary source on a project.
One document set the template. On 31 October 2008, Satoshi Nakamoto published "Bitcoin: A Peer-to-Peer Electronic Cash System." Nine pages, eight references, and the word "blockchain" never appears once.
What a whitepaper is supposed to contain
- The problem. What is broken, and why existing solutions do not fix it.
- The technical approach. How the system works, in enough detail that someone could evaluate it.
- Tokenomics. Total supply, distribution, allocation to team and investors, unlock schedule, and what the token actually does.
- Architecture. Consensus mechanism, network design, and dependencies on other systems.
- Team. Who is building it, with verifiable identities.
- Roadmap. What ships when.
- Risks. What could go wrong. Frequently absent, which is itself informative.
Covering the first two exceptionally, Bitcoin's whitepaper barely touches the rest. Technical proposal. Not a fundraising document.
How whitepapers changed
Worth understanding. It explains why the format lost credibility.
During the ICO boom of 2017 and 2018, a whitepaper became a fundraising instrument. Substantial sums were raised on documents describing systems nobody built. Plagiarism was common. So were fabricated team members, borrowed diagrams, and roadmaps with no engineering behind them.
As a signal today, a whitepaper carries far less weight than it did in 2013. Many serious projects now publish documentation, code repositories, and audit reports instead, treating the whitepaper as a formality.
So the question is no longer whether a project has one. What the document reveals when you actually read it is what counts.
How to read one critically
Work through it in this order, because the checks that eliminate the most projects sit near the top and cost the least time to run. Problems surface early.
1. Check the tokenomics before the technology. Total supply, circulating supply, and the allocation split. What percentage went to the team and early investors, and when does it unlock? Ahead of you, a large unlock is the single most predictive detail in most whitepapers.
2. Look for what the token does. Plenty of documents describe a system that works fine without the token, then attach one anyway. Where the function is "governance" and nothing else, ask what is being governed.
3. Test the problem statement. Does the problem exist? Is a blockchain the reasonable solution, or would a database work? Many projects fail on that question alone.
4. Check the team. Verifiable names, real histories, work you can look up. Anonymous teams are not automatically disqualifying, though they remove your recourse entirely.
5. Read the technical section for specificity. Real engineering has numbers, trade-offs, and acknowledged limitations. Vague technical language usually conceals nothing underneath.
6. Search for plagiarism. Paste distinctive sentences into a search engine. Projects still get caught this way.
7. Compare the roadmap to what shipped. With a document two years old, check what was delivered against what was promised. Nothing tells you more.
Warning signs
| Signal | Why it matters |
|---|---|
| Guaranteed or projected returns | No legitimate technical document includes these |
| Price predictions or charts | Marketing material dressed as research |
| No tokenomics section | The most important information is the missing information |
| Team photos without names | Stock imagery is common |
| Buzzword density with no specifics | Frequently conceals an absence of engineering |
| No risk section | Every real system has failure modes |
| Partnerships that cannot be confirmed | Named logos are routinely used without agreement |
The documents worth reading
Two repay reading for their own sake, whatever you happen to think of the assets they eventually produced or the industry that grew up around them.
Bitcoin's whitepaper runs nine pages and is largely comprehensible without a computer science background. It states a problem, proposes a mechanism, and stops.
Published by Vitalik Buterin in late 2013, Ethereum's whitepaper is longer and explains the reasoning behind programmable contracts rather than only the mechanism.
Both share a quality most later documents lack. They argue for something. Specifically enough to be wrong.
What a whitepaper does not tell you
- Whether the code exists. Documents are not implementations. Check the repo.
- Whether it still applies. Projects change direction. Plenty of whitepapers describe systems abandoned years ago.
- Whether the team can execute. Writing a plausible design and shipping it are unrelated skills.
- Whether the token will do anything. Tokenomics describe intended mechanics, never outcomes.
- Whether an audit was passed. Separate document entirely, and its absence is worth noting.
Where mb.io fits
Reading a whitepaper is part of assessing a token. To trade one, you want somewhere that reviewed it too, which is what a regulated crypto exchange does.
mb.io is a regulated crypto spot exchange backed by MultiBank Group, a financial institution founded in 2005 that serves more than 2 million clients across 100+ countries.
- Every listed asset is reviewed before it reaches the platform
- Regulated by VARA in the UAE and AUSTRAC in Australia
- 10/10 security score from Hacken, an independent blockchain security auditor
- Institutional-grade MPC custody powered by Fireblocks, with segregated client funds
- Buy, sell, and swap in three steps, from sign-up to purchase
- 24/7 customer support, on web and on the iOS and Android apps
Open your account and start trading on mb.io.
Frequently asked questions
What is a crypto whitepaper?
A document published by a project to explain what it is building, how the technology works, and how its token functions. Intended as the primary technical reference.
When was the Bitcoin whitepaper published?
31 October 2008, by Satoshi Nakamoto, under the title "Bitcoin: A Peer-to-Peer Electronic Cash System." Nine pages, and the word "blockchain" never appears.
Do all crypto projects have a whitepaper?
Most do, and it means less than it once did. Serious projects now prioritise documentation, public code, and audit reports. Plenty of projects with no substance publish polished whitepapers.
What should I look for in a whitepaper?
Tokenomics first: supply, allocation to team and investors, and the unlock schedule. Then whether the token has a function, whether the problem is real, whether the team is verifiable, and what actually shipped since publication.
Are whitepapers reliable?
As a signal, considerably less than during the 2013 to 2016 period. During the ICO boom of 2017 and 2018 came widespread plagiarism, fabricated teams, and documents describing systems nobody built.
What is the difference between a whitepaper and a litepaper?
A litepaper is a shorter, less technical summary aimed at a general audience. Some projects publish both. Where only a litepaper exists, the detailed reasoning has not been made public.
Does a whitepaper mean a project is legitimate?
No. Producing a document costs almost nothing, and both the pump and dump and rug pull playbooks routinely include one. Starting point for research rather than evidence.
Where can I find a project's whitepaper?
Usually on the project's own site, and sometimes in its public code repository. Reaching it through the official domain matters rather than a link in a message, since fake documents on fake sites are a standard phishing route.
