Commission Delegated Regulation (EU) 2025/421 of 16 December 2024 supplementing Regulation (EU) 2023/1114
as it stood on 2026-08-07, permalink: /eu-eurlex/32025r0421/2026-08-07
Article 1
The data necessary for the classification of crypto-asset white papers is set out the Annex.
The data set out in the Annex shall be provided in a common format in accordance with the ISO 20022 standard.
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, Article 19 or Article 51 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
When using the ISO 17442 Legal Entity Identifier, persons drawing up a crypto-asset white paper referred to in Articles 6, Article 19 or Article 51 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
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.
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.
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
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.
Provenance and validity dates, identifier, hash
| as of | 2026-08-07 → this version applied |
| valid | 2024-12-16 → open publisher-asserted |
| type | REG_DEL 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 |
| language | en |
| published | 2024-12-16 |
| lex_id | eu-eurlex:32025r0421:2024-12-16 |
| record sha256 | b919c34abb7c32563a95c2a6998d9d48bb467c6f8c9c66db00d6d5423b0d03e5 |
New here? What am I looking at?
This is a consolidated text: the original law with every later amendment merged in, as the official publisher produced it for a given date. Laws are amended constantly, so “the law” has no single text, only a text per date. That date is the banner above.
It has no legal force. Only the version published in the official gazette (Mémorial / Official Journal) is authentic, the publishers say so themselves, and so do we. Lex reproduces their text without altering a byte, and links the source on every page. This is legal information, never legal advice: it reports what the text said, never what it means for your situation.
“Valid from → to” = the window in which this text applied. “Open” = still current as far as the publisher has consolidated. Each article carries its own hash so you can prove it was not tampered with , here is how.
timeline next version (2024-12-16) →
| tier | A, publisher-supplied validity dates |
| history begins | publisher |
| index built | 2026-08-07T19:46:23Z · corpus 8d5e859 |
| stamp signature | valid (ECDSA-P256) |