A whitepaper (also written "white paper") is a document in which a crypto project explains what it is building, how its technology works, what its token is for and how the token will be distributed. The term was borrowed from government and business reports, where a white paper sets out a position or proposal in detail. In crypto, it became the standard way to introduce a new blockchain, protocol or token to developers and buyers.
The best-known example is the nine-page Bitcoin white paper published by Satoshi Nakamoto on 31 October 2008. For many years crypto whitepapers had no fixed format or legal status, and quality ranged from rigorous technical papers to marketing brochures. In the European Union that changed with MiCA, which makes a "crypto-asset white paper" a regulated disclosure document with required content and legal liability.
Whitepaper in plain terms
Think of the plans and brochure an architect shows before a building goes up. They explain what the building is for, how it will stand, who paid for it and when it should open. A careful buyer reads them closely; a careless developer can fill them with pretty pictures and vague promises.
A crypto whitepaper plays the same role for a digital project. It is a promise about what will be built and how the token fits in. A good one lets experts check the design. A poor one is mostly sales talk, and the existence of a whitepaper says nothing on its own about whether the project is sound.
Landmark whitepapers
- Bitcoin (2008). "Bitcoin: A Peer-to-Peer Electronic Cash System" was posted to a cryptography mailing list on 31 October 2008. It described a peer-to-peer payment system that prevents double spending using proof of work and a chain of timestamped blocks. The Bitcoin network launched in January 2009.
- Ethereum (2013–2014). Vitalik Buterin circulated the Ethereum white paper in late 2013, proposing a blockchain with a built-in programming language for smart contracts. A more formal technical specification, the "yellow paper" by Gavin Wood, followed in 2014, and the Ethereum network launched in 2015.
- ICO-era papers (2017–2018). During the ICO boom thousands of projects published whitepapers to raise funds. Many described products that were never delivered, and some copied text from other projects.
Protocol changes after launch are usually documented through improvement proposals rather than new whitepapers; see BIPs and EIPs.
What a whitepaper usually contains
- Problem and purpose. What the project aims to solve and for whom.
- Technical design. Architecture, consensus method, security model and how the system scales.
- Token design. Supply, issuance, uses and distribution, often called tokenomics, including circulating and total supply.
- Sale terms. Price, caps such as a hard cap, and use of funds, if a token sale is planned.
- Team and roadmap. Who is behind the project and planned milestones.
- Risks. Technical, legal and market risks, required under some regimes.
Whitepapers under MiCA
MiCA (Regulation (EU) 2023/1114) applies in full from 30 December 2024. Its Title II covers crypto-assets other than asset-referenced tokens and e-money tokens. A person offering such crypto-assets to the public in the EU, or seeking admission to trading, must in most cases draw up a crypto-asset white paper with the information listed in Article 6 and Annex I, notify it to the national competent authority, and publish it. The authority does not approve it, and the paper must say so. Information must be fair, clear and not misleading, and the offeror and its management can be liable for losses caused by incomplete or misleading statements.
Some offers are exempt from Title II, such as very small offers, offers to qualified investors only, and offers of utility tokens that give access to an existing good or service, unless the token is to be traded on a platform run by a crypto-asset service provider. White papers for asset-referenced tokens need approval by the authority, and those for e-money tokens are notified by the issuing bank or e-money institution. In the United States, by contrast, a whitepaper has no special legal status, but statements in it can be used as evidence in securities cases brought by the SEC under the Howey Test.
Red flags and limitations
A whitepaper is written by the project itself, so readers are generally advised to check it critically. Warning signs include copied or plagiarised text, vague technical sections, missing information on who controls the token supply, unrealistic promises of returns, and anonymous teams. Many failed projects and rug pulls had professional-looking whitepapers, and tokens often trade far from anything the paper describes; independent research (DYOR) remains necessary.