Lab: free tools · size first · stock scanner · crypto scanner · journal

General

Whitepaper

A whitepaper is a formal technical and economic document published by a cryptocurrency or blockchain project. It describes the problem being solved, the proposed technical solution, the tokenomics (token supply, distribution and incentive mechanisms) and the team's qualifications, and it serves as the foundational reference document for evaluating a project before investing.

A whitepaper is the document a crypto project publishes to explain what it does, how its technology and token work, and who is behind it. A good one is specific about the problem, the design and the token's role. Vague promises, unrealistic returns and copied content are warning signs. Reading the whitepaper and comparing it with what was actually built is a basic due diligence step.

Two famous examples

The Bitcoin whitepaper, posted by Satoshi Nakamoto on October 31, 2008, runs nine pages. It sets out the problem of double spending without a trusted party, then explains proof of work, the chain of blocks and why an attacker with less than half the computing power is unlikely to catch up. Vitalik Buterin's Ethereum whitepaper from 2013 laid out a blockchain with a built in programming language. Both are short, specific and testable against what was later built.

Whitepapers under MiCA

In the EU, the Markets in Crypto-Assets Regulation turned the whitepaper into a legal document. Since December 30, 2024, anyone offering most crypto assets to the public in the EU must publish a white paper in a set format, notify it to their national regulator and keep it up to date. The issuer can be held liable for information in it that is incomplete, unfair or misleading. That gives EU buyers something they can rely on, and a basis for a claim if it's wrong.

Reading one without wasting an afternoon

Start with the token section: supply, how it's split, vesting schedules and what the token is actually needed for. Read the team and the legal entity next, then the technical design, checking that it describes a real mechanism with specific numbers. Marketing pages and price charts inside a whitepaper are a poor sign.

After launch

Check that the token supply on chain matches the stated numbers and that team tokens vest on the stated schedule. Projects change plans, and that's fine if they say so publicly. If a whitepaper has been quietly edited, compare it with archived copies on the Wayback Machine.