> 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-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-5/article-85.md). # Article 85 | | | | --------------- | ------------------------------------------------------------------------------- | | **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 | ### Identification of significant crypto-asset service providers 1. A [crypto-asset service provider](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service-provider) shall be deemed significant if it has in the Union at least 15 million active users, on average, in one calendar year, where the average is calculated as the average of the daily number of active users throughout the previous calendar year. 2. [Crypto-asset service](https://www.mica.wtf/definitions/definitions/mica/crypto-asset-service) providers shall notify their [competent authorities](https://www.mica.wtf/definitions/definitions/mica/competent-authority) within two months of reaching the number of active users as set out in paragraph 1. Where the [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md) agrees that the threshold set out in paragraph 1 is met, it shall notify ESMA thereof. 3. Without prejudice to the responsibilities of competent authorities under this Regulation, the competent authorities of the [home Member States](https://www.mica.wtf/definitions/definitions/mica/home-member-state) shall provide ESMA’s Board of Supervisors with annual updates on the following supervisory developments in relation to significant [crypto-asset](https://www.mica.wtf/definitions/definitions/mica/crypto-asset) service providers: 1. ongoing or concluded authorisations as referred to in [Article 59](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-59.md); 2. ongoing or concluded processes of withdrawal of authorisations as referred to in [Article 64](/mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-64.md); 3. the exercise of supervisory powers set out in [Article 94](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-1/article-94.md)(1), first subparagraph, points (b), (c), (e), (f), (g), (y) and (aa). The [competent authority](https://www.mica.wtf/definitions/definitions/mica/competent-authority) of the [home Member State](https://www.mica.wtf/definitions/definitions/mica/home-member-state) may provide ESMA’s Board of Supervisors with more frequent updates, or notify it prior to any decision taken by the competent authority of the home Member State with regard to the first subparagraph, point (a), (b) or (c). 4. The update referred to in paragraph 3, second subparagraph, may be followed by an exchange of views at ESMA’s Board of Supervisors. 5. Where appropriate, ESMA may make use of its powers under Articles 29, 30, 31 and 31b of Regulation (EU) No 1095/2010. ### Related * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/crypto-asset-service-provider.md) — definition used in this article * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service-provider.md) — definition used in this article * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/crypto-asset-service-provider.md) — definition used in this article * [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) — definition used in this article * [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.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 * [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-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-5/article-85.md?ask=&goal= ``` `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.