Quick answer
The short answer
A crypto whitepaper is a document that explains your coin: the problem it solves, how the technology works, how many coins exist and who gets them, the team, a roadmap and the risks. Write it for a smart stranger in plain language, back every claim with a number or a link, and never promise a price. Keep it as short as clarity allows.
- Step 1: SummaryWhat the coin is, in one paragraph.
- Step 2: ProblemWho is stuck today, and why.
- Step 3: SolutionWhat your coin does about it.
- Step 4: TechnologyConsensus, block time, supply rules, wallets.
- Step 5: Coin supply and distributionHow many coins, who gets them, when.
- Step 6: Team and roadmapWho builds it, and what comes when.
- Step 7: RisksWhat could go wrong, said plainly.
- Step 8: Legal noticeWhat the document is not.
Eight sections. The hard part is not the structure. It is knowing what to leave out.
CHAPTER 01
What a whitepaper is, and what Bitcoin's looked like
A whitepaper is your coin's explanation, not an ad. Bitcoin's is the best model: short, specific and calm.
A whitepaper answers one question: why should anyone care about this coin? Readers include future users, miners, exchange staff, journalists and, in some places, regulators. They all skim first, so every section must make sense on its own.
The reference point is Bitcoin: A Peer-to-Peer Electronic Cash System, written by Satoshi Nakamoto and published on 31 October 2008. That was two months before the first block was mined. It has nine pages.
9 pages
is all it took to explain Bitcoin: an abstract, twelve numbered sections and a list of references.
Source: Bitcoin whitepaper (PDF)
| Bitcoin paper section | What it does | Your equivalent |
|---|---|---|
| Abstract and 1. Introduction | Names the problem and the idea | Summary, problem and solution |
| 2. Transactions, 3. Timestamp Server, 4. Proof-of-Work | Explains how the system works | Technology |
| 5. Network, 6. Incentive | How nodes behave and why they are paid | Technology, supply and distribution |
| 10. Privacy, 11. Calculations | Limits and attack maths | Risks |
| 12. Conclusion and References | Wraps up and shows sources | Roadmap and sources |
Section titles from the Bitcoin paper as published on the Nakamoto Institute library.
CHAPTER 02
The story sections: summary, problem, solution
This is the part most people read. Keep it short, specific and free of hype.
Write these three first and keep them to about a page together. If a reader stops here, they should still know what your coin is.
- Section 1
Summary
One paragraph: what the coin is, who it is for, and the single most important fact about it (for example, a fixed supply or fast blocks). Say that it has its own blockchain.
- Section 2
The problem
Name who is stuck and what they do today. A game studio paying fees to a platform. A community with no shared money. Be specific, with one real example.
- Section 3
The solution
What your coin changes. Link each feature to a problem from section 2. If a feature solves nothing above, cut it.
Use the words your readers use. Say "block time" the first time, then explain it in a few words: how often a new block is added. The complete guide to creating a cryptocurrency has plain explanations of the common terms.
CHAPTER 03
The technology section: your chain's real settings
A coin with its own blockchain has exact numbers. Write them down. This is where you earn trust.
This is where a coin with its own blockchain has an edge over a token. A token paper has to explain someone else's chain. Yours can state the exact settings you chose. Fill in every row:
| Setting | Plain meaning | Example of how to write it |
|---|---|---|
| Base code | The open-source software your coin starts from | Name the coin it is forked from and the version |
| Consensus | How the network agrees on new blocks | Proof of work, proof of stake or proof of authority, and why you chose it |
| Block time | How often a new block arrives | A target in seconds or minutes |
| Block reward and halving | New coins per block and how often that drops | Starting reward and the halving interval in blocks |
| Maximum supply | The most coins that can ever exist | A number, or "no cap" with the yearly rate |
| Genesis block | The first block of the chain | Its date and the message you put in it |
| Addresses and wallets | How people hold the coin | Address format and the wallets that exist |
| Explorer and nodes | How anyone can check the chain | The explorer link and the number of nodes at launch |
Use the numbers you actually chose. If something is not decided yet, write "to be decided" rather than a guess.
Explain the consensus choice in two or three sentences. Proof of work vs proof of stake covers how to decide. The genesis block deserves its own line in your paper, because it fixes the date your chain begins. Our genesis block guide explains what it is.
Add a simple diagram if you can: transactions go into blocks, blocks form the chain, and nodes check each other. One clear picture beats a page of text.
CHAPTER 04
Supply, team, roadmap and risks
The sections readers check for red flags: who gets the coins, who you are, what is next, and what could fail.
Supply and distribution
Show how many coins exist and who receives them: the premine (coins created for the owner at launch), the miners or validators, a community fund, anything reserved. A simple table works best. Add the date each amount is released. The tokenomics guide shows how to plan these numbers.
Team
Say who is building it and what they have done before, with links people can check. If the team prefers to stay anonymous, say so and explain how readers can still verify the project: open code, a public explorer and published settings.
Roadmap
- Launch
Chain, explorer and wallets live
A coin built with a tool like ours can be live in about 30 minutes.
- Next
Community and mining
A pool, a faucet if you want one, and the first users.
- Later
Listings and tools
Tracking sites and exchanges, once the coin has real activity.
Use phases, not exact dates, for anything you do not control. A missed date damages trust more than a vague one.
Risks
Write the risks like a warning label. The coin may lose value, may be hard to sell, the code may contain bugs, a small network can be attacked, and laws may change. The EU rule below requires several of these statements anyway, and readers respect a paper that says them first.
CHAPTER 05
The EU rule: when a white paper is required
Under MiCA, a public offer of a crypto-asset in the EU can need a formal white paper. Here is the simple version.
In the EU, the Markets in Crypto-Assets regulation (MiCA) turns the whitepaper from a nice extra into a legal document in some cases. Under Article 4 of the MiCA regulation, offering a crypto-asset to the public in the EU generally requires the offeror to be a legal person (a company, not an individual) who has drawn up, notified and published a crypto-asset white paper.
- Rule
Public offer in the EU
You need a white paper, a legal entity as the offeror, and the white paper must be notified and published.
- Exception
Small offers
The white paper duty does not apply if the total amount raised over 12 months does not exceed EUR 1,000,000.
The official text of Article 6 says what the document must contain. In plain English, the list is:
- Information about the offeror (and the issuer, if different).
- Information about the crypto-asset project.
- Information about the offer to the public.
- Information about the crypto-asset itself.
- The rights and obligations attached to it.
- The underlying technology.
- The risks.
- The main negative effects on the climate and environment of the consensus mechanism used.
It must also carry set statements. The first page says the offeror is solely responsible for the content. The document must state that the asset may lose value in part or in full, may not always be transferable, may not be liquid, and is not covered by investor compensation or deposit guarantee schemes. It must have a short, non-technical summary, show the date of notification, include a table of contents, and be available in a machine-readable format. It must not make assertions about the asset's future value.
CHAPTER 06
Your fill-in outline
Copy this checklist into a document and answer every line. Then edit it down.
Aim for plain English and short paragraphs, with one idea each. Export a PDF, and also publish the text as a web page on your own site. A web page is easy to link to, quote and update.
The outline is the easy part. The numbers in the technology section are what make it real.
If you do not have those numbers yet, the HeroRPC builder sets them as you go: base, consensus, block time, supply and more, with the price shown live. A coin with its own blockchain starts at $149 one-time, and you see the full price in the builder.
QUESTIONS
Questions people ask
What should a crypto whitepaper include?
A summary, the problem, your solution, the technology (consensus, block time, supply rules), how coins are distributed, the team, a roadmap, the risks and a legal notice. Back every claim with a number or a link.
How long should a crypto whitepaper be?
As long as it needs to be and no longer. Bitcoin's whitepaper is nine pages. Put the summary on the first page so a skimmer gets the point at once.
Do I need a whitepaper to launch a coin?
Nothing technical requires one. But readers, exchanges and tracking sites expect an explanation of the project, and in the EU a public offer of a crypto-asset can legally require a white paper. Ask a lawyer about your situation.
What is the MiCA white paper rule?
Under Article 4 of the EU MiCA regulation, a public offer of a crypto-asset needs a published white paper from a legal person, unless the total raised over 12 months does not exceed EUR 1,000,000. This is not legal advice.
Can I use a whitepaper template?
Yes, as a structure. The outline in this guide is one. But the content must be yours: copied text fails because it describes someone else's coin, and readers notice.
Should I put the price or returns in the whitepaper?
No. Do not promise returns or predict a price. It reads like a scam, and the EU rule says a white paper must not make assertions about future value.
What was the first crypto whitepaper?
Bitcoin's: "Bitcoin: A Peer-to-Peer Electronic Cash System" by Satoshi Nakamoto, published on 31 October 2008. Many later papers followed its habit of explaining the system step by step.
Where should I publish my whitepaper?
On your own website, as a normal web page and as a PDF download. Link it from your homepage, your explorer and anywhere you apply for a listing.
SOURCES
Sources and how we made this guide
- Bitcoin: A Peer-to-Peer Electronic Cash System (PDF) (nine pages, abstract, 12 numbered sections and references)
- Nakamoto Institute, Bitcoin whitepaper (title, author and publication date 31 October 2008, section titles)
- Bitcoin Wiki, Genesis block (first block dated 3 January 2009)
- ESMA, MiCA Article 4: offers to the public of crypto-assets other than ARTs or EMTs (white paper duty and the EUR 1,000,000 over 12 months exemption)
- ESMA, MiCA Article 6: content and form of the crypto-asset white paper (required information and statements)
Written by
Written and checked by the people who run HeroRPC's builder and node servers. Every figure links to its source.
Published . Last updated .
