SYMBOL

DATA TYPE

DEFINITION

{ALPHANUM-n}

Up to n alphanumerical characters

Free text field.

{DATE_TIME_FORMAT}

ISO 8601 date and time format

Date and time in the following format:

YYYY-MM-DDThh:mm:ss.ddddddZ.

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

{FFG DTI}

9 alphanumerical characters

Code to identify a group of equivalent Digital Token Identifiers as defined in ISO 24165 standard type 3

{INTEGER-n}

Integer number of up to n digits in total

Numerical field for both positive and negative integer values.

{LEI}

20 alphanumerical characters

Legal entity identifier as defined in ISO 17442

{MIC}

4 alphanumerical characters

Market identifier as defined in ISO 10383

Number

Field

Content

Form and standards

1

Type of crypto-asset white paper

The type of crypto-asset white paper notified.

Where the crypto-asset white paper concerns asset-referenced tokens, the code ‘ARTW’ shall be used.

Where the crypto-asset white paper concerns e-money tokens, the code ‘EMTW’ shall be used.

Where the crypto-asset white paper concerns crypto-assets other than asset-referenced tokens and e-money tokens the code ‘OTHR’ shall be used.

Choice from list of predefined values:

‘ARTW’

‘EMTW’

‘OTHR’

2

Name of the issuer

Name of the issuer

Free alphanumerical text

3

Legal form of the issuer

Legal form

ISO standard 20275 ‘Financial Services – Entity Legal Forms (ELF)’

4

Legal entity identifier of the issuer, where available

Legal entity identifier of the issuer, where available

{LEI}

5

Other identifier of the issuer required pursuant to applicable national law, where available

Other identifier of the issuer required pursuant to applicable national law, where available

Free alphanumerical text

6

Legal entity identifier of the entity that drew up the crypto-asset white paper, where available

Legal entity identifier of the entity that drew up the crypto-asset white paper, where available

{LEI}

7

Other identifier of the entity that drew up the crypto-asset white paper required pursuant to applicable national law, where available

Other identifier of the entity that drew up the crypto-asset white paper required pursuant to applicable national law

Free alphanumerical text

8

Identifier of operator of the trading platform

Segment market identifier code (MIC) for the trading platform operated by the crypto-asset service provider (CASP), where available, otherwise operating MIC

{MIC}

9

Commercial name or trading name of the issuer, where available

Commercial name or trading name of the issuer, where available

Free alphanumerical text

10

Physical address of the issuer

Physical address of the issuer

Free alphanumerical text

11

Telephone number of the issuer, where available

Telephone number of the issuer, where available

Free alphanumerical text

12

Email of the issuer, where available

Email of the issuer, where available

Free alphanumerical text

13

Website of the issuer

Website of the issuer

Free alphanumerical text

14

Home Member State

Home Member State as defined in Article 3, point (33), of Regulation (EU) 2023/1114

Closed list of EU Member States

15

Host Member States

Host Member State as defined in Article 3, point (34), of Regulation (EU) 2023/1114.

Closed list of EU Member States

16

Starting date of offer to the public or admission to trading

Starting date or, if not available at the time of the notification by the competent authority, the intended starting date of offer to the public or admission to trading

YYYY-MM-DD

17

Any other services provided by the issuer

Any other services provided by the issuer not covered by Regulation (EU) 2023/1114, with a reference to the applicable Union or national legal acts regulating that service, where applicable

Free alphanumerical text

18

The date of authorisation, where applicable

The date of authorisation by the competent authority, where applicable

YYYY-MM-DD

19

The date of withdrawal of authorisation, where applicable

The date of withdrawal of authorisation by the competent authority, where applicable

YYYY-MM-DD

20

Publication date

Effective or intended publication date of the crypto-asset white paper or of the modified crypto-asset white paper, as applicable

YYYY-MM-DD

21

Date and time of notification

Date and time of the latest notification of the white paper to the competent authority

YYYY-MM-DD Thh:mm:ss.ddddddZ.

22

Language or languages of the crypto-asset white paper

Language or languages in which the crypto-asset white paper is drafted.

Where multiple languages have been used, this field shall be reported as many times as necessary

Closed list of EU languages

23

Record identifier

Unique identifier of the uploaded record, assigned by the sending competent authority

{ALPHANUM-500}

24

Data file reference

Reference code needed to link the data file with corresponding metadata file

{ALPHANUM-500}

25

The type of submission

Type of submission

NEWT = New

MODI = Modify

EROR = Error

CORR = Correction

26

Version

Version of the dataset (data and metadata)

{INTEGER-50}

27

Digital Token Identifier used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available

Code used to uniquely identify the crypto-asset or each of the several crypto assets to which the crypto-asset white paper relates, where available

ISO 24165 Digital Token Identifier {DTI}

28

Functionally Fungible Group Digital Token Identifier, where available

Code used to uniquely identify the functionally fungible group to which the digital asset belongs (i.e. common to each of the several assets to which the crypto-asset white paper relates), i.e. code used to identify the white paper ISO 24165 DTI of type = 3 (i.e. functionally fungible group), where available

ISO 24165 [FFG DTI]

29

Personal data flag

Flag indicating if the submitted crypto-asset white paper contains personal data

‘true’ – Yes

‘false’ – No