> 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/eu-level/technical-standards/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable.md). # 2025/421 — White Paper Classification | | | | ---------------- | -------------------------------------------------------------------------------------------------------------- | | **Instrument** | Commission Delegated Regulation (EU) 2025/421 (RTS) | | **Drafted by** | ESMA | | **Legal basis** | [Article 109(8) MiCA](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-109.md) | | **Status** | In force | | **In force** | 13 April 2025 (twentieth day after OJ publication on 24 March 2025) | | **Applies from** | 23 December 2025 | | **Source** | [EUR-Lex](https://eur-lex.europa.eu/eli/reg_del/2025/421/oj/eng) | ### Recitals 1. In accordance with Regulation (EU) 2023/1114, the register of [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) white papers, of issuers of asset-referenced tokens and e-money tokens, and of [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) providers (‘register’) established in accordance with [Article 109](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-109.md) of Regulation (EU) 2023/1114 is to contain information allowing the register to facilitate the accessibility of white papers classified on the basis of the types of crypto-assets set out in that Regulation. The data necessary for the classification of crypto-asset white papers should support national competent authorities in their task of verifying that the requirements of Regulation (EU) 2023/1114 are applied consistently. 2. To ensure the most efficient operation of the register, competent authorities should submit the data to the European Securities and Markets Authority (ESMA) in the same format as the white paper. Furthermore, to minimise costs, ESMA and competent authorities should be able to derive the relevant data for the classification of white papers in the register from the information disclosed in [crypto-asset](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset.md) white papers. To minimise the changes in the data required as of the date of application of [Article 110](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-110.md) of Regulation (EU) 2023/1114, the data used to classify crypto-asset white papers should comprise the data that competent authorities will provide to the European Single Access Point (ESAP) in accordance with Article 5(1), point (e), of Regulation (EU) 2023/2859 of the European Parliament and of the Council. 3. To ensure efficient processing of data, legal persons drawing up the crypto-asset white paper and identified therein by an ISO 17442 [legal entity identifier](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/legal-entity-identifier.md) (LEI) should ensure that such LEI is valid and duly renewed. Where the person drawing up the white paper does not have a LEI, the register should contain an identifier that ensures similar characteristics for the purposes of the register. 4. Crypto-assets that are not financial instruments cannot at present be described by using the ISO Classification of Financial Instruments (CFI) code. A standard universal method of classification is being developed. However, this method of classification will not be finalised before the application of this Regulation. Hence, to identify the crypto-asset white papers consistently in the register referred to in [Article 109(1)](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-109.md) of Regulation (EU) 2023/1114, an international standard identifier for digital tokens, the Functionally Fungible [Group](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/group.md) Digital Token Identifier (FFG DTI) should be used. Furthermore, to identify the crypto-assets and to allow users to retrieve the main characteristics of the crypto-assets, including their technology-specific features, and to group tokens issued on several blockchains that are pertaining to the same crypto-asset white paper, the ISO 24165 Digital Token Identifiers (DTI) should be used. The FFG DTI and the DTI are appropriate for the purposes of the register since they respect the principles of uniqueness, neutrality, reliability, open source, scalability, accessibility on a cost-recovery basis and they are offered under an appropriate governance framework. 5. Since this Regulation concerns the classification of crypto asset white papers and is therefore linked to Commission Implementing [Regulation (EU) 2024/2984](/eu-level/technical-standards/its/implementing-technical-standards-forms-formats-templates-crypto-asset-white-papers.md) which concerns standard forms, formats and templates for the white paper, it is necessary to align the dates of application of the two Regulations. The deferred application is also necessary to enable persons drawing up crypto-asset white papers and competent authorities to adapt to the requirements laid down in this Regulation. 6. This Regulation is based on the draft regulatory technical standards submitted to the Commission by ESMA. 7. ESMA has conducted open public consultations on the draft regulatory technical standards on which this Regulation is based, analysed the potential related costs and benefits and requested the advice of the Securities and Markets Stakeholder [Group](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/group.md) established in accordance with Article 37 of Regulation (EU) No 1095/2010 of the European Parliament and of the Council, ### Article 1 — Data for the classification of crypto-asset white papers 1. The data necessary for the classification of crypto-asset white papers is set out the Annex. 2. The data set out in the Annex shall be provided in a common format in accordance with the ISO 20022 standard. 3. By way of derogation from paragraph 2 of this Article, where the data set out in the Annex is included in the crypto-asset white paper referred to in [Article 6](/mica/title-ii-crypto-assets-other-than-asset-referenced-tokens-or-e-money-tokens-art.-4-15/article-6.md), [Article 19](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-19.md) or [Article 51](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-51.md) of Regulation (EU) 2023/1114, the data set out in the Annex to this Regulation may be provided in the same machine-readable format in which the crypto-asset white paper was prepared in accordance with Implementing Regulation (EU) 2024/2984. ### Article 2 — Legal Entity Identifiers When using the ISO 17442 [Legal Entity Identifier](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/legal-entity-identifier.md), persons drawing up a crypto-asset white paper referred to in [Articles 6](/mica/title-ii-crypto-assets-other-than-asset-referenced-tokens-or-e-money-tokens-art.-4-15/article-6.md), [Article 19](/mica/title-iii-asset-referenced-tokens-art.-16-47/chapter-1/article-19.md) or [Article 51](/mica/title-iv-e-money-tokens-art.-48-48/chapter-1/article-51.md) of Regulation (EU) 2023/1114 shall ensure that the identifier is:\ a) valid and issued in accordance with the terms of any of the Local Operating Units of the Global Legal Entity Identifier System;\ b) included in the Global Legal Entity Identifier database maintained by the Central Operating Unit appointed by the Regulatory Oversight Committee. ### Article 3 — Identification of the crypto-asset and the related white paper 1. When the ISO 24165 Digital Token Identifier is provided, the crypto-asset white paper shall be identified with a valid identifier of type 3 pertaining to the group of crypto-assets to which the white paper relates. 2. When the ISO 24165 Digital Token Identifier is provided, the crypto-asset or crypto-assets to which the crypto-asset white paper relates shall be individually identified with a valid identifier assigned to each of the crypto-assets to which the white paper relates. 3. When the ISO 24165 Digital Token Identifier is not available, the crypto-asset white paper shall identify the crypto-assets to which the crypto-asset white paper relates, by using a digital token identifier approved by ESMA at Union level, which meets all of the following characteristics:\ a) unique;\ b) neutral;\ c) reliable;\ d) open source;\ e) scalable;\ f) accessible;\ g) available at a reasonable cost basis; and\ h) is subject to an appropriate governance framework. ### Article 4 — Entry into force and application This Regulation shall enter into force on the twentieth day following that of its publication in the *Official Journal of the European Union*. This Regulation shall apply from 23 December 2025. ### Annex — Data necessary for the classification of crypto-asset white papers in the register referred to in [Article 109](/mica/title-vii-competent-authorities-eba-and-esma-art.-93-138/chapter-2/article-109.md) of Regulation (EU) 2023/1114 #### Legend | SYMBOL | DATA TYPE | DEFINITION | | -------------------- | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | {ALPHANUM-n} | Up to n alphanumerical characters | Free text field. | | {DATE\_TIME\_FORMAT} | ISO 8601 date and time format | Date and time in the following format: YYYY-MM-DDThh:mm:ss.ddddddZ. — ‘YYYY’ is the year, — ‘MM’ is the month, — ‘DD’ is the day, — ‘T’ – means that the letter ‘T’ shall be used, — ‘hh’ is the hour, — ‘mm’ is the minute, — ‘ss.dddddd’ is the second and its fraction of a second, — Z is UTC time. Dates and times shall be recorded in UTC. | | {DATEFORMAT} | ISO 8601 date format | Dates shall be formatted in the following format: YYYY-MM-DD. | | {DECIMAL-n/m} | Decimal number of up to n digits in total of which up to m digits can be fraction digits | Numerical field for both positive and negative values. — decimal separator is ‘.’ (full stop), — negative numbers are prefixed with ‘-’ (minus); Values are rounded and not truncated. | | {DTI} | 9 alphanumerical characters | Digital Token Identifier as defined in ISO 24165 standard | | {FFG DTI} | 9 alphanumerical characters | Code to identify a group of equivalent Digital Token Identifiers as defined in ISO 24165 standard type 3 | | {INTEGER-n} | Integer number of up to n digits in total | Numerical field for both positive and negative integer values. | | {LEI} | 20 alphanumerical characters | Legal entity identifier as defined in ISO 17442 | | {MIC} | 4 alphanumerical characters | Market identifier as defined in ISO 10383 | | Number | Field | Content | Form and standards | | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | | 1 | Type of crypto-asset white paper | The type of crypto-asset white paper notified. Where the crypto-asset white paper concerns asset-referenced tokens, the code ‘ARTW’ shall be used. Where the crypto-asset white paper concerns e-money tokens, the code ‘EMTW’ shall be used. Where the crypto-asset white paper concerns crypto-assets other than asset-referenced tokens and e-money tokens the code ‘OTHR’ shall be used. | Choice from list of predefined values: ‘ARTW’ ‘EMTW’ ‘OTHR’ | | 2 | Name of the issuer | Name of the issuer | Free alphanumerical text | | 3 | Legal form of the issuer | Legal form | ISO standard 20275 ‘Financial Services – Entity Legal Forms (ELF)’ | | 4 | Legal entity identifier of the issuer, where available | Legal entity identifier of the issuer, where available | {LEI} | | 5 | Other identifier of the issuer required pursuant to applicable national law, where available | Other identifier of the issuer required pursuant to applicable national law, where available | Free alphanumerical text | | 6 | Legal entity identifier of the entity that drew up the crypto-asset white paper, where available | Legal entity identifier of the entity that drew up the crypto-asset white paper, where available | {LEI} | | 7 | Other identifier of the entity that drew up the crypto-asset white paper required pursuant to applicable national law, where available | Other identifier of the entity that drew up the crypto-asset white paper required pursuant to applicable national law | Free alphanumerical text | | 8 | Identifier of operator of the trading platform | Segment market identifier code (MIC) for the trading platform operated by the crypto-asset service provider (CASP), where available, otherwise operating MIC | {MIC} | | 9 | Commercial name or trading name of the issuer, where available | Commercial name or trading name of the issuer, where available | Free alphanumerical text | | 10 | Physical address of the issuer | Physical address of the issuer | Free alphanumerical text | | 11 | Telephone number of the issuer, where available | Telephone number of the issuer, where available | Free alphanumerical text | | 12 | Email of the issuer, where available | Email of the issuer, where available | Free alphanumerical text | | 13 | Website of the issuer | Website of the issuer | Free alphanumerical text | | 14 | Home Member State | Home Member State as defined in [Article 3](/mica/title-i-subject-matter-scope-and-definitions-art.-1-3/article-3.md), point (33), of Regulation (EU) 2023/1114 | Closed list of EU Member States | | 15 | Host Member States | Host Member State as defined in [Article 3](/mica/title-i-subject-matter-scope-and-definitions-art.-1-3/article-3.md), point (34), of Regulation (EU) 2023/1114. | Closed list of EU Member States | | 16 | Starting date of offer to the public or admission to trading | Starting date or, if not available at the time of the notification by the competent authority, the intended starting date of offer to the public or admission to trading | YYYY-MM-DD | | 17 | Any other services provided by the issuer | Any other services provided by the issuer not covered by Regulation (EU) 2023/1114, with a reference to the applicable Union or national legal acts regulating that service, where applicable | Free alphanumerical text | | 18 | The date of authorisation, where applicable | The date of authorisation by the competent authority, where applicable | YYYY-MM-DD | | 19 | The date of withdrawal of authorisation, where applicable | The date of withdrawal of authorisation by the competent authority, where applicable | YYYY-MM-DD | | 20 | Publication date | Effective or intended publication date of the crypto-asset white paper or of the modified crypto-asset white paper, as applicable | YYYY-MM-DD | | 21 | Date and time of notification | Date and time of the latest notification of the white paper to the competent authority | YYYY-MM-DD Thh:mm:ss.ddddddZ. | | 22 | Language or languages of the crypto-asset white paper | Language or languages in which the crypto-asset white paper is drafted. Where multiple languages have been used, this field shall be reported as many times as necessary | Closed list of EU languages | | 23 | Record identifier | Unique identifier of the uploaded record, assigned by the sending competent authority | {ALPHANUM-500} | | 24 | Data file reference | Reference code needed to link the data file with corresponding metadata file | {ALPHANUM-500} | | 25 | The type of submission | Type of submission | NEWT = New MODI = Modify EROR = Error CORR = Correction | | 26 | Version | Version of the dataset (data and metadata) | {INTEGER-50} | | 27 | Digital Token Identifier used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available | Code used to uniquely identify the crypto-asset or each of the several crypto assets to which the crypto-asset white paper relates, where available | ISO 24165 Digital Token Identifier {DTI} | | 28 | Functionally Fungible Group Digital Token Identifier, where available | Code used to uniquely identify the functionally fungible group to which the digital asset belongs (i.e. common to each of the several assets to which the crypto-asset white paper relates), i.e. code used to identify the white paper ISO 24165 DTI of type = 3 (i.e. functionally fungible group), where available | ISO 24165 \[FFG DTI] | | 29 | Personal data flag | Flag indicating if the submitted crypto-asset white paper contains personal data | ‘true’ – Yes ‘false’ – No | ### Related * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/dora/crypto-asset-service-provider.md) — defined term used on this page * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service-provider.md) — defined term used on this page * [crypto-asset service provider](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/crypto-asset-service-provider.md) — defined term used on this page * [legal entity identifier](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/tofr/legal-entity-identifier.md) — defined term used on this page * [crypto-asset service](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/crypto-asset-service.md) — defined term used on this page * [competent authority](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/competent-authority.md) — defined term used on this page * [offer to the public](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/offer-to-the-public.md) — defined term used on this page * [home Member State](https://github.com/jakesenfti/micawtf/blob/main/spaces/definitions/mica/home-member-state.md) — defined term used on this page --- # 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/eu-level/technical-standards/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable.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.