MiCAR requires a crypto-asset whitepaper for almost every public offering and admission to trading in the EU. But the rules differ substantially depending on the type of token — and there are important exemptions that many issuers overlook.

This guide covers when a whitepaper is required, what it must contain (with a mandatory content checklist by token type), the approval and notification process, and the consequences of getting it wrong.

Part 1: Do You Need a MiCAR Whitepaper?

The Default Rule

Under MiCAR Article 4 and Article 46, any offer to the public of crypto-assets in the EU — or any application for admission to trading on a crypto-asset trading platform — requires a whitepaper unless a specific exemption applies.

This applies to:

"Other" crypto-assets (tokens that are not ARTs or EMTs) — covered by Title III, Articles 4–15
Asset-referenced tokens (ARTs) — covered by Title IV, Articles 16–47
E-money tokens (EMTs) — covered by Title V, Articles 48–58

The whitepaper requirements differ meaningfully across these three categories.

When You DON'T Need a Whitepaper

MiCAR Article 4(2) provides six exemptions for "other" crypto-assets. Article 17(1) provides separate (narrower) exemptions for ARTs. EMTs have no public exemptions — a whitepaper is always required.

Exemptions for "other" crypto-assets (Article 4(2))

| Exemption | Condition | |-----------|-----------| | Small offering | Offered to fewer than 150 natural or legal persons per Member State | | Low-value offering | Total consideration of the offer across the EU does not exceed €1 million (or equivalent) over 12 months | | Free distribution | Crypto-assets offered for free (e.g., airdrops with no strings attached — the recipient gives no money, data, or work in exchange) | | Mining/validation | Crypto-assets created automatically as a mining or validation reward under the protocol (e.g., block rewards) | | Unique and non-fungible | The crypto-asset is unique and non-fungible — i.e., a genuine NFT that is not fractionalised and not fungible with other assets | | Qualified investors only | Offered exclusively to qualified investors and can only be held by qualified investors |

Important: The small offering (fewer than 150 persons) and low-value (below €1M) exemptions do not stack. Each applies independently. An issuer targeting fewer than 150 persons per Member State is exempt regardless of total consideration, and vice versa.

No whitepaper exemptions for ARTs

For asset-referenced tokens, there is no small/low-value exemption. Every ART requires a whitepaper — and that whitepaper must be approved by the competent authority before the token is offered to the public.

Bitcoin, Ether, and decentralised assets

ESMA's guidance (ESMA75-453128700-1272) confirms that fully decentralised crypto-assets — those with no identifiable issuer — fall outside the whitepaper obligation because there is no legal entity capable of drawing up and publishing one. Bitcoin (BTC) and Ether (ETH) are the clearest examples. Stablecoins issued by a central entity are not exempt.

Part 2: Whitepaper Requirements by Token Type

A. "Other" Crypto-Assets (Title III, Article 6)

For tokens that are not ARTs or EMTs, the whitepaper must contain all of the following under Article 6:

Section 1: Information About the Offeror or Person Seeking Admission

[ ] Legal name and registered address of the issuer (or offeror if different)
[ ] LEI (Legal Entity Identifier) or equivalent identifier
[ ] Business activities of the issuer — what the company does, other than the token project
[ ] Identity and contact details of majority shareholders (>20% voting rights or capital) if the offeror is not listed on a regulated market
[ ] Financial statements for the last two financial years (if available); or audited opening balance sheet if less than two years old
[ ] Ongoing legal proceedings or regulatory actions that could materially affect the project
[ ] Summary of principal risk factors relating to the issuer

Section 2: Information About the Project

[ ] Project name and a plain-language description of the main features
[ ] Purpose of the offering and intended use of proceeds raised
[ ] Description of the project's development stage and timeline to delivery
[ ] Identities of any third parties involved (advisors, contractors, infrastructure providers) and their role
[ ] Summary of principal risk factors relating to the project

Section 3: Information About the Crypto-Asset

[ ] Type of crypto-asset (e.g., utility token, payment token, hybrid)
[ ] Whether it is unique and non-fungible — if yes, how and why (relevant for NFT issuers testing the exemption boundary)
[ ] Total supply or, if no cap, the issuance algorithm
[ ] Initial offering price per unit (in fiat currency, if applicable) or issuance methodology
[ ] Distribution plan and intended recipients (including any free allocations, founding team vesting, etc.)
[ ] Rights and obligations attached to the crypto-asset — what can the holder do with it? What must the issuer provide?
[ ] Lock-up periods or transfer restrictions, if any
[ ] Regulatory status of the crypto-asset and any regulatory authorisation obtained or applied for

