> 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-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-1/article-97.md).

# Article 97

|                 |                                                                                 |
| --------------- | ------------------------------------------------------------------------------- |
| **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                                         |

### Promotion of convergence on the classification of crypto-assets

1. By 30 December 2024, the ESAs shall jointly issue guidelines in accordance with Article 16 of Regulation (EU) No 1093/2010, Article 16 of Regulation (EU) No 1094/2010 and Article 16 of Regulation (EU) No 1095/2010 to specify the content and form of the explanation accompanying the [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) white paper referred to in [Article 8](/mica/title-ii-crypto-assets-other-than-asset-referenced-tokens-or-e-money-tokens-art.-4-15/article-8.md)(4) and of the legal opinions on the qualification of [asset-referenced tokens](https://www.mica.wtf/definitions/definitions/mica/asset-referenced-token) referred to in [Article 17](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-17.md)(1), point (b)(ii), and [Article 18](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-18.md)(2), point (e). The guidelines shall include a template for the explanation and the opinion and a standardised test for the classification of crypto-assets.
2. The ESAs shall, in accordance with Article 29 of Regulation (EU) No 1093/2010, Article 29 of Regulation (EU) No 1094/2010 and Article 29 of Regulation (EU) No 1095/2010, respectively, promote discussion among [competent authorities](https://www.mica.wtf/definitions/definitions/mica/competent-authority) on the classification of the [crypto-assets](https://www.mica.wtf/definitions/definitions/mica/crypto-asset), including on the classification of those crypto-assets that are excluded from the scope of this Regulation pursuant to [Article 2](/mica/title-i-subject-matter-scope-and-definitions-art.-1-3/article-2.md)(3). The ESAs shall also identify the sources of potential divergences in the approaches of the competent authorities to the classification of those crypto-assets and shall, to the extent possible, promote a common approach thereto.
3. [Competent authorities](https://www.mica.wtf/definitions/definitions/mica/competent-authority) of the home or the [host Member States](https://www.mica.wtf/definitions/definitions/mica/host-member-state) may request ESMA, EIOPA or EBA, as appropriate, for an opinion on the classification of crypto-assets, including those that are excluded from the scope of this Regulation pursuant to [Article 2](/mica/title-i-subject-matter-scope-and-definitions-art.-1-3/article-2.md)(3). ESMA, EIOPA or EBA, as applicable, shall provide such opinion in accordance with Article 29 of Regulation (EU) No 1093/2010, Article 29 of Regulation (EU) No 1094/2010 and Article 29 of Regulation (EU) No 1095/2010, as applicable, within 15 working days of receipt of the request from the competent authorities.
4. The ESAs shall jointly draw up an annual report based on the information contained in the register referred to in [Article 109](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-109.md) and on the results of their work referred to in paragraphs 2 and 3 of this Article, identifying difficulties in the classification of crypto-assets and divergences in the approaches of the competent authorities.

***

**Level 2 instruments**

* [EBA/GL/2024/16 — CASP Supervisory Reporting](/eu-level/guidelines/guidelines-on-templates-to-assist-competent-authorities-in-performing-their-supervisory-duties.md) — Guidelines
* [JC 2024/28 — Crypto Classification Test](/eu-level/guidelines/esas-guidelines-on-templates-for-explanations-and-opinions-and-the-standardised-test.md) — Guidelines

### Related

* [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) — definition used in this article
* [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/crypto-asset.md) — definition used in this article
* [C714 — Adoption of Joint ESAs Guidelines on templates and the standardised test for crypto-asset classification](broken://pages/Djb9Q6hTR6upFdN1vLbF) — national implementation reference
* [Policy Statement PS-03-2024 — Fees and submission requirements for MiCAR entities](broken://pages/pJJYgqJ8UcYBtDYq7ezl) — national implementation reference
* [The European Supervisory Authorities have issued a number of guidelines regarding crypto-assets](broken://pages/s0R3qIWNoYK2NAvReQ2W) — national implementation reference
* [Crypto-asset activities — guidelines of the European Supervisory Authorities](broken://pages/c200vTKVxnI3r0kTMqnh) — national implementation reference
* [Markets in Crypto-Assets (MiCA) — HCMC crypto-assets hub](broken://pages/ObjLwuhaUIjweG5uYzp9) — national implementation reference
* [Markets in Crypto-Assets Regulation (MiCAR) - Central Bank of Ireland](broken://pages/XoXD0jhcrvQXfABY9b3g) — national implementation reference


---

# 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-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-1/article-97.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.