> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-19.md).

# Article 19

|                 |                                                                                 |
| --------------- | ------------------------------------------------------------------------------- |
| **Instrument**  | Regulation (EU) 2023/1114 (MiCA)                                                |
| **Source**      | [EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32023R1114) |
| **Status**      | In force                                                                        |
| **Review rule** | Legal-text changes require human review                                         |

### Content and form of the crypto-asset white paper for asset-referenced tokens

1. A [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) white paper for an [asset-referenced token](https://www.mica.wtf/definitions/definitions/mica/asset-referenced-token) shall contain all of the following information, as further specified in Annex II:

   1. information about the [issuer](https://www.mica.wtf/definitions/definitions/mica/issuer) of the [asset-referenced token](https://www.mica.wtf/definitions/definitions/mica/asset-referenced-token);
   2. information about the [asset-referenced token](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/asset-referenced-token.md);
   3. information about the [offer to the public](https://www.mica.wtf/definitions/definitions/mica/offer-to-the-public) of the [asset-referenced token](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/asset-referenced-token.md) or its admission to trading;
   4. information on the rights and obligations attached to the asset-referenced token;
   5. information on the underlying technology;
   6. information on the risks;
   7. information on the [reserve of assets](https://www.mica.wtf/definitions/definitions/mica/reserve-of-assets);
   8. information on the principal adverse impacts on the climate and other environment-related adverse impacts of the [consensus mechanism](https://www.mica.wtf/definitions/definitions/mica/consensus-mechanism) used to issue the asset-referenced token.

   The [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) white paper shall also include the identity of the person other than the [issuer](https://www.mica.wtf/definitions/definitions/mica/issuer) that offers to the public or seeks admission to trading pursuant to [Article 16](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-16.md)(1), second subparagraph, and the reason why that particular person offers that asset-referenced token or seeks its admission to trading. In cases where the crypto-asset white paper is not drawn up by the issuer, the crypto-asset white paper shall also include the identity of the person that drew up the crypto-asset white paper and the reason why that particular person drew it up.
2. All information listed in paragraph 1 shall be fair, clear and not misleading. The [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) white paper shall not contain material omissions and shall be presented in a concise and comprehensible form.
3. The [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) white paper shall not contain any assertions as regards the future value of the crypto-assets, other than the statement referred to in paragraph 4.
4. The crypto-asset white paper shall contain a clear and unambiguous statement that:
   1. the asset-referenced token may lose its value in part or in full;
   2. the asset-referenced token may not always be transferable;
   3. the asset-referenced token may not be liquid;
   4. the asset-referenced token is not covered by the investor compensation schemes under Directive 97/9/EC;
   5. the asset-referenced token is not covered by the [deposit](https://www.mica.wtf/definitions/definitions/mica/deposit) guarantee schemes under Directive 2014/49/EU.
5. The crypto-asset white paper shall contain a statement from the [management body](https://www.mica.wtf/definitions/definitions/mica/management-body) of the [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md) of the asset-referenced token. That statement shall confirm that the crypto-asset white paper complies with this Title and that, to the best of the knowledge of the management body, the information presented in the crypto-asset white paper is fair, clear and not misleading and the crypto-asset white paper makes no omission likely to affect its import.
6. The crypto-asset white paper shall contain a summary, inserted after the statement referred to in paragraph 5, which shall in brief and non-technical language provide key information about the [offer to the public](https://www.mica.wtf/definitions/definitions/mica/offer-to-the-public) of the asset-referenced token or the intended admission to trading of the asset-referenced token. The summary shall be easily understandable and presented and laid out in a clear and comprehensive format, using characters of readable size. The summary of the crypto-asset white paper shall provide appropriate information about the characteristics of the asset-referenced token concerned in order to help prospective holders of that asset-referenced token to make an informed decision.

   The summary shall contain a warning that:

   1. it should be read as an introduction to the crypto-asset white paper;
   2. the prospective holder should base any decision to purchase the asset-referenced token on the content of the crypto-asset white paper as a whole and not on the summary alone;
   3. the [offer to the public](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/offer-to-the-public.md) of the asset-referenced token does not constitute an offer or solicitation to purchase [financial instruments](https://www.mica.wtf/definitions/definitions/mica/financial-instrument) and that any such offer or solicitation can be made only by means of a prospectus or other offer documents pursuant to the applicable national law;
   4. the crypto-asset white paper does not constitute a prospectus as referred to in Regulation (EU) 2017/1129 or any other offer document pursuant to Union or national law.

   The summary shall state that the holders of asset-referenced tokens have a right of redemption at any time, and the conditions for such redemption.
7. The crypto-asset white paper shall contain the date of its notification and a table of contents.
8. The crypto-asset white paper shall be drawn up in an official language of the [home Member State](https://www.mica.wtf/definitions/definitions/mica/home-member-state), or in a language customary in the sphere of international finance.

   Where the asset-referenced token is also offered in a Member State other than the [issuer](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/issuer.md)’s [home Member State](https://www.mica.wtf/definitions/definitions/mica/home-member-state), the crypto-asset white paper shall also be drawn up in an official language of the [host Member State](https://www.mica.wtf/definitions/definitions/mica/host-member-state), or in a language customary in the sphere of international finance.
9. The crypto-asset white paper shall be made available in a machine-readable format.
10. ESMA, in cooperation with EBA, shall develop draft implementing technical standards to establish standard forms, formats and templates for the purposes of paragraph 9.

    ESMA shall submit the draft implementing technical standards referred to in the first subparagraph to the Commission by 30 June 2024.

    Power is conferred on the Commission to adopt the implementing technical standards referred to in the first subparagraph in accordance with Article 15 of Regulation (EU) No 1095/2010.
11. ESMA, in cooperation with EBA, shall develop draft regulatory technical standards on the content, methodologies and presentation of information referred to in paragraph 1, first subparagraph, point (h), in respect of the sustainability indicators in relation to adverse impacts on the climate and other environment‐related adverse impacts.

    When developing the draft regulatory technical standards referred to in the first subparagraph, ESMA shall consider the various types of [consensus mechanisms](https://www.mica.wtf/definitions/definitions/mica/consensus-mechanism) used to validate transactions in crypto-assets, their incentive structures and the use of energy, renewable energy and natural resources, the production of waste and greenhouse gas emissions. ESMA shall update those regulatory technical standards in the light of regulatory and technological developments.

    ESMA shall submit the draft regulatory technical standards referred to in the first subparagraph to the Commission by 30 June 2024.

    Power is delegated to the Commission to supplement this Regulation by adopting the regulatory technical standards referred to in the first subparagraph of this paragraph in accordance with Articles 10 to 14 of Regulation (EU) No 1095/2010.

***

**Level 2 instruments**

* [2025/422 — Sustainability Indicators](/eu-level/technical-standards/rts/regulatory-technical-standards-sustainability-indicators-adverse-climate-environment-impacts.md) — RTS
* [2024/2984 — White Paper Format](/eu-level/technical-standards/its/implementing-technical-standards-forms-formats-templates-crypto-asset-white-papers.md) — ITS
* [ESMA75-453128700-1229 — Second Technical Standards Package](/eu-level/technical-standards/final-reports/final-report-on-the-technical-standards-specifying-certain-requirements-of-mica-2nd-package.md) — Final Report (final draft submitted)

### Related

* [asset-referenced token](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/asset-referenced-token.md) — definition used in this article
* [consensus mechanism](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/consensus-mechanism.md) — definition used in this article
* [offer to the public](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/offer-to-the-public.md) — definition used in this article
* [home Member State](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/home-member-state.md) — definition used in this article
* [host Member State](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/host-member-state.md) — definition used in this article
* [reserve of assets](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/reserve-of-assets.md) — definition used in this article
* [management body](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/management-body.md) — definition used in this article
* [management body](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/management-body.md) — definition used in this article


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.mica.wtf/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-19.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
