Rule · MAJOR
COMMON.NOTIFICATION_DATE
Date of notification to the competent authority
- Citation
- Art. 6(8), Art. 19(7), Art. 51(7) MiCAR
- Canonical form
- Art. 6 Abs. 8, Art. 19 Abs. 7, Art. 51 Abs. 7 MiCAR
- Runs for
- Annex I · other crypto-assets; Annex II · asset-referenced tokens; Annex III · e-money tokens
- Severity if open
- MAJOR
- Section key
notification_date- Minimum words
- none: checks for a calendar date
- Listed terms (English)
- none
- Listed terms (German)
- none
- Package version
- 1.2.1, built from source that may include unreleased changes
- Source
- rules/common.py
How the status is set
- Missing: section
notification_dateis absent or empty, or holds only placeholder text such as TBD or TBC. - Review: the section names no calendar date, that is no day, month and four-digit year that exist together. A month with its year, a two-digit year and an impossible date such as 31.02.2026 count as no date.
- Pass: the section names such a date, however short the section. It may read
2026-03-02,02.03.2026or2/3/2026, or write the month in English or German, as in2 March 2026,March 2, 2026or2. März 2026. A pass means a date was found, nothing more.
Legal basis
Art. 6(8), Art. 19(7), Art. 51(7) MiCAR
Checked on 2026-10-27 against the Official Journal text in English and German (OJ L 150, 9.6.2023) and the consolidated version of 9 January 2024. No amendment and no English or German corrigendum changes Art. 6(8), Art. 19(7) or Art. 51(7). The date format was read in the English and German text of Implementing Regulation (EU) 2024/2984, which has no amendment or corrigendum.
Synthetic examples
Each example is linted when this page is generated. The build fails if a result differs.
The section key is missing or empty.
{
"title": "Synthetic rule example",
"type": "other",
"sections": {}
}A placeholder alone is no answer, so the section counts as missing.
{
"title": "Synthetic rule example",
"type": "other",
"sections": {
"notification_date": "TBD"
}
}A month and a year name no calendar date.
{
"title": "Synthetic rule example",
"type": "other",
"sections": {
"notification_date": "Notified in March 2026."
}
}Since 23 December 2025 the template of Implementing Regulation (EU) 2024/2984 has the date reported as YYYY-MM-DD (field 01 of Table 2, I.01 of Tables 3 and 4). Four words suffice. The check does not confirm that the date is the date of notification.
{
"title": "Synthetic rule example",
"type": "other",
"sections": {
"notification_date": "Date of notification: 2026-03-02"
}
}Limitations
- Reads one section key,
notification_date. Text elsewhere in the draft is not considered. - Looks for a calendar date only. It does not confirm that the date is the date of notification or that it is plausible, and it does not check the table of contents that the same provisions require. Since 23 December 2025 the template of Implementing Regulation (EU) 2024/2984 has the date reported as YYYY-MM-DD; the check accepts the other formats above as well and does not test that form.
- Status and severity are fixed by the rule. A draft cannot waive or downgrade them.
Disagree with this rule, or missing one? Propose a rule change.