> 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-2/article-110.md).

# Article 110

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

### Register of non-compliant entities providing crypto-asset services

1. ESMA shall establish a non-exhaustive register of entities that provide [crypto-asset services](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service) in violation of [Article 59](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-59.md) or [61](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-61.md).
2. The register shall contain at least the commercial name or the website of a non-compliant entity and the name of the [competent authority](https://www.mica.wtf/definitions/definitions/mica/competent-authority) that submitted the information.
3. The register shall be publicly available on ESMA’s website in a machine-readable format and shall be updated on a regular basis to take into account any changes of circumstances or any information that is brought to ESMA’s attention concerning the registered non-compliant entities. The register shall enable centralised access to information submitted by [competent authorities](https://www.mica.wtf/definitions/definitions/mica/competent-authority) from the Member States or third countries, as well as by EBA.
4. ESMA shall update the register to include information on any case of infringement of this Regulation identified on its own initiative in accordance with Article 17 of Regulation (EU) No 1095/2010 in which it has adopted a decision under paragraph 6 of that Article addressed to a non-compliant entity providing [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) services, or any information on entities providing [crypto-asset services](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service) without the necessary authorisation or registration submitted by the relevant supervisory authorities of third countries.
5. In the cases referred to in paragraph 4 of this Article, ESMA may apply the relevant supervisory and investigative powers of competent authorities as referred to in [Article 94](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-1/article-94.md)(1) to non-compliant entities providing [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) services.

***

**Level 2 instruments**

* [ESMA Statement — MiCA Data Standards and Format Requirements](/eu-level/soft-law/statement-on-mica-data-standards-format-requirements.md) — Statement

### Related

* [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md) — definition used in this article
* [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


---

# 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-2/article-110.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.