{"release":{"id":"a4f2a0495fe55b47323883f82977a9b34ab66171ec9623e39925d3a7045b6c81","published":"2026-11-01T16:41:30Z","pinned":false},"limits":{"coverage":{"history":"current_only","held_since":"2026-10-26","gaps":[],"covered":["2025/421 — RTS — White Paper Classification [in force] L2"],"not_covered":["national guidance","court decisions"]},"freshness":{"release_id":"a4f2a0495fe55b47323883f82977a9b34ab66171ec9623e39925d3a7045b6c81","release_published":"2026-11-01T16:41:30Z","checked_at":"2026-10-26","checked_against":"EUR-Lex"},"truncation":null,"failures":[],"incomplete":[]},"page":{"path":"/mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable/annexes/annex","url":"https://www.headlesslaw.com/mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable/annexes/annex","title":"ANNEX — Data necessary for the classification of crypto-asset white papers in the register referred to in [Article 109](../../articles/109.md) of Regulation (EU) 2023/1114","family":"l2_unit_view","work_id":"mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable","view_of":"/mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable","status":"in_force","force_status":"in_force","date_state":"current","requested_date":null,"as_of":"2026-11-02","applies_from":null,"application":null,"version_label":"Commission Delegated Regulation (EU) 2025/421, OJ L, 2025/421, 24.3.2025","check":{"against":"EUR-Lex","on":"2026-10-26"},"check_result":"matched","official_url":"https://eur-lex.europa.eu/eli/reg_del/2025/421/oj/eng","valid_from":"0001-01-01","valid_until":null,"content_id":"2616dd1e85cd03c5","versions":["0001-01-01"],"version_url":"https://www.headlesslaw.com/mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable/annexes/annex/versions/2026-10-26","revision_url":"https://www.headlesslaw.com/mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable/annexes/annex/versions/2026-10-26/rev/2616dd1e85cd03c5","versions_url":"https://www.headlesslaw.com/mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable/annexes/annex/versions","relations_url":"https://www.headlesslaw.com/mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable/annexes/annex/relations","act_url":"https://www.headlesslaw.com/mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable#annex","source_line":"Commission Delegated Regulation (EU) 2025/421 · binding · OJ L, 2025/421, 24.3.2025 · dated 16 Dec 2024 [in force]","attribution":{"prepared_by":"European Commission","published_by":"Publications Office of the EU","published_in":"Official Journal of the European Union","document_type":"delegated_regulation","legal_nature":"binding_adopted","addressees":"not stated in the document","dates":{"document_date":"2024-12-16","published_on":"2025-03-24","entry_into_force":"2025-04-13","locators":{"document_date":"CELLAR 32025R0421 work_date_document","published_on":"CELLAR 32025R0421 official-journal-act_date_publication","entry_into_force":"CELLAR 32025R0421 resource_legal_date_entry-into-force (earliest)"}},"adoption":null},"context":{"act":{"work_id":"mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable","path":"/mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable","name":"Commission Delegated Regulation (EU) 2025/421","number":"2025/421","celex":"32025R0421","title_official":"COMMISSION DELEGATED REGULATION (EU) 2025/421 of 16 December 2024 supplementing Regulation (EU) 2023/1114 of the European Parliament and of the Council with regard to regulatory technical standards specifying the data necessary for the classification of crypto-asset white papers and the practical arrangements to ensure that such data is machine-readable (Text with EEA relevance)","document_date":"2024-12-16"},"position":{"kind":"annex","key":"annex","index":1,"articles":4,"annexes":1},"prev":{"path":"/mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable/articles/4","key":"4","title":"Article 4 — Entry into force and application"},"next":null,"act_anchor":"#annex"}},"provenance":{"official_url":"https://eur-lex.europa.eu/eli/reg_del/2025/421/oj/eng","check":{"result":"matched","checked_at":"2026-10-26","against":"EUR-Lex"},"repo_path":"mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable.md","unit_text_sha256":"937433d377cc99dd251685ecbc6a3bdffb22496b9395794b977ef64bb52d908e","note":"the unit is a byte-exact part of the act page, whose check record covers it"},"unit":{"locator":"mica/level-2/rts/regulatory-technical-standards-data-classification-white-papers-machine-readable/annex","kind":"annex","key":"annex","heading":"ANNEX — Data necessary for the classification of crypto-asset white papers in the register referred to in [Article 109](../../articles/109.md) of Regulation (EU) 2023/1114","text":"### ANNEX — Data necessary for the classification of crypto-asset white papers in the register referred to in [Article 109](../../articles/109.md) of Regulation (EU) 2023/1114\n\n#### Legend\n\n| SYMBOL | DATA TYPE | DEFINITION |\n| -------------------- | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| {ALPHANUM-n} | Up to n alphanumerical characters | Free text field. |\n| {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. |\n| {DATEFORMAT} | ISO 8601 date format | Dates shall be formatted in the following format: YYYY-MM-DD. |\n| {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. |\n| {DTI} | 9 alphanumerical characters | Digital Token Identifier as defined in ISO 24165 standard |\n| {FFG DTI} | 9 alphanumerical characters | Code to identify a group of equivalent Digital Token Identifiers as defined in ISO 24165 standard type 3 |\n| {INTEGER-n} | Integer number of up to n digits in total | Numerical field for both positive and negative integer values. |\n| {LEI} | 20 alphanumerical characters | Legal entity identifier as defined in ISO 17442 |\n| {MIC} | 4 alphanumerical characters | Market identifier as defined in ISO 10383 |\n\n| Number | Field | Content | Form and standards |\n| ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |\n| 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’ |\n| 2 | Name of the issuer | Name of the issuer | Free alphanumerical text |\n| 3 | Legal form of the issuer | Legal form | ISO standard 20275 ‘Financial Services – Entity Legal Forms (ELF)’ |\n| 4 | Legal entity identifier of the issuer, where available | Legal entity identifier of the issuer, where available | {LEI} |\n| 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 |\n| 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} |\n| 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 |\n| 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} |\n| 9 | Commercial name or trading name of the issuer, where available | Commercial name or trading name of the issuer, where available | Free alphanumerical text |\n| 10 | Physical address of the issuer | Physical address of the issuer | Free alphanumerical text |\n| 11 | Telephone number of the issuer, where available | Telephone number of the issuer, where available | Free alphanumerical text |\n| 12 | Email of the issuer, where available | Email of the issuer, where available | Free alphanumerical text |\n| 13 | Website of the issuer | Website of the issuer | Free alphanumerical text |\n| 14 | Home Member State | Home Member State as defined in [Article 3](../../articles/3.md), point (33), of Regulation (EU) 2023/1114 | Closed list of EU Member States |\n| 15 | Host Member States | Host Member State as defined in [Article 3](../../articles/3.md), point (34), of Regulation (EU) 2023/1114. | Closed list of EU Member States |\n| 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 |\n| 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 |\n| 18 | The date of authorisation, where applicable | The date of authorisation by the competent authority, where applicable | YYYY-MM-DD |\n| 19 | The date of withdrawal of authorisation, where applicable | The date of withdrawal of authorisation by the competent authority, where applicable | YYYY-MM-DD |\n| 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 |\n| 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. |\n| 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 |\n| 23 | Record identifier | Unique identifier of the uploaded record, assigned by the sending competent authority | {ALPHANUM-500} |\n| 24 | Data file reference | Reference code needed to link the data file with corresponding metadata file | {ALPHANUM-500} |\n| 25 | The type of submission | Type of submission | NEWT = New MODI = Modify EROR = Error CORR = Correction |\n| 26 | Version | Version of the dataset (data and metadata) | {INTEGER-50} |\n| 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} |\n| 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] |\n| 29 | Personal data flag | Flag indicating if the submitted crypto-asset white paper contains personal data | ‘true’ – Yes ‘false’ – No |\n\n","marks":[],"text_hash":"937433d377cc99dd251685ecbc6a3bdffb22496b9395794b977ef64bb52d908e","revision":1}}