Section 4: Offering Terms

[ ] Minimum and maximum amount of the offering (or if no cap, a statement to that effect)
[ ] Minimum subscription amount per investor, if applicable
[ ] Payment currencies accepted
[ ] Offering start and end dates (or offer period methodology)
[ ] What happens if the minimum is not reached (cooling-off, refund mechanism)
[ ] Arrangements for the safekeeping of funds raised during the offering period

Section 5: Technology

[ ] Description of the distributed ledger technology (DLT) used or planned — public/private/permissioned, consensus mechanism
[ ] Smart contract address(es) where applicable, or explanation if smart contracts are not used
[ ] Security measures and protocols for the technology
[ ] Access protocols and procedures for holders of the crypto-asset
[ ] Whether a third-party technical audit of the smart contracts or protocol has been carried out (and if so, the auditor's findings)

Section 6: Rights and Obligations

[ ] Redemption rights, if any — under what conditions can a holder redeem the token, and at what value?
[ ] Governance rights — does the token confer voting or governance rights?
[ ] Economic rights — revenue share, yield, or other economic entitlements?
[ ] Transfer mechanics — how are tokens transferred on-chain? Any transfer restrictions?
[ ] Dispute resolution and applicable law

B. Asset-Referenced Tokens (Title IV, Article 19)

ART whitepapers must contain everything required for "other" crypto-assets PLUS the following additional sections:

Additional ART Requirements

[ ] Reference assets — clear description of each reference asset or basket of assets (currencies, commodities, crypto-assets, or rights) and the weighting of each
[ ] Reserve composition — description of the reserve of assets, how it is invested, the custody arrangements (which custodians, in which jurisdictions), and how it is segregated from the issuer's own assets
[ ] Redemption rights — any holder must be able to redeem the ART at face value (i.e., at the aggregate value of the reference assets) at any time; the whitepaper must explain how this works in practice
[ ] Stabilisation mechanism — how the peg is maintained; what happens if the reserve falls below the required level; any circuit breakers
[ ] Investment policy for the reserve — whether reserve assets are invested (money market funds, sovereign bonds), any yield generated, and whether/how that yield is passed to holders
[ ] Governance of the reserve — who manages it, how decisions are made, any independent oversight
[ ] Liquidity mechanism — arrangements to ensure sufficient liquidity for redemptions under normal and stress conditions
[ ] Insolvency protection — how holders' claims are protected if the issuer becomes insolvent (segregation, priority claim, etc.)

ART Approval Process

Unlike "other" crypto-assets, an ART whitepaper must be approved by the National Competent Authority (NCA) before the token is offered to the public or admitted to trading.

The process under Articles 21–22:

Application submission — Submit the draft whitepaper plus the full ART authorisation application (governance, capital, reserve plan, marketing materials) to the home Member State NCA
Completeness check — NCA has 25 working days to confirm the application is complete (or request missing information)
Assessment period — 60 working days from the date of confirmed completeness (NCA may extend by 20 working days for complex cases)
Decision — NCA approves or refuses; approval is published on the NCA's website
ESMA notification — NCA notifies ESMA; ESMA publishes approved ARTs on its register
EU passport — Once approved, the ART can be offered across all EU Member States without separate approval in each

Significant ART threshold: If the ART is projected to exceed 10 million holders, a daily transaction volume over €5 million, or €200 million in reserve value, ESMA must be notified and has specific additional oversight powers.

C. E-Money Tokens (Title V, Article 51)

EMT issuers must be authorised as credit institutions or electronic money institutions (EMIs) under the relevant EU directives. The whitepaper requirements for EMTs mirror the "other" crypto-asset requirements with important modifications:

EMT-Specific Requirements

[ ] The reference currency — EMTs must reference a single official EU currency (or in limited cases, another official currency)
[ ] The 1:1 redemption right — EMT holders must always be able to redeem at face value in the reference currency at any time at par; the whitepaper must explain the mechanism
[ ] Custody arrangements — funds received in exchange for EMTs must be held in segregated accounts at credit institutions; the whitepaper must identify the custodian
[ ] No interest payments — the whitepaper must confirm that no interest or similar benefit will be paid to EMT holders
[ ] Prohibition on investing reserve — EMT reserves must be deposited at credit institutions, not invested in financial instruments (unlike ART reserves)

EMT Notification Process

Unlike ARTs, EMTs do not require whitepaper approval from the NCA. Instead:

Notification — The issuer notifies the NCA at least 40 working days before the intended offering date (using the format specified by the competent authority)
NCA review — The NCA reviews but does not formally approve; it can require changes
Publication — The whitepaper is published on the issuer's website; the NCA can object within 20 working days of publication

Part 3: Common Mandatory Whitepaper Elements (All Types)

Regardless of token type, all MiCAR whitepapers must:

[ ] Be accurate, clear, and not misleading — the liability standard under Article 14 (for "other" crypto-assets) and Article 26 (for ARTs) is civil liability for loss suffered due to a whitepaper that contains false statements or material omissions
[ ] Be written in an official EU language — the language of the home Member State, plus any other language if offered cross-border
[ ] Include a clear, prominent disclaimer at the top — Article 6(2) requires a specific statutory warning box
[ ] Be published on the issuer's website — freely accessible for as long as the crypto-asset is offered or traded
[ ] Not constitute a prospectus — MiCAR whitepapers are not EU Prospectus Regulation documents; if your token qualifies as a financial instrument under MiFID II, the Prospectus Regulation applies instead
[ ] Include the date of the whitepaper
[ ] Be updated — any material change must trigger a whitepaper update (and re-notification or re-approval where applicable)

The Mandatory Warning Box

Article 6(2) requires a specific warning statement at the beginning of every "other" crypto-asset whitepaper. The warning must state:

"This crypto-asset whitepaper has not been approved by any competent authority in any Member State of the European Union. The offeror of the crypto-asset is solely responsible for the content of this crypto-asset whitepaper."

For ARTs and EMTs, the wording differs because those do involve NCA oversight — but a corresponding disclosure of regulatory status is required.

Part 4: Pre-Notification Requirement (All Types)

For "other" crypto-assets, the issuer must notify the NCA at least 20 working days before publishing the whitepaper.

This is a notification, not an approval. The NCA cannot prevent publication based on the notification alone — but the NCA can subsequently require changes or take action if the whitepaper is misleading.

For ARTs: The full approval process (see above) takes precedence — the 20-working-day notification is replaced by the 60-working-day approval process.

For EMTs: The 40-working-day notification requirement applies (see above).

Part 5: Trading Platform Obligations

If a crypto-asset trading platform lists a token, it must verify that a compliant whitepaper exists before admitting the asset to trading. Under Article 76, operators of trading platforms:

Must publish the whitepaper on their website
May not admit a "other" crypto-asset that has not had its whitepaper notified to the relevant NCA
Must de-list tokens where the issuer's whitepaper becomes non-compliant or where the issuer fails to update it following a material change

This creates a de facto listing standard: firms wishing to be listed on EU trading platforms must have a compliant, current whitepaper.

Part 6: Civil Liability for Whitepaper Defects

Article 14 (for "other" crypto-assets) and Article 26 (for ARTs) create a direct civil liability regime. If a whitepaper:

Contains a materially false or misleading statement
Omits material information that a prospective investor would need
Is not updated when a material change occurs

...then the issuer (and the persons who signed the whitepaper) are civilly liable to any purchaser who suffers a loss as a result. The burden of proof is reversed: the issuer must prove it did not breach the whitepaper standards, not the investor.

This liability attaches to the persons who signed the whitepaper — which is why most issuers use senior officers (CEO, CFO, board members) as signatories.

Summary: Whitepaper Requirements by Token Type

| Requirement | "Other" Crypto-Assets | ART | EMT | |-------------|----------------------|-----|-----| | Whitepaper required? | Yes (unless exempt) | Yes (always) | Yes (always) | | NCA approval needed? | No | Yes | No | | Pre-notification period | 20 working days | N/A (replaced by approval) | 40 working days | | Reserve description required? | No | Yes | Yes | | Redemption mechanism required? | No | Yes | Yes | | Interest payments permitted? | Yes | Limited | No | | EU passport on approval? | No (notification only) | Yes | Yes (via EMI passport) | | Civil liability for defects? | Yes (Art. 14) | Yes (Art. 26) | Yes |

Next Steps

If you are an issuer preparing a MiCAR whitepaper, the analysis above covers the mandatory content. The practical challenge is translating regulatory requirements into disclosure language that is both legally compliant and readable to non-specialist investors.

Use FinancialRegulations.EU to query the underlying regulation text — ask specific questions about Article 6, Article 19, or Article 51 requirements, get answers sourced directly from the regulation, and build your compliance checklist with confidence.

MiCAR Whitepaper Requirements: Mandatory Content Checklist by Token Type