Whitepaper
A whitepaper is the document in which a project states the problem it solves, how it works technically and how the tokens are distributed. It is the first thing worth reading and the first thing that gets faked.
Where it comes from
The genre was set by Satoshi Nakamoto's 2008 document: nine pages describing bitcoin's mechanics with no promises of returns and not a word about price. It reads in half an hour and remains the model for how this is done.
By 2017 the form had degenerated. Whitepapers became marketing brochures with roadmaps, teams made of stock photography, and sections about revolutionising an industry without a single technical detail.
So the value of the document today is not that it exists but what is actually in it and whether any of it can be checked.
What to look for
- The problem before the solutionA good document explains why existing approaches fail. Without that, the blockchain is usually unnecessary here.
- Token distribution in numbersTeam and investor shares, the unlock schedule. The absence of that section is itself an answer.
- What the token is forIf the product would work without the token, the token exists to raise money rather than to make anything work.
- Checkable claimsLinks to code, benchmarks, named partners you can ask. Promises about the future cost nothing.
- The tonePrice forecasts, guaranteed returns and the word "revolutionary" in a technical document signal the wrong audience.