This document is an excerpt from the EUR-Lex website
Document 32025R1140
Commission Delegated Regulation (EU) 2025/1140 of 27 February 2025 supplementing Regulation (EU) 2023/1114 of the European Parliament and of the Council with regard to regulatory technical standards specifying records to be kept of all crypto-asset services, activities, orders and transactions undertaken
Commission Delegated Regulation (EU) 2025/1140 of 27 February 2025 supplementing Regulation (EU) 2023/1114 of the European Parliament and of the Council with regard to regulatory technical standards specifying records to be kept of all crypto-asset services, activities, orders and transactions undertaken
Commission Delegated Regulation (EU) 2025/1140 of 27 February 2025 supplementing Regulation (EU) 2023/1114 of the European Parliament and of the Council with regard to regulatory technical standards specifying records to be kept of all crypto-asset services, activities, orders and transactions undertaken
C/2025/1206
OJ L, 2025/1140, 10.6.2025, ELI: http://data.europa.eu/eli/reg_del/2025/1140/oj (BG, ES, CS, DA, DE, ET, EL, EN, FR, GA, HR, IT, LV, LT, HU, MT, NL, PL, PT, RO, SK, SL, FI, SV)
Date of entry into force unknown (pending notification) or not yet in force., Date of effect: 30/06/2025
|
Official Journal |
EN L series |
|
2025/1140 |
10.6.2025 |
COMMISSION DELEGATED REGULATION (EU) 2025/1140
of 27 February 2025
supplementing Regulation (EU) 2023/1114 of the European Parliament and of the Council with regard to regulatory technical standards specifying records to be kept of all crypto-asset services, activities, orders and transactions undertaken
(Text with EEA relevance)
THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Regulation (EU) 2023/1114 of the European Parliament and of the Council of 31 May 2023 on markets in crypto-assets, and amending Regulations (EU) No 1093/2010 and (EU) No 1095/2010 and Directives 2013/36/EU and (EU) 2019/1937 (1), and in particular Article 68(10), third subparagraph, thereof,
Whereas:
|
(1) |
The records crypto-asset service providers are required to keep should be adapted to their type of business and the range of crypto-asset services, activities, orders, and transactions they undertake. |
|
(2) |
Crypto-asset service providers should be free to determine the manner in which they keep records of relevant data relating to all orders and transactions in crypto-assets. However, consistent and comparable records on services, activities, orders and transactions are essential for competent authorities to fulfil their supervisory tasks and to take enforcement measures. In particular, competent authorities should be able to perform the same analysis on all record datasets, regardless of which crypto-asset service provider produced the record. Crypto-asset service providers should therefore provide consistent details of the records on services, activities, orders and transactions by using uniform standards where a competent authority requests such information pursuant to Article 94 of Regulation (EU) 2023/1114. For the same reasons, it is necessary to specify that the records should be maintained in a medium allowing effective supervision by competent authorities. |
|
(3) |
In order to leverage from the knowledge and application of Regulation (EU) No 600/2014 of the European Parliament and of the Council (2), to ensure consistent reporting standards across financial sector and to minimise the reporting burden for crypto-asset service providers, data should be recorded in accordance with the standards referred to in that Regulation. In order to ensure consistency between this Delegated Regulation and Commission Delegated Regulation (EU) 2025/416 (3), the same standards should apply when the records are also required in accordance with that Delegated Regulation. |
|
(4) |
To ensure that competent authorities can properly supervise services provided by crypto-asset service providers, it is necessary that crypto-asset service providers keep a record of the policy arrangements and procedures put in place to comply with Regulation (EU) 2023/1114. |
|
(5) |
Market abuse, including market manipulation, may be carried out through various means, including through algorithmic trading. Therefore, in order to ensure effective market surveillance, where investment decisions are made by a person other than the client or by a computer algorithm, that person or algorithm should be identified in the order and transaction records using unique, robust and consistent identifiers. For the same reasons, it is important to lay down that where more than one person in a crypto-asset service provider makes the investment decision, the person with primary responsibility for the decision is to be identified in the record. |
|
(6) |
To ensure unique, consistent and robust identification of natural persons in order and transaction records, those natural persons should be identified by a concatenation of the country of their nationality followed by identifiers assigned by the country of nationality of those persons. Where those identifiers are not available, natural persons should be identified by identifiers created from a concatenation of their date of birth and name. |
|
(7) |
It is necessary that certain personal data are recorded by crypto-asset service providers to identify their clients or other natural persons relevant for orders or transactions in crypto-assets, as these data are fundamental to ensure efficient supervision by competent authorities, including in the area of market abuse. For all instances of identifying natural persons, this is to be done by following the level of prioritization of the different identifiers detailed in Annex II of Commission Delegated Regulation (EU) 2017/590 (4). |
|
(8) |
It is possible that natural persons who need to be identified for recordkeeping purposes are residents of a country other than the one of their nationality. The country of residence of natural persons can affect several obligations under Regulation (EU) 2023/1114, and is therefore an important data element for ensuring effective supervision by competent authorities. Whenever their country of residence is different from that person’s nationality, this should be indicated by providing the country code of the country of residence of that natural person. |
|
(9) |
To facilitate market surveillance and to allow for the comparability of the records to be kept by crypto-asset service providers, clients of crypto-asset service providers that are legal entities should be identified with a code that is compatible with the internationally established criteria for the development of robust identification systems for the monitoring of financial markets. Such code should be unique, neutral, reliable, open source, scalable, accessible, available for free or at a reasonable cost, and subject to an appropriate governance framework. These criteria were also used by the competent authorities for assessing the most appropriate identifiers in previous technical standards on supervisory data (5) (6), to ensure consistency and comparability of data on financial transactions, and therefore should also be applicable in the context of this Regulation. |
|
(10) |
LEI is a widely recognised, financially and operationally accessible international identifier used in financial markets. LEI is an international identifier that ensures access to the underlying data at all times, allowing for comparability and aggregation of information at Union level, improving the quality and timeliness of aggregated data and reducing the reporting burden for crypto-asset service providers. Therefore, crypto-asset services providers should, where available, record the LEI of clients that are legal persons on whose behalf they carry out orders and execute transactions. However, there are other legal entity identifiers that may be appropriate for use in the context of this Regulation. Directive (EU) 2017/1132 of the European Parliament and of the Council (7) requires companies subject to that Directive to have a European Unique identifier (‘EUID’), which unequivocally identifies companies and as such is an appropriate tool for the identification of entities in the EU. Within a period of 18 months after the entry into force of this Regulation, the Commission and ESMA will work closely to facilitate the use of EUID as a tool to identify clients that are legal entities for the purpose of this Regulation. Following the completion of this work, the Commission should assess the readiness to use EUID for the purposes of Article 14. Additionally, to ensure openness to other identifiers which may be fit for supervisory purposes and support the integrity of the market, this Regulation sets out criteria that should be met by those alternative identifiers. To enable the market to use such eligible alternative identifiers, ESMA should approve their use where they meet the criteria set out in this Regulation. |
|
(11) |
A unique method for the identification and classification of parties compliant with the above-mentioned criteria and instruments that follow these principles directly supports efforts to achieve data-driven market monitoring by competent authorities. |
|
(12) |
Manual or algorithmic abusive behaviours can also occur when a crypto-asset service provider determines the trading platform for crypto-asset to access or the crypto-asset service provider to which the orders are to be transmitted or any other conditions related to the execution of the order. Therefore, to ensure effective market surveillance, a person or computer algorithm within the crypto-asset service provider performing such activities should be identified in the order and transaction records. For the same reasons, where both a person and computer algorithm are involved, or more than one person or algorithm is involved, the crypto-asset service provider should determine, on a consistent basis following predetermined criteria, which person or algorithm is primarily responsible for those activities. |
|
(13) |
To ensure that competent authorities have access to information that is relevant, accurate and complete, the details relating to the order to be transmitted between crypto asset service providers should be specified. |
|
(14) |
Given the cross-border nature of crypto assets trading, in order to avoid data gaps where a crypto-asset service provider transmits orders or executes transactions via an entity to which Regulation (EU) 2023/1114 does not apply, the crypto-asset service provider should record the transmission of those orders or the execution of those transactions as if it had transmitted those orders or executed those transactions itself. Such information may be of particular importance for the performance of adequate market monitoring and market abuse supervision by the competent authority. |
|
(15) |
To properly monitor the integrity and stability of the markets in crypto-assets, competent authorities need reliable, consistent and standardised information on the crypto-assets that are traded. Such information should enable them to identify the individual crypto-asset being traded according to internationally established principles. In addition, competent authorities should be able to retrieve the main characteristics of the crypto-assets traded, including their technology-specific features. Crypto-asset service providers should therefore use an internationally agreed digital token identifier to identify crypto-assets in the order and transactions records that they provide to competent authorities. The Digital Token Identifier (DTI) managed by the Digital Token Identifier Foundation is an internationally agreed identifier that guarantees reliable, consistent, standardised and available information and allows for comparability and aggregation of information at the level of the European Union, improving the quality and timeliness of aggregated data and reducing the reporting burden for crypto-asset service providers. Therefore, crypto-asset service providers should be able to use the DTI to identify crypto-assets. However, to ensure openness to other token identifiers which may be fit for supervisory purposes and support the integrity of the market, it is necessary to lay down criteria that should be met by those alternative identifiers. To enable the market to use eligible alternative identifiers, ESMA should approve their use where they meet the criteria set out in this Regulation. |
|
(16) |
To be able to properly monitor the integrity and stability of the markets in crypto-assets, competent authorities need reliable, consistent and standardised information on the crypto-assets that are traded. Such information should enable them to classify the individual crypto-asset being traded according to internationally established principles. Such classification should also enable authorities to connect data on white papers with data on transactions and orders in the same crypto asset. The ISO code for the Classification of Financial Instruments (CFI) is an international standard used for classifying financial instruments. However, crypto-assets that are not financial instruments cannot currently be described using the CFI code. The ISO CFI is being revised to accommodate the classification of crypto-assets, but this revision will not be finalized before the application of this Regulation. Therefore, until such revision is completed, an interim classification indicating the type of crypto-assets (crypto-assets other than asset-referenced tokens and e-money tokens, asset-referenced tokens, and e-money tokens) should be used. |
|
(17) |
To ensure efficient and effective market monitoring by competent authorities, transaction records should reflect whether the transaction was executed wholly or partly through a branch of the crypto-asset service provider located in another Member State or in a third country. The inclusion of data detailing the activity of each branch in the records kept by the crypto-asset service providers, should not lead to a disproportionate administrative burden for the crypto-asset service provider, but would enable competent authorities to supervise the services provided by crypto-asset service providers more efficiently and to enhance the visibility on how those services are provided within the different Member States. |
|
(18) |
In line with the principle of data minimisation, crypto-asset service providers should only keep information that is necessary and sufficient to enable competent authorities to carry out a comprehensive assessment of the crypto-asset service provider’s compliance with the relevant requirements of Regulation (EU) 2023/1114 and with that Regulation’s provisions on market abuse. When processing personal data included in the records, crypto-asset service providers and competent authorities should comply with the relevant provisions of Regulation (EU) 2016/679 of the European Parliament and of the Council (8). |
|
(19) |
In order to ensure certain and efficient identification of crypto-asset service providers responsible for executing orders or transactions, those providers should ensure that they are identified in the records maintained pursuant to their record-keeping obligations using validated, issued, and duly renewed legal entity identifiers (LEIs). Pursuant to Article 62 in Regulation (EU) 2023/1114, crypto-asset service providers are required to obtain a legal entity identifier in order to be authorised. Furthermore, to enable the competent authorities to fulfil their supervisory tasks and take enforcement measures in accordance with Article 68(10) of Regulation (EU) 2023/1114, such identifier should be verified, up-to-date and included in the records to be maintained in accordance with this Regulation. |
|
(20) |
The European Data Protection Supervisor was consulted in accordance with Article 42(1) of Regulation (EU) 2018/1725 of the European Parliament and of the Council (9) and delivered an opinion on 28 August 2024. |
|
(21) |
This Regulation is based on the draft regulatory technical standards submitted to the Commission by the European Securities and Markets Authority (‘ESMA’). |
|
(22) |
ESMA has conducted open public consultations on the draft regulatory technical standards upon which this Regulation is based, analysed the potential related costs and benefits and requested the advice of the Securities and Markets Stakeholder Group established in accordance with Article 37 of Regulation (EU) No 1095/2010 of the European Parliament and of the Council (10), |
HAS ADOPTED THIS REGULATION:
SECTION 1
Retention of records and general provision on records
Article 1
Definitions
For the purposes of this Regulation, the following definitions shall apply:
|
(1) |
‘transaction’ means the conclusion of an acquisition or disposal of crypto-assets other than the crypto-assets referred to in Article 2(3) and (4) of Regulation (EU) 2023/1114; |
|
(2) |
‘undertaking a transaction’ means executing a transaction or transmitting an order for crypto-assets on behalf of a client; |
|
(3) |
‘executing a transaction’ means providing any of the following services or performing any of the following activities that result in a transaction:
|
Article 2
Retention of records
1. The records shall be retained in a medium that allows the storage of information in a way accessible for future reference by the competent authority, in such a form and manner that all of the following conditions are met:
|
(a) |
competent authorities are able to access those records readily and to reconstitute each key stage of the processing of each crypto-asset service, activity, order or transaction; |
|
(b) |
it is possible to easily ascertain any corrections or other amendments to the records, and the contents of the records prior to such corrections or amendments; |
|
(c) |
it is not possible to manipulate or alter the records; |
|
(d) |
it allows for the exploitation of the data by means of an ICT or any other efficient system, where it is not possible to easily analyse the data due to its volume and nature; |
|
(e) |
the crypto-asset service provider's record-keeping arrangements comply with the record keeping requirements under this Regulation irrespective of the technology used. |
2. Crypto-assets service providers shall keep the records listed in Section 1 of the Annex, depending upon the nature of their services and activities.
3. The obligation to keep the records listed in Section 1 of the Annex shall not affect any obligation to keep records set out in any other Union act.
SECTION 2
Record keeping relating to specific crypto-asset services and to activities of crypto-asset service providers
Article 3
Record-keeping of the crypto-asset service provider’s policies and procedures
1. Crypto-asset service providers shall keep records of any policies and procedures they are required to maintain in writing under Regulation (EU) 2023/1114 and its implementing measures.
2. Crypto-asset service providers shall also keep the records of the assessment and periodical review, carried out by their management body, of the effectiveness of the policy arrangements, and procedures referred to in Articles 68(6) of Regulation (EU) 2023/1114, including of any deficiencies identified in relation to such policy arrangements and procedures and of any measures taken to address such deficiencies.
Article 4
Record-keeping of documents setting out the crypto-asset service provider’s and the client’s rights and obligations
1. Crypto-asset service providers shall keep the documents setting out their rights and obligations in relation to their provision of service, as well as those setting out the rights and obligations of their clients for a period of five years from the termination of the agreement to provide services.
2. At the request of a competent authority, made before the expiry of the five-year period referred to in paragraph 1, crypto-asset service providers shall keep the documents referred to in paragraph 1 for a period of up to seven years from the date of termination of the agreement to provide crypto-asset services.
Article 5
Record-keeping in relation to the safekeeping of clients’ crypto-assets and funds
1. Crypto-asset service providers shall keep records enabling them to distinguish, at any time and without delay, crypto-assets and funds held for one client from crypto-assets and funds held for any other client and from their own assets.
2. Crypto-asset service providers shall maintain their records in a way that ensures that they may be used for auditing purposes as records.
3. Such records shall include the following:
|
(a) |
records that readily identify the balances of crypto-assets and funds held for each client; |
|
(b) |
where clients’ funds are held by crypto-asset service providers in accordance with Article 70(2) and (3) of Regulation (EU) 2023/1114, details of the accounts in which those funds are held and the relevant agreements between the crypto-assets service provider with the credit institutions or central banks with which the clients’ funds are placed; |
|
(c) |
details of the accounts opened with third parties holding crypto-assets for the crypto-assets service provider and of the outsourcing agreements with those third parties; |
|
(d) |
details of third parties carrying out any tasks outsourced in accordance with Article 73 of Regulation (EU) 2023/1114 and details of the outsourced tasks; |
|
(e) |
names and functions of persons responsible for the safekeeping of clients’ crypto-assets and funds within the crypto-asset service provider; |
|
(f) |
agreements that establish client ownership over crypto-assets and funds. |
SECTION 3
Record-keeping of orders and transactions
Article 6
Record-keeping of orders
1. For every initial order received from a client and for every initial decision to deal taken, crypto-asset service providers shall record and keep the details set out in the second and third columns of Table 2 of Section 2 of the Annex and the details set out in Table 4 of Section 4 of that Annex, to the extent that such details concern the initial orders and those decisions to deal.
2. Where a competent authority requests any of the details referred to in paragraph 1 in accordance with Article 94(1), points (a) or (d), or Article 94(3), point (a), of Regulation (EU) 2023/1114, the crypto-assets service providers shall provide such details as set out in the fourth column of Table 2 of Section 2 of the Annex to this Regulation.
3. Where the details set out in Table 2 of Section 2 of the Annex to this Regulation are also required pursuant to Article 76 of Regulation (EU) 2023/1114 or to Articles 25 and 26 of Regulation (EU) No 600/2014, they shall be maintained according to the standards set out in those Regulations.
Article 7
Record keeping of transactions
1. Crypto-asset service providers shall, immediately after having undertaken a transaction, record the details set out in the second and third columns of Table 3 of Section 3 and Table 4 of Section 4 of the Annex.
2. Where competent authorities request any of the details referred to in paragraph 1 in accordance with Article 94(1), points (a) or (d), or Article 94(3), point (a), of Regulation (EU) 2023/1114, the operators of trading platforms for crypto-assets shall provide such details as set out in the fourth column of Table 3 of Section 3 of the Annex.
Article 8
Identification of person or computer algorithm within the crypto-asset service provider making the investment decision
1. Where a person or computer algorithm within a crypto-asset service provider makes the investment decision to acquire or dispose of a specific crypto-asset on behalf of the crypto-asset service provider or on behalf of a client in accordance with a discretionary mandate given by the client, that person or computer algorithm shall be identified and recorded as specified in Field 41 of Table 3 of Section 3 of the Annex.
2. Where a person and computer algorithm are both involved in taking the investment decision, or more than one person or algorithm are involved in taking that decision, the crypto-asset service provider shall record the person or computer algorithm with primary responsibility for that decision.
Article 9
Designation to identify natural persons
1. A client who is a natural person shall be identified in the crypto-asset service provider’s records using the designation resulting from the concatenation of the ISO 3166-1 alpha-2 (2-letter country code) of the client’s nationality, followed by the national client identifier specified in Annex II to Delegated Regulation (EU) 2017/590, based on the client’s nationality.
2. The national client identifier referred to in paragraph 1 shall be assigned in accordance with the priority levels provided for in Annex II of Delegated Regulation (EU) 2017/590 using the highest priority identifier that a person has, regardless of whether that identifier is already known to the crypto-asset service provider.
3. For the purposes of identifying a natural person, if the person is a national of more than one European Economic Area (EEA) country, the country code of the first nationality when sorted alphabetically by its ISO 3166-1 alpha-2 code and the identifier of that nationality assigned in accordance with paragraph 2 shall be used.
4. Where a natural person has a non-EEA nationality, the highest priority identifier in accordance with the field referring to ‘all other countries’ provided in Annex II of Delegated Regulation (EU) 2017/590 shall be used. Where a natural person has EEA and non-EEA nationality, the country code of the EEA nationality and the highest priority identifier of that nationality assigned in accordance with paragraph 2 shall be used.
5. Where a client is a resident of a country other than the one of its nationality, crypto-asset service providers shall also identify that person based on the country of residence of the person as prescribed in Field 41 of Table 2 in the Annex.
6. Where the identifier assigned in accordance with paragraph 2 is based on CONCAT, the client shall be identified by the crypto-asset service provider using the concatenation of the following elements in the following order:
|
(a) |
the date of birth of the person in the format YYYYMMDD; |
|
(b) |
the five first characters of the first name of the person; |
|
(c) |
the five first characters of the surname of the person. |
7. For the purposes of paragraph 6, prefixes to names shall be excluded and first names and surnames shorter than five characters shall be appended by ‘#’ so as to ensure that references to names and surnames in accordance with paragraph 6 contain five characters. All characters shall be in upper case. No apostrophes, accents, hyphens, punctuation marks or spaces shall be used.
Article 10
Identification of a person or computer algorithm determining conditions for the execution of a transaction
1. Where a person or computer algorithm within the crypto-asset service provider which executes a transaction determines which trading platform for crypto-assets located outside the Union to access, which other crypto-asset service provider to transmit orders to or any conditions related to the execution of a transaction, that employee or computer algorithm shall be identified in Field 41 of Table 3 in Section 3 of the Annex.
2. Where a person within the crypto-asset service provider takes decisions determining the execution of the transaction, the crypto-asset service provider shall assign a designation for identifying that person in its transaction records in accordance with Article 9.
3. Where a computer algorithm operating under the control of the crypto-asset service provider takes decisions determining the execution of the transaction, that computer algorithm shall be identified in Field 43 of the Table in Section 3 of the Annex.
4. Where a person and computer algorithm are both involved in execution of the transaction, or more than one person or algorithm are involved, the crypto-asset service provider shall record the person or computer algorithm primarily responsible for the execution of the transaction in Field 43 of Table 3 in Section 3 of the Annex.
Article 11
Recording of reception and transmission of orders
1. Crypto-asset service providers that receive and transmit to another crypto-asset service provider an order for crypto-assets on behalf of clients as referred to in Article 1(3)(a) shall record the details of such orders as specified in Fields 1, 2, 10, 12, 14, 15, 16, 17, 19, 20, 21, 25, 37 of Table 2 of Section 2 of the Annex, if and to the extent that those fields are relevant for that order.
2. Where the order transmitted was received from a crypto-asset service provider who had previously transmitted that order, the fields provided pursuant to paragraph 1 shall be those identifying the transmitting crypto-asset service provider.
3. Where an order is transmitted more than one time, the order details referred to in paragraph 1 shall be those of the client of the crypto-asset service provider who first transmitted the order and shall be recorded by the crypto-asset service provider who transmitted the order for the first time.
4. Where orders are aggregated for more than one client, the order details referred to in paragraph 1 shall be recorded for each client.
Article 12
Recording of orders and transactions executed via trading platforms or service providers to which Regulation (EU) 2023/1114 does not apply
1. Where a crypto-asset service provider executes an order or a transaction on behalf of a client through a trading platform for crypto-assets or a service provider to which Regulation (EU) 2023/1114 does not apply, the crypto-asset service provider shall record the details of the order or transaction as if it had executed the order or transaction itself.
2. The crypto-asset service provider shall record the information referred to in paragraph 1 in the fields specified in Table 2 of Section 2 and in Table 3 of Section 3 of the Annex, where those fields are applicable to the order or transaction in question.
Article 13
Recording of reception and transmission of orders to entities to which Regulation (EU) 2023/1114 does not apply
1. Where a crypto-asset service provider transmits an order to an entity to which Regulation (EU) 2023/1114 does not apply, the crypto-asset service provider shall record the details of the transmitted order in the fields specified in Table 2 of Section 2 of the Annex, to the extent those fields are applicable to the order or transaction in question.
2. Where the order is aggregated for several clients, the information referred to in Article 9 and 14, as applicable, shall be recorded for each client.
Article 14
Identification of clients that are legal entities
1. When providing to the competent authorities the information referred to in Articles 6 and 7, a crypto-asset service provider shall identify any clients that are legal entities by using a legal entity identifier code corresponding to those clients.
2. Crypto-asset service providers shall record the legal entity identifier codes that comply with the ISO 17442 standard and are included in the Global LEI database maintained by the Central Operating Unit appointed by the Legal Entity Identifier Regulatory Oversight Committee.
3. Where the client does not have a legal entity identifier compliant with the ISO 17442 standard, the crypto asset service provider shall obtain one for the client, or use an identifier defined at Union level which meets all of the following characteristics:
|
(a) |
is unique; |
|
(b) |
is neutral; |
|
(c) |
is reliable; |
|
(d) |
is open source; |
|
(e) |
is scalable; |
|
(f) |
is accessible; |
|
(g) |
is available for free or at a reasonable cost; |
|
(h) |
is subject to an appropriate governance framework. |
Article 15
Identification of crypto-assets
When providing information to competent authorities under Articles 6 and 7, a crypto-asset service provider shall identify the crypto-assets that are the subject of the recorded order or transaction, or used as a means of payment, by using a digital token identifier that is compliant with the ISO 24165 standard or an equivalent unique identifier approved by ESMA at Union level, which meets all of the following characteristics:
|
(a) |
is unique; |
|
(b) |
is neutral; |
|
(c) |
is reliable; |
|
(d) |
is open source; |
|
(e) |
is scalable; |
|
(f) |
is accessible; |
|
(g) |
is available at a reasonable cost basis; and |
|
(h) |
is subject to an appropriate governance framework. |
Article 16
Recording of transactions undertaken by branches
1. Where a crypto-asset service provider undertakes a transaction wholly or partly through its branch, it shall include in its transaction records, the ISO 3166 country code of such branch, in accordance with Fields 7, 16, 34, 42 or 44 of Table 3 in Section 3 of the Annex.
2. The crypto-asset service provider shall include in the transaction records the following information:
|
(a) |
whether the branch received the order from a client or whether the branch made an investment decision for a client in accordance with a discretionary mandate given to it by the client; |
|
(b) |
whether the branch has supervisory responsibility for the person taking the investment decision concerned; |
|
(c) |
whether the branch has supervisory responsibility for the person determining the conditions for execution of the transaction; |
|
(d) |
whether the transaction was fully or partially undertaken on a trading platform for crypto-assets located outside the Union using the branch’s membership of that trading platform for crypto-assets. |
Article 17
Identification of the crypto-asset service provider undertaking orders and transactions
1. Crypto-asset service providers that undertake orders or transactions which trigger the obligation to keep records shall ensure that they are identified in the records to be maintained pursuant to this Regulation with a correct legal entity identifier which complies with the ISO 17442 standard and is included in the Global LEI database maintained by the Central Operating Unit appointed by the Legal Entity Identifier Regulatory Oversight Committee.
2. Crypto-asset service providers shall ensure that the reference data related to their legal entity identifier is renewed in accordance with the terms of any of the accredited Local Operating Units of the Global Legal Entity Identifier System.
Article 18
Entry into force
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 be binding in its entirety and directly applicable in all Member States.
Done at Brussels, 27 February 2025.
For the Commission
The President
Ursula VON DER LEYEN
(1) OJ L 150, 9.6.2023, p. 40, ELI: http://data.europa.eu/eli/reg/2023/1114/oj.
(2) Regulation (EU) No 600/2014 of the European Parliament and of the Council of 15 May 2014 on markets in financial instruments and amending Regulation (EU) No 648/2012 (OJ L 173, 12.6.2014, p. 84, ELI: http://data.europa.eu/eli/reg/2014/600/oj).
(3) Commission Delegated Regulation (EU) 2025/416 of 29 November 2024 supplementing Regulation (EU) 2023/1114 of the European Parliament and of the Council with regard to regulatory technical standards specifying the content and format of order book records for crypto-asset service providers operating a trading platform for crypto-assets (OJ L, 2025/416, 14.3.2025, ELI: http://data.europa.eu/eli/reg_del/2025/416/oj).
(4) Commission Delegated Regulation (EU) 2017/590 of 28 July 2016 supplementing Regulation (EU) No 600/2014 of the European Parliament and of the Council with regard to regulatory technical standards for the reporting of transactions to competent authorities (OJ L 87, 31.3.2017, p. 449, ELI: http://data.europa.eu/eli/reg_del/2017/590/oj).
(5) Commission Implementing Regulation (EU) 2019/363 of 13 December 2018 laying down implementing technical standards with regard to the format and frequency of reports on the details of securities financing transactions (SFTs) to trade repositories in accordance with Regulation (EU) 2015/2365 of the European Parliament and of the Council and amending Commission Implementing Regulation (EU) No 1247/2012 with regard to the use of reporting codes in the reporting of derivative contracts (OJ L 81, 22.3.2019, p. 85, ELI: http://data.europa.eu/eli/reg_impl/2019/363/oj).
(6) Commission Implementing Regulation (EU) No 1247/2012 of 19 December 2012 laying down implementing technical standards with regard to the format and frequency of trade reports to trade repositories according to Regulation (EU) No 648/2012 of the European Parliament and of the Council on OTC derivatives, central counterparties and trade repositories (OJ L 352, 21.12.2012, p. 20, ELI: http://data.europa.eu/eli/reg_impl/2012/1247/oj).
(7) Directive (EU) 2017/1132 of the European Parliament and of the Council of 14 June 2017 relating to certain aspects of company law (OJ L 169, 30.6.2017, p. 46, ELI: http://data.europa.eu/eli/dir/2017/1132/oj).
(8) Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (OJ L 119, 4.5.2016, p. 1, ELI: http://data.europa.eu/eli/reg/2016/679/oj).
(9) Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No 1247/2002/EC (OJ L 295, 21.11.2018, p. 39, ELI: http://data.europa.eu/eli/reg/2018/1725/oj).
(10) Regulation (EU) No 1095/2010 of the European Parliament and of the Council of 24 November 2010 establishing a European Supervisory Authority (European Securities and Markets Authority), amending Decision No 716/2009/EC and repealing Commission Decision 2009/77/EC (OJ L 331, 15.12.2010, p. 84, ELI: http://data.europa.eu/eli/reg/2010/1095/oj).
ANNEX
SECTION 1
Records of services and activities: list of records to be kept by crypto-asset service providers according to the nature of their services and activities
|
Type of record |
Summary of content |
||||||||||||||||||
|
Communication with clients |
|||||||||||||||||||
|
Marketing communications |
Each marketing communication issued by the crypto-asset service provider (except in oral form) or on its behalf. |
||||||||||||||||||
|
Information to clients |
Information other than marketing communication provided by the crypto-asset service provider, or on its behalf, to the client about the crypto-asset service provider, its services and activities, crypto-assets, and the applicable costs and related charges. |
||||||||||||||||||
|
Records of communication with clients |
Records of telephone conversations or electronic communications relating to transactions or to the reception, transmission and execution of client orders, including where such conversations or communications do not result in the conclusion of a transaction or in the provision of the services of reception and transmission of orders or execution of order. |
||||||||||||||||||
|
Rights and obligations of the crypto-asset service provider and the client |
|||||||||||||||||||
|
Client agreements |
Any document agreed between the crypto-asset service provider and the client that set out the rights and obligations of the parties. |
||||||||||||||||||
|
Consent of the client |
Any communication between the crypto-asset service provider and the client or any document evidencing that the client consented to the provision of services and to the terms upon which the crypto-asset service provider will provide such services to the client. |
||||||||||||||||||
|
Market abuse |
|||||||||||||||||||
|
Market abuse |
Records of instances where circumstances indicate that market abuse has been committed, is being committed, or is likely to be committed. Such records shall contain the identification of the persons or computer algorithms involved. For persons professionally arranging or executing transactions in crypto-assets, the records shall contain the information documenting the analysis carried out with regard to orders, transactions, and aspects of the functioning of distributed ledger technology that could constitute market abuse, referred to in Article 3 of Commission Delegated Regulation establishing technical standards adopted pursuant to Article 92(2) of Regulation (EU) 2023/1114). |
||||||||||||||||||
|
Safekeeping of clients’ crypto-assets and funds |
|||||||||||||||||||
|
Clients’ crypto-assets and means of access to crypto-assets held by the crypto-asset service provider |
The records enabling the crypto-asset service provider to safeguard the ownership rights of clients and to prevent the use of clients’ crypto-assets for their own account, as required by Article 70(1) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Clients’ funds held by a crypto-asset service provider |
The records enabling the crypto-asset service provider to safeguard the ownership rights of clients and to prevent the use of clients’ funds for their own account as required by Article 70(2) of Regulation (EU) 2023/1114. Any document, records, or evidence demonstrating that the crypto-asset service provider complies with its obligations under Article 70(3) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Complaints handling |
|||||||||||||||||||
|
Complaints |
The records kept in accordance with Article 1(2)(f) of Commission Delegated Regulation (EU) 2025/294 (1). |
||||||||||||||||||
|
Conflicts of interest and personal transactions |
|||||||||||||||||||
|
Conflicts of interest |
The information referred to in Article 6(5) of Commission Delegated Regulation establishing technical standards adopted pursuant to Article 72(5) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Personal transaction |
The records of a personal transaction as referred to in Article 2(4) of Commission Delegated Regulation establishing technical standards adopted pursuant to Article 72(5) of Regulation (EU) 2023/1114, specifying the date and time of the transaction, the conditions, its volume, the counterparty and any authorisation or prohibition in connection with that transaction, in accordance with that Delegated Regulation. |
||||||||||||||||||
|
Outsourcing |
|||||||||||||||||||
|
Outsourcing agreements |
Records of the written agreements referred to in Article 73(3) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Outsourced services and activities |
Records of any service or activity outsourced to a third party together, including:
|
||||||||||||||||||
|
Custody and administration of crypto-assets on behalf of clients |
|||||||||||||||||||
|
Register of positions |
Records of the registers of positions referred to in Article 75(2) and (4) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Statement of positions |
Records of the statement of positions referred to in Article 75(5) of Regulation 2023/1114. |
||||||||||||||||||
|
Communications with clients |
Records of any communication with the client referred to in Article 75(5), second subparagraph, of Regulation 2023/1114, including the response received by the client or lack thereof. |
||||||||||||||||||
|
Use of other crypto-asset service providers |
Where clients’ crypto-assets or means of access to crypto-assets are in custody or controlled in accordance with Article 75(9) of Regulation (EU) 2023/1114:
|
||||||||||||||||||
|
Operation of a trading platform for crypto-assets |
|||||||||||||||||||
|
Operating rules |
A copy of the operating rules referred to in Article 76(1) of Regulation (EU) 2023/1114, including deficiencies detected and the measures taken to remedy them. |
||||||||||||||||||
|
Assessment of suitability of the crypto-asset |
Records of the assessment referred to in Article 76(2) of Regulation (EU) 2023/1114 and its outcome. |
||||||||||||||||||
|
In-built anonymisation function |
Records of cases where crypto-assets have an in-built anonymisation function. |
||||||||||||||||||
|
Consent of the client to matched principal trading |
Records of clients’ consent to the crypto-asset service provider engaging in matched principal trading on the platform for crypto-assets that it operates, as referred to in Article 76(6) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Exchange of crypto-assets for funds or other crypto-assets |
|||||||||||||||||||
|
Price and limits |
|
||||||||||||||||||
|
Placing of crypto-assets |
|||||||||||||||||||
|
Information to clients or prospective clients |
Records of the communications referred to in Article 79(1) of Regulation (EU) 2023/1114 and of the consent received from the offeror or person seeking admission to trading or any third party acting on its behalf. |
||||||||||||||||||
|
Placing operations |
Records of any placing operation of the crypto-asset service provider, kept in accordance with the requirement for the crypto-asset service provider to have in place a centralised procedure to identify all its placing operations as provided in Commission Delegated Regulation establishing technical standards adopted pursuant to Article 72(5) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Advice and portfolio management |
|||||||||||||||||||
|
Information to clients |
Records of any communication made in accordance with Article 81(2), (4) and (9) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Assessment of suitability |
Records of all information collected from each client and assessed to conduct the suitability assessment referred to in Article 81(1) of Regulation (EU) 2023/1114, and all internal documents relating to such suitability assessment. Records of clients who did not provide the information required by Article 81(8) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Investment advice |
Records of the time and date on which advice on crypto-assets was rendered, records of the crypto-assets that were recommended, and the suitability report provided to the client in accordance with Article 81(13) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Periodic statement for portfolio management services |
Records of any periodic statement provided to the client in accordance with Article 81(14) of Regulation (EU) 2023/1114. |
||||||||||||||||||
|
Inducements |
|
||||||||||||||||||
|
Transfer services |
|||||||||||||||||||
|
Records to be kept by the crypto-asset service provider of the originator |
Records of:
|
||||||||||||||||||
|
Records to be kept by the crypto-asset service provider of the beneficiary |
Records of:
|
||||||||||||||||||
|
Records to be kept by intermediary crypto-asset service providers |
Records of:
|
||||||||||||||||||
SECTION 2
Records of orders
Table 1
Legend for Table 2 of this Section and for Table 3 of Section 3
|
Symbol |
Data type |
Definition |
||||||||||||||||
|
{ALPHANUM-n} |
Up to n alphanumerical characters |
Free text field |
||||||||||||||||
|
{CFI_CODE} |
6 characters |
ISO 10962 CFI code |
||||||||||||||||
|
{COUNTRYCODE_2} |
2 alphanumerical characters |
2 letter country code, as defined by ISO 3166-1 alpha-2 country code |
||||||||||||||||
|
{CURRENCYCODE_3} |
3 alphanumerical characters |
3 letter currency code, as defined by ISO 4217 currency codes |
||||||||||||||||
|
{DATE_TIME_FORMAT} |
ISO 8601 date and time format |
Date and time in the following format: YYYY-MM-DDThh:mm:ss.ddddddZ.
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.
|
||||||||||||||||
|
{DTI} |
9 alphanumerical characters |
Digital token identifier as defined in ISO 24165 standard |
||||||||||||||||
|
{DTI_SHORT_NAME} |
n alphanumeric characters |
DTI short name as registered according to the ISO 24165-2 data elements for registration of the DTI |
||||||||||||||||
|
{INTEGER-n} |
Integer number of up to n digits in total |
Numerical field for both positive and negative integer values. |
||||||||||||||||
|
{ISIN} |
12 alphanumerical characters |
ISIN code, as defined in ISO 6166 |
||||||||||||||||
|
{LEI} |
20 alphanumerical characters |
Legal entity identifier as defined in ISO 17442 |
||||||||||||||||
|
{MIC} |
4 alphanumerical characters |
Market identifier as defined in ISO 10383 |
||||||||||||||||
|
{NATIONAL_ID} |
35 alphanumerical characters |
The identifier is derived in accordance with Article 9 and Annex II of Delegated Regulation (EU) 2017/590 |
Table 2
Details of orders to be kept
|
Field Number |
Field Name |
Field description |
Details on the order data to be provided to the competent authority |
||
|
Section A – Identification of the relevant parties |
|||||
|
1 |
Client identification code |
Code used to identify the client of the crypto-assets service provider which submitted the order. Where the client is a legal entity, the LEI code of the client or the alternative identifiers referred to in Article 14(3) shall be used. Where the client is not a legal entity, the {NATIONAL_ID} shall be used. In case of pending allocations, the flag PNAL shall be used. This field shall be ‘NOAP’ where the crypto-asset service provider has a direct interest to buy or sell. |
{LEI} {NATIONAL_ID} {ALPHANUM-20} {PNAL} ‘NOAP’ |
||
|
2 |
Investment decision within the CASP |
Code used to identify the person or the algorithm within the crypto assets service provider who is taking the investment decision. Where a natural person within the crypto-asset service provider takes the investment decision the person who is responsible or has primary responsibility for the investment decision shall be identified with the {NATIONAL_ID}. Where an algorithm that automatically determines individual parameters of orders, including initiating the order or determining its timing, price or quantity, took the investment decision, the field shall be populated with a code assigned according to Article 8. This field shall be left blank where the investment decision was not made by a person or algorithm within the crypto asset service provider. |
{NATIONAL_ID} – Natural persons {ALPHANUM-50} – Algorithms |
||
|
3 |
Execution within firm |
Code used to identify the person or algorithm within the crypto-asset service provider determining the conditions for the execution of the transaction resulting from the order. Where a natural person determines the conditions for the execution of the transaction, the person shall be identified by {NATIONAL_ID}. Where an algorithm that automatically determines individual parameters of orders, including initiating the order or determining its timing, price, or quantity, is responsible for the execution of the transaction, this field shall be populated with a code assigned by the crypto asset service provider, in accordance with Article 10. Where more than one person or a combination of persons and algorithms are involved in the execution of the transaction, the crypto asset service provider shall determine the trader or algorithm primarily responsible and populate this field with the identity of that trader or algorithm. |
{NATIONAL_ID} – Natural persons {ALPHANUM-50} – Algorithms |
||
|
Section B – Trading capacity and liquidity provision |
|||||
|
4 |
Trading capacity |
Indicates whether the crypto-asset service provider undertaking the transaction is carrying out matched principal trading or exchanges crypto-assets for funds. Where the order submission does not result from the crypto-asset service provider carrying out matched principal trading or exchanging crypto-assets for funds or other crypto-assets, the field shall indicate that the transaction was carried out under any other capacity. |
‘DEAL’ – Exchange crypto-assets for funds or other crypto-assets ‘MTCH’ – Matched principal ‘AOTC’ – Any other capacity |
||
|
Section C – Date and time |
|||||
|
5 |
Date and Time |
The date and time for each event listed in Section G and J. |
{DATE_TIME_FORMAT} |
||
|
Section D – Validity period and order restrictions |
|||||
|
6 |
Validity period |
Good-For-Day: the order expires at the end of the trading day on which it was entered in the order book. Good-Till-Cancelled: the order will remain active in the order book and be executable until it is actually cancelled. Good-Till-Time: the order expires at the latest at a pre-determined time within the current trading session. Good-Till-Date: the order expires at the end of a specified date. Good-Till-Specified Date and Time: the order expires at a specified date and time. Good After Time: the order is only active after a pre-determined time within the current trading session. Good After Date: the order is only active from the beginning of a pre-determined date. Good After Specified Date and Time: the order is only active from a pre-determined time on a pre-determined date. Immediate-Or-Cancel: an order which is executed upon its entering into the order book (for the quantity that can be executed) and which does not remain in the order book for the remaining quantity (if any) that has not been executed. Fill-Or-Kill: an order which is executed upon its entering into the order book provided that it can be fully filled: in the event the order can only be partially executed, then it is automatically rejected and cannot therefore be executed. Other: any additional indications that are unique for specific business models, trading platforms or systems. |
‘DAVY’ – Good-For-Day ‘GTCV’ – Good-Till-Cancelled ‘GTTV’ – Good-Till-Time ‘GTDV’ – Good-Till-Date ‘GTSV’ – Good-Till-Specified Date and Time ‘GATV’ – Good After Time ‘GADV’ – Good After Date ‘GASV’ – Good After Specified Date and Time ‘IOCV’ – Immediate-Or-Cancel ‘FOKV’ – Fill-Or-Kill or {ALPHANUM-4} character’ not already in use for the trading venue’s own classification. |
||
|
7 |
Order restriction |
Good For Closing Price Crossing Session: where an order qualifies for the closing price crossing session. Valid For Auction: the order is only active and can only be executed at auction phases (which can be pre-defined by the CASP client who submitted the order, e.g. opening and/closing auctions and/or intraday auction). Valid For Continuous Trading only: the order is only active during continuous trading. Other: any additional indications that are unique for specific business models, trading platforms or systems. |
‘SESR’ – Good For Closing Price Crossing Session ‘VFAR’ – Valid For Auction ‘VFCR’ – Valid For Continuous Trading only {ALPHANUM-4} character’ not already in use for the trading venue’s own classification. This field shall be populated with multiple flags separated by a comma where more than one flag is applicable. |
||
|
8 |
Validity period and time |
This field refers to the time stamp reflecting the time on which the order becomes active or it is ultimately removed from the order book: Good for day: the date of entry with the timestamp immediately prior to midnight; Good till time: the date of entry and the time to that specified in the order; Good till date: will be the specified date of expiry with the timestamp immediately prior to midnight; Good till specified date and time: the specified date and time of expiry; Good after time: the date of entry and the specified time at which the order becomes active; Good after date: the specified date with the timestamp immediately after midnight; Good after specified date and time: the specified date and time at which the order becomes active; Good till Cancel: the ultimate date and time the order is automatically removed by market operations; Other: timestamp for any additional validity type. |
{DATE_TIME_FORMAT} |
||
|
Section E – Identification of the order |
|||||
|
9 |
Segment MIC code |
Identification of the trading platform for crypto-asset where the order was submitted. Where the trading platform for crypto-asset uses segment MICs, the segment MIC shall be used. Where the trading platform for crypto-asset does not use segment MICs, the operating MIC shall be used. This field shall only be populated for orders to be executed on a trading platform for crypto-assets. |
{MIC} |
||
|
10 |
Crypto-asset identification code |
Unique and unambiguous identifier of the crypto-asset. |
{DTI} {ALPHANUM-20} |
||
|
11 |
Crypto-asset classification |
Taxonomy used to classify the crypto-asset or A complete and accurate CFI code shall be provided where available. |
ART EMT OT {CFI_CODE} |
||
|
12 |
Order identification code |
An alphanumerical code assigned by the operator of the trading platform for crypto-assets to the individual order. |
{ALPHANUM-50} |
||
|
Section F – Events affecting the order |
|||||
|
13 |
New order, order cancellation |
New order: submission of a new order to the CASP operating the trading platform for crypto-assets. Cancelled at the initiative of the client of the CASP: where the client decides upon its own initiative to cancel the order it has previously entered. |
‘NEWO’ – New order ‘CAME’ – Cancelled at the initiative of the client of the CASP |
||
|
Section G – Type of order |
|||||
|
14 |
Order type |
Identifies the type of order submitted to the trading platform for crypto-asset as per the trading platform for crypto-asset specifications. |
{ALPHANUM-50} |
||
|
15 |
Order type classification |
Classification of the order according to two generic order types. LIMIT order: where the order is tradable; STOP order: where the order becomes tradable only upon the realisation of a pre-determined price event. |
The letters ‘LMTO’ for limit or the letters ‘STOP’ for stop |
||
|
Section H – Prices |
|||||
|
16 |
Limit price |
The maximum price at which a buy order can trade or the minimum price at which a sell order can trade. The spread price for a strategy order, which can be negative or positive. This field shall be ‘NOAP’ for orders that do not have a limit price or for unpriced orders. Where the price is reported in monetary terms, the price shall be provided in the major currency unit. Where the crypto-asset is traded based on a currency pair, the price shall express the quantity of the quote currency for one unit of the base currency. Where the price is expressed in sub-components of that crypto-asset, the price shall nonetheless be recorded in decimal notation of the price expressed in units of that crypto-asset. |
{DECIMAL-18/13} in case the price is expressed as monetary value. {DECIMAL-11/10} in case the price is expressed as a percentage or yield. {DECIMAL-18/17} in case the price is expressed as basis points ‘NOAP’ |
||
|
17 |
Additional limit Price |
Any other limit price which may apply to the order. This field shall be left ‘NOAP’ where there is no limit price. Where the price is reported in monetary terms, the price shall be provided in the major currency unit. Where the crypto-asset is traded based on a currency pair, the price shall express the quantity of the quote currency for one unit of the base currency. Where the price is expressed in sub-components of that crypto-asset, the price shall nonetheless be recorded in decimal notation of the price expressed in units of that crypto-asset. |
{DECIMAL-18/13} where the price is expressed as a monetary value. {DECIMAL-11/10} where the price is expressed as a percentage or yield. {DECIMAL-18/17} in case the price is expressed as basis points ‘NOAP’ |
||
|
18 |
Stop price |
The price that must be reached for the order to become active. For stop orders triggered by events independent of the price of the crypto-asset, this field shall be populated with a stop price equal to zero. This field shall be ‘NOAP’ where not relevant. Where the price is reported in monetary terms, the shall be provided in the major currency unit. Where the crypto-asset is traded based on a currency pair, the price shall express the quantity of the quote currency for one unit of the base currency. Where the price is expressed in sub-components of that crypto-asset, the price shall be nonetheless recorded in decimal notation of the price expressed in units of that crypto-asset. |
{DECIMAL-18/13} where the price is expressed as a monetary value. {DECIMAL-11/10} where the price is expressed as a percentage or yield. {DECIMAL-18/17} in case the price is expressed as basis points ‘NOAP’ |
||
|
19 |
Pegged limit price |
The maximum price at which a pegged order to buy can trade or the minimum price at which a pegged order to sell can trade. This field shall be ‘NOAP’ if not relevant. Where the price is reported in monetary terms, the price shall be provided in the major currency unit. Where the crypto-asset is traded based on a currency pair, the price shall express the quantity of the quote currency for one unit of the base currency. Where the price is expressed in sub-components of that crypto-asset, the price shall be nonetheless recorded in decimal notation of the price expressed in units of that crypto-asset. |
{DECIMAL-18/13} where the price is expressed as a monetary value. {DECIMAL-11/10} where the price is expressed as a percentage or yield. {DECIMAL-18/17} in case the price is expressed as basis points ‘NOAP’ |
||
|
20 |
Transaction price |
Traded price of the transaction excluding, where applicable, commission, other fees and accrued interest. A price that is recorded in monetary terms shall be provided in the major currency unit. Where a price is not applicable, the field shall be populated with the value ‘NOAP’. Where the crypto-asset is traded based on a currency pair, the price shall express the quantity of the quote currency for one unit of the base currency. |
{DECIMAL-18/13} where the price is expressed as a monetary value. ‘NOAP’ |
||
|
21 |
Price currency |
Currency in which the trading price for the crypto-asset related to the order is expressed (applicable where the price is expressed as monetary value). Where the crypto-asset is traded in electronic money/e-money token, the Digital Token Identifier or the alternative identifier referred to in Article 15 shall be used. Where the price of the crypto-asset is expressed in monetary terms and it is expressed in a currency pair, the currency pair in which the price for the crypto-asset related to the order is expressed shall be reported. The first currency code shall be that of the base currency and the second currency code shall be that of the quote currency. The quote currency determines the price of one unit of the base currency. The ISO currency code and the DTI short name as registered according to the ISO 24165-2 data elements for registration of the DTI or alternative identifier shall be used to represent the fiat currency and the crypto-asset, respectively, in the currency pair. |
{CURRENCYCODE_3} {DTI} {ALPHANUM-20} {CURRENCYCODE_3} should be used for fiat currencies in a currency pair {DTI_SHORT_NAME} should be used for crypto assets in a currency pair ‘NOAP’ |
||
|
22 |
Price notation |
Indicates whether the price is expressed in monetary value, in percentage, in yield, or in basis points. |
‘MONE’ – Monetary value ‘PERC’ – Percentage ‘YIEL’ – Yield ‘BAPO’ – Basis points |
||
|
Section I – Order instructions |
|||||
|
23 |
Buy-sell indicator |
To show whether the order is to buy or sell. |
‘BUYI’ – buy ‘SELL’ – sell |
||
|
24 |
Order status |
To identify orders that are active/inactive/suspended: Active – non-quote orders that are tradable. Inactive – non-quote orders that are not tradable. |
‘ACTI’ – active or ‘INAC’ – inactive |
||
|
25 |
Quantity notation |
Indicates whether the quantity reported is expressed in number of units, as a nominal value, or as a monetary value, or crypto-assets units. |
‘UNIT’ – Number of units ‘NOML’ – Nominal value ‘MONE’ – Monetary value ‘CRYP’ – Crypto-asset |
||
|
26 |
Quantity currency |
Currency in which the quantity is expressed. The currency shall refer to the crypto-asset units, even where the transaction is denominated in sub-components of that crypto-asset. This field only needs to be populated where the quantity is expressed as a nominal or monetary value or crypto-assets units. |
{CURRENCYCODE_3} {DTI} {ALPHANUM-20} |
||
|
27 |
Initial quantity |
The number of units of the crypto-asset in the order. Where the order pertains to a fraction of a crypto-asset, indicate the quantity in decimal notation of the unit. The nominal or monetary value of the crypto-asset. |
{DECIMAL-18/17} in case the quantity is expressed as number of units {DECIMAL-18/5} in case the quantity is expressed as monetary or nominal value |
||
|
28 |
Remaining quantity |
The total quantity that remains in the order book after a partial execution or in the case of any other event affecting the order. On a partial fill order event, this shall be the total remaining volume after that partial execution. On an order entry, this shall equal the initial quantity. |
{DECIMAL-18/17} in case the quantity is expressed as a number of units {DECIMAL-18/5} where the quantity is expressed as monetary or nominal value |
||
|
29 |
Traded quantity |
Where there is a partial or full execution, this field shall be populated with the executed quantity. |
{DECIMAL-18/17} in case the quantity is expressed as a number of units {DECIMAL-18/5} where the quantity is expressed as monetary or nominal value |
||
|
30 |
Minimum Acceptable Quantity (MAQ) |
The minimum acceptable quantity for an order to be filled, which can consist of multiple partial executions and is normally only for non-persistent order types. This field shall be ‘NOAP’ where not relevant. |
{DECIMAL-18/17} in case the quantity is expressed as a number of units {DECIMAL-18/5} where the quantity is expressed as monetary or nominal value ‘NOAP’ |
||
|
31 |
Minimum executable size (MES) |
The minimum execution size of any individual potential execution. This field shall be left blank where not relevant. |
{DECIMAL-18/17} in case the quantity is expressed as a number of units {DECIMAL-18/5} where the quantity is expressed as monetary or nominal value |
||
|
32 |
MES first execution only |
Specifies whether the MES is relevant only for the first execution. This field can be left blank where Field 29 is left blank. |
‘true’ ‘false’ |
||
|
33 |
Passive only indicator |
Indicates whether the order is submitted to the trading platform for crypto-asset with a characteristic/flag, such that the order shall not immediately be executed against any contra visible orders. |
‘true’ ‘false’ |
||
|
34 |
Passive or aggressive indicator |
On partial fill and fill order events, indicates whether the order was already resting on the order book and providing liquidity (passive) or the order initiated the trade and thus took liquidity (aggressive). This field shall be left blank where not relevant |
‘PASV’ – passive or ‘AGRE’ – aggressive. |
||
|
35 |
Self-Execution Prevention |
Indicates whether the order has been entered with self-execution prevention criteria, so that it would not execute with an order on the opposite side of the book entered by the same member or participant. |
‘true’ ‘false’ |
||
|
36 |
Trading platform for crypto-asset transaction identification code |
For orders executed on trading platforms for crypto-assets, alphanumerical code assigned by the trading platform for crypto-assets to the transaction pursuant to Article 14 of Commission Delegated Regulation (EU) 2025/416 (2). The code shall be unique, consistent, and persistent per ISO10383 segment MIC and per trading day. The components of the transaction identification code shall not disclose the identity of the counterparties to the transaction for which the code is maintained.
|
{ALPHANUM-52} |
||
|
Section J – Indicative auction price and volume |
|||||
|
37 |
Indicative auction price |
The price at which each auction is due to uncross in respect to the crypto-asset for which one or more orders have been placed. |
{DECIMAL-18/5} in case the price is expressed as monetary or nominal value. Where price reported in monetary terms, it shall be provided in the major currency unit. {DECIMAL-11/10} in case the price is expressed as a percentage or yield |
||
|
38 |
Indicative auction volume |
The volume (number of units of crypto-asset) that can be executed at the indicative auction price in Field 50 where the auction ended at that precise moment of time. |
{DECIMAL-18/17} in case the quantity is expressed as number of units {DECIMAL-18/5} in case the quantity is expressed as monetary or nominal value |
||
|
Section K – Order transmission |
|||||
|
39 |
Transmitting crypto-asset service provider |
In case of transmission of an order under Article 11, the LEI code of the transmitting crypto-asset service provider. |
{LEI} |
||
|
40 |
Transmission of an order indicator |
‘true’ shall be populated by the transmitting firm within the transmitting firm’s report where the conditions for transmission specified in Article 11 were not satisfied ‘false’ – in all other circumstances |
‘true’ ‘false’ |
||
|
Section L – Country of residence of the client |
|||||
|
41 |
Identification of the country of residence |
Shall be populated where a client is a resident of a country other than the one of its nationality, as described in Article 9(5). |
{COUNTRYCODE_2} ‘NOAP’ |
||
SECTION 3
Records of transactions
For the legend, please refer to Section 2, Table 1.
Table 3
Details of transactions to be kept
|
Field no |
Field |
Content to be recorded |
Details on transaction data to be provided to the competent authority |
|
1 |
Transaction status |
Indication as to whether the transaction is new or a cancellation. |
‘NEWT’ – New ‘CANC’ – Cancellation |
|
2 |
Transaction Record Number |
Identification number that is unique to the executing firm for each record. |
{ALPHANUM-52} |
|
3 |
Trading platform for crypto-asset transaction identification code |
This is a number generated by the trading platform for crypto-assets and disseminated to both the buying and the selling parties in accordance with Article 14 of Delegated Regulation (EU) 2025/416 supplementing Regulation (EU) 2023/1114. Where relevant, the transaction hash or other identification alphanumerical string which is automatically generated on the DLT that enables to uniquely identify a specific transaction. |
{ALPHANUM-52} |
|
4 |
Executing entity identification code |
Code used to identify the entity executing the transaction. |
{LEI} {ALPHANUM-20} |
|
5 |
CASP covered by Regulation (EU) 2023/1114. |
Indicates whether the entity identified in Field 4 is a crypto-asset service provider to which Regulation (EU) 2023/1114 applies. |
‘true’ – yes ‘false’ – no |
|
6 |
Buyer identification code |
Code used to identify the acquirer of the crypto-asset. Where the buyer is a legal entity, the LEI code of the acquirer or the alternative identifiers referred to in Article 14(3) shall be used. Where the buyer is a natural person, the identifier specified in Article 9. Where the order was transmitted for execution on behalf of clients to a firm performing crypto-asset services outside of the Union, the MIC code of the platform or the LEI or equivalent identifiers referred to in Article 14 of the firm shall be used. Where the crypto-asset service provider executes the transaction on a trading platform located in a third country, the LEI of the buyer, the alternative identifier referred to in Article 14(3) or the National ID shall be recorded. ‘INTC’ shall be used to designate an aggregate client account within the crypto-asset service provider to report a transfer into or out of that account with an associated allocation to the individual client(s) out of or into that account respectively. |
{LEI} {ALPHANUM-20} {MIC} {NATIONAL_ID} ‘INTC’ |
|
7 |
Country of the branch of the crypto-asset service provider for the buyer |
Where the buyer is a client, this field shall identify the country of the branch that received the order from the client or made an investment decision for a client in accordance with a discretionary mandate given to it by the client as required by Article 16. Where this activity was not conducted by a branch, this field should be populated with the country code of the home Member State of the crypto-asset service provider or the country code of the Member State where the crypto-asset service provider has established its registered office. |
{COUNTRYCODE_2} |
|
8 |
Buyer – first name(s) |
Full first name(s) of the buyer. In case of more than one first name, all names shall be included in this field, separated by a comma. |
{ALPHANUM-140} |
|
9 |
Buyer – surname(s) |
Full surname(s) of the buyer. In case of more than one surname, all surnames shall be included in this field, separated by a comma. |
{ALPHANUM-140} |
|
10 |
Buyer – date of birth |
Date of birth of the buyer. |
{DATEFORMAT} |
|
11 |
Buyer decision maker code |
Code used to identify the person who makes the decision to acquire the crypto-asset. Where the decision is made by a crypto-asset service provider, this field shall be populated with the identity of the crypto-asset service provider rather than of the individual making the investment decision. Where the decision-maker is a legal entity, the LEI code or the alternative identifiers referred to in Article 14(3) of the decision-maker shall be used. Where the decision-maker is not a legal entity, the identifier specified in Article 9 shall be used. |
{LEI} {ALPHANUM-20} {NATIONAL_ID} |
|
12 |
Buy decision maker – First Name(s) |
Full first name(s) of the decision-maker for the buyer. In case of more than one first name, all names shall be included in this field, separated by a comma. |
{ALPHANUM-140} |
|
13 |
Buy decision maker – Surname(s) |
Full surname(s) of the decision-maker for the buyer. In case of more than one surname, all surnames shall be included in this field, separated by a comma. |
{ALPHANUM-140} |
|
14 |
Buy decision maker – Date of birth |
Date of birth of the decision-maker for the buyer. |
{DATEFORMAT} |
|
15 |
Seller identification code |
Code used to identify the disposer of the crypto-asset. Where the seller is a legal entity, the LEI code of the disposer or the alternative identifiers referred to in Article 14(3) shall be used. Where the seller is not a legal entity, the identifier specified in Article 9 shall be used. Where the order was transmitted for execution on behalf of the client to a crypto-asset service provider providing services outside of the Union, the MIC code of the platform or the LEI of that crypto-asset service provider shall be used. Where the crypto-asset service provider executes the transaction on a trading platform located in a third country, the LEI, the alternative identifier referred to in Article 14(3) or the National ID of the seller shall be provided. ‘INTC’ shall be used to designate an aggregate client account within the CASP to record a transfer into or out of that account with an associated allocation to the individual client(s) out of or into that account respectively. |
{LEI} {ALPHANUM-20} {MIC} {NATIONAL_ID} ‘INTC’ |
|
16 |
Country of the branch for the seller |
Where the seller is a client, this field shall identify the country of the branch that received the order from the client or made an investment decision for a client in accordance with a discretionary mandate given to it by the client as required by Article 16. Where this activity was not conducted by a branch, this field shall be populated with the country code of the home Member State of the crypto-asset service provider or the country code of the country where the crypto-asset service provider has established its head office or registered office (in the case of third-country firms). |
{COUNTRYCODE_2} |
|
17 |
Seller – first name(s) |
Full first name(s) of the seller. In case of more than one first name, all names shall be included in this field, separated by a comma. |
{ALPHANUM-140} |
|
18 |
Seller – surname(s) |
Full surname(s) of the seller. In case of more than one surname, all surnames shall be included in this field, separated by a comma. |
{ALPHANUM-140} |
|
19 |
Seller – date of birth |
Date of birth of the seller. |
{DATEFORMAT} |
|
20 |
Seller decision maker code |
Code used to identify the person who makes the decision to sell the crypto-asset. Where the decision is made by a crypto-asset service provider, this field shall be populated with the identity of the CASP rather than of the individual making the investment decision. Where the decision maker is a legal entity, the LEI code or the alternative identifier referred to in Article 14(3) of the decision maker shall be used. Where the decision maker is a non-legal entity, the identifier specified in Article 9 shall be used. |
{LEI} {ALPHANUM-20} {NATIONAL_ID} |
|
21 |
Sell decision maker – First Name(s) |
Full first name(s) of the decision maker for the seller. In case of more than one first name, all names shall be included in this field, separated by a comma. |
{ALPHANUM-140} |
|
22 |
Sell decision maker – Surname(s) |
Full surname(s) of the decision maker for the seller. In case of more than one surname, all surnames shall be included in this field, separated by a comma. |
{ALPHANUM-140} |
|
23 |
Sell decision maker – Date of birth |
Date of birth of the decision maker for the seller. |
{DATEFORMAT} |
|
24 |
Transmission of order indicator |
‘true’ shall be populated by the transmitting firm within the transmitting firm’s report where the conditions for transmission specified in Article 11 were not satisfied ‘false’ – in all other circumstances |
‘true’ ‘false’ |
|
25 |
Transmitting firm identification code for the buyer |
Code used to identify the firm transmitting the order. This shall be populated by the receiving firm within the receiving firm’s report with the identification code provided by the transmitting firm. |
{LEI} {ALPHANUM-20} |
|
26 |
Transmitting firm identification code for the seller |
Code used to identify the firm transmitting the order. This shall be populated by the receiving firm within the receiving firm’s report with the identification code provided by the transmitting firm |
{LEI} {ALPHANUM-20} |
|
27 |
Trading date time |
Date and time when the transaction was executed. For transactions not executed on a trading venue, the date and time shall be when the parties agree to the content of the following fields: quantity, price, currencies in Fields 31, 34 and 44, instrument identification code, instrument classification and underlying instrument code, where applicable. For transactions not executed on a trading venue, the time recorded shall be at least to the nearest second. Where the transaction results from an order transmitted by the executing firm on behalf of a client to a third party where the conditions for transmission set out in Article 11 were not satisfied, this shall be the date and time of the transaction rather than the time of the order transmission. |
{DATE_TIME_FORMAT} |
|
28 |
Trading capacity |
Indicates whether the CASP undertaking the transaction is carrying out matched principal trading, or exchange of crypto-assets for funds. Where the transaction does not result from the executing firm carrying out matched principal trading or through exchange of crypto-assets for funds, the field shall indicate that the transaction was carried out under any other capacity. |
‘DEAL’ – Exchange of crypto-assets for funds or other crypto-assets ‘MTCH’ – Matched principal ‘AOTC’ – Any other capacity |
|
29 |
Quantity |
The number of units of the crypto-assets or the monetary value of the crypto asset. Where the price is expressed in sub-components of that crypto-asset, it shall be nonetheless recorded in decimal notation of the price expressed in units of that crypto-asset. The information reported in this field shall be consistent with the values provided in Fields 31 and 32. |
{DECIMAL-18/17} in case the quantity is expressed as number of units {DECIMAL-18/5} in case the quantity is expressed as monetary or nominal value |
|
30 |
Quantity currency |
Currency in which the quantity is expressed. Only applicable where the quantity is expressed as nominal or monetary value. The quantity shall refer to the crypto-asset units, even where the transaction is denominated in sub-components of that crypto-asset. Where the crypto-asset is traded in electronic money/e-money token, the Digital Token Identifier code or the alternative identifier referred to in Article 15 shall be used. |
{CURRENCYCODE_3} {DTI} {ALPHANUM-20} |
|
31 |
Price |
Traded price of the transaction excluding, where applicable, commission, any other fee and accrued interest. Where the crypto-asset is traded based on a currency pair, the price shall express the quantity of the quote currency for one unit of the base currency. Where the price is expressed in sub-components of that crypto-asset, the price shall be nonetheless recorded in decimal notation of the price expressed in units of that crypto-asset. Where the price is recorded in monetary terms, the price shall be provided in the major currency unit. Where price is not applicable, the value shall be ‘NOAP’. The information recorded in this field shall be consistent with the values provided in Field 30. |
{DECIMAL-18/13} in case the price is expressed as monetary value {DECIMAL-11/10} in case the price is expressed as percentage or yield {DECIMAL-18/17} in case the price is expressed as basis points ‘NOAP’ in case the price is not applicable |
|
32 |
Price Currency |
Currency in which the price is expressed (applicable where the price is expressed as a monetary value). Where the price of the crypto-asset is expressed in monetary terms and is expressed in a currency pair, the currency pair in which the price for the crypto-asset related to the order is expressed shall be reported. The first currency code shall be that of the base currency and the second currency code shall be that of the quote currency. The quote currency determines the price of one unit of the base currency. The ISO currency code and the DTI short name as registered in accordance with the ISO 24165-2 data elements for registration of the DTI or the alternative identifier referred to in Article 15 shall be used to represent the fiat currency and the crypto asset respectively in the currency pair. |
{CURRENCYCODE_3} {DTI} {ALPHANUM-20} {CURRENCYCODE_3} should be used for fiat currencies in a currency pair {DTI_SHORT_NAME} should be used for crypto assets in a currency pair ‘NOAP’ |
|
33 |
Trading platform for crypto-asset |
Identification of the trading platform for crypto-asset where the transaction was executed. Use the ISO 10383 segment MIC for transactions executed on a trading platform for crypto-assets. Where the segment MIC does not exist, use the operating MIC. Use MIC code ‘XOFF’ for crypto-assets admitted to trading, or traded on a trading platform for crypto-assets or for which a request for admission was made, where the transaction on that crypto-asset was not executed on a trading platform for crypto-assets. Use MIC code ‘XXXX’ for crypto-assets that are not admitted to trading or traded on a trading platform for crypto-assets, or for which no request for admission has been made. |
{MIC} |
|
34 |
Country of the branch membership |
Code used to identify the country of a branch of the crypto-asset service provider whose trading platform for crypto-asset membership was used to execute the transaction. Where a branch’s trading platform for crypto-asset membership was not used, this field shall be populated with the country code of the home Member State of the crypto-asset service provider or the country code of the country where the firm has established its head office or registered office (in the case of third-country firms). This field shall only be populated for the market side of a transaction executed on a trading platform for crypto-assets. |
{COUNTRYCODE_2} |
|
35 |
Up-front payment |
Monetary value of any up-front payment received or paid by the seller. Where the seller receives the up-front payment, the value populated shall be positive. Where the seller pays the up-front payment, the value populated shall be negative. |
{DECIMAL-18/5} |
|
36 |
Up-front payment currency |
Currency of the up-front payment. |
{CURRENCYCODE_3} {DTI} {ALPHANUM-20} |
|
37 |
Complex trade component id |
Identifier, internal to the crypto-asset service provider, to identify all the transaction records related to the same execution of a combination of crypto-assets. The code must be unique at the level of the firm for the group of transaction records related to the execution. |
{ALPHANUM-35} |
|
38 |
Crypto-asset identification code |
Code used to identify the crypto-asset. This field applies to crypto-assets for which a request for admission to trading has been made, that are admitted to trading or traded on a trading platform for crypto-assets. |
{DTI} {ALPHANUM-20} |
|
39 |
Crypto-asset full name |
Full name of the crypto-asset. |
{ALPHANUM-350} |
|
40 |
Crypto-asset classification |
Taxonomy used to classify the crypto-asset. or A complete and accurate CFI code shall be provided where available. |
ART EMT OT {CFI_CODE} |
|
41 |
Investment decision within the crypto-asset service provider |
Code used to identify the person or algorithm within the crypto-asset service provider taking the investment decision. The code shall remain the same for each set of code or trading strategy that constitutes the algorithm and shall be used consistently when referring to the algorithm or version of the algorithm once assigned to it. For natural persons, the identifier specified in Article 9 shall be used where the investment decision was made by an algorithm that automatically determines individual parameters of orders, including the decision to initiate the order or determining its timing, price or quantity, the field shall be populated as set out in Article 8. This field only applies for investment decision within the firm. Where the transaction is for a transmitted order that has met the conditions for transmission set out in Article 11, this field shall be populated by the receiving firm within the receiving firm’s record using the information received from the transmitting firm. |
{NATIONAL_ID} – Natural persons {ALPHANUM-50} – Algorithms |
|
42 |
Country of the branch responsible for the person making the investment decision |
Code used to identify the country of the branch of the crypto-asset service provider for the person taking the investment decision, as set out in Article 16. Where the person taking the investment decision was not supervised by a branch, this field shall be populated with the country code of the home Member State of the crypto-asset service provider or the country code of the Member State where the crypto-asset service provider has established its registered office. Where the transaction is for a transmitted order that has met the conditions for transmission set out in Article 11, this field shall be populated by the receiving firm within the receiving firm’s record using the information received from the transmitting firm. This field is not applicable where the investment decision was made by an algorithm that automatically determines individual parameters of orders, including as whether to initiate the order or determining its timing, price, or quantity. |
{COUNTRYCODE_2} |
|
43 |
Execution within firm |
Code used to identify the person or algorithm that automatically determines individual parameters within the crypto-asset service provider for the execution of orders, including the decision to initiate the order or determining its timing, price, or quantity. For natural persons, the identifier specified in Article 9 shall be used. Where the execution was made by an algorithm that automatically determines individual parameters of orders, including the decision to initiate the order or determining its timing, price, or quantity, the field shall be populated as set out in Article 8. |
{NATIONAL_ID} – Natural persons {ALPHANUM-50} – Algorithms CLIENT – Client |
|
44 |
Country of the branch supervising the person determining the conditions for execution |
Code used to identify the country of the branch of the crypto-asset service provider for the person determining the execution of the transaction, as set out in Article 16. Where the person responsible was not supervised by a branch, this field shall be populated with the country code of the home Member State of the crypto-asset service provider, or the country code of the country where the crypto-asset service provider has established its registered office. This field is not applicable where the execution was made by an algorithm that automatically determines individual parameters of orders, including the decision to initiate the order, or determining its timing, price or quantity. |
{COUNTRYCODE_2} |
|
45 |
Short selling indicator |
Designation to identify any sale of a crypto-asset which the seller does not own at the time of entering into the agreement to sell, including such a sale where at the time of entering into the agreement to sell the seller has borrowed or agreed to borrow the share or debt instrument for delivery at settlement. |
‘true’ ‘false’ |
SECTION 4
On-chain data
Table 4
Details of on-chain data to be kept
|
Field no |
Field |
Content to be recorded |
Details to be provided to the competent authority |
|
1 |
Transaction hash |
Identifier enabling the unique identification of a specific transaction occurring on the network. |
{ALPHANUM-140} |
|
2 |
Wallet addresses |
Code uniquely identifying the wallet, belonging to the buyer/seller, to which the crypto-asset is transferred. |
{ALPHANUM-140} |
|
3 |
Smart Contract Addresses |
Code uniquely identifying the smart contract address. |
{ALPHANUM-140} |
|
4 |
Timestamp |
Timestamp of the creation of the block. |
{DATE_TIME_FORMAT} |
|
5 |
Quantity/ Current Total Supply |
Ratio between the transferred quantity and the current floating amount of the asset. |
|
|
6 |
Token ID |
Digital Token Identifier |
{DTI} |
|
7 |
Network fee |
Fees which are requested to cover the costs for the creation of a new block. |
|
|
8 |
Fee limit |
This is the maximum amount of ‘network fees’ that an on-chain user is willing to pay for the executions of a specific transaction. |
|
|
9 |
Data size |
This field is connected to Field 8. On-chain transaction can contain ‘attachments’ in a specific data field that affect the ‘network fees’ required to process the transaction. |
|
|
10 |
To |
The unique identifiers for buyer and seller are usually generated by the DLT protocol on the basis of the buyer/seller wallet addresses. |
{ALPHANUM-140} |
|
11 |
From |
The unique identifier for seller usually generated by the DLT protocol on the basis of the seller wallet addresses. |
{ALPHANUM-140} |
|
12 |
Currency |
Currency code |
{CURRENCYCODE_3} {DTI} |
|
13 |
Transaction Record Number |
Identification number reported in Field 2 of Section 3 that is unique to the executing firm for each record to ensure that a link can be made between the on-chain report and the off-chain one. |
{ALPHANUM-140} |
(1) Commission Delegated Regulation (EU) 2025/294 of 1 October 2024 supplementing Regulation (EU) 2023/1114 of the European Parliament and of the Council with regard to regulatory technical standards specifying the requirements, templates and procedures for the handling of complaints by the crypto-asset service providers (OJ L, 2025/294, 13.2.2025, ELI: http://data.europa.eu/eli/reg_del/2025/294/oj).
(2) Commission Delegated Regulation (EU) 2025/416 of 29 November 2024 supplementing Regulation (EU) 2023/1114 of the European Parliament and of the Council with regard to regulatory technical standards specifying the content and format of order book records for crypto-asset service providers operating a trading platform for crypto-assets (OJ L, 2025/416, 14.3.2025, ELI: http://data.europa.eu/eli/reg_del/2025/416/oj).
ELI: http://data.europa.eu/eli/reg_del/2025/1140/oj
ISSN 1977-0677 (electronic edition)