Rule · MAJOR
COMMON.LANGUAGE
Language of the white paper (home Member State official language or customary in international finance)
- Citation
- Art. 6(9), Art. 19(8), Art. 51(8) MiCAR
- Canonical form
- Art. 6 Abs. 9, Art. 19 Abs. 8, Art. 51 Abs. 8 MiCAR
- Runs for
- Annex I · other crypto-assets; Annex II · asset-referenced tokens; Annex III · e-money tokens
- Severity if open
- MAJOR
- Section key
language- Minimum words
- none: checks for an official EU language
- 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
languageis absent or empty, or holds only placeholder text such as TBD or TBC. - Review: the section names none of the 24 official languages of the EU.
- Pass: the section names at least one of them by its English or German name, however short the section: Bulgarian (Bulgarisch), Croatian (Kroatisch), Czech (Tschechisch), Danish (Dänisch), Dutch (Niederländisch), English (Englisch), Estonian (Estnisch), Finnish (Finnisch), French (Französisch), German (Deutsch), Greek (Griechisch), Hungarian (Ungarisch), Irish (Irisch), Italian (Italienisch), Latvian (Lettisch), Lithuanian (Litauisch), Maltese (Maltesisch), Polish (Polnisch), Portuguese (Portugiesisch), Romanian (Rumänisch), Slovak (Slowakisch), Slovenian (Slowenisch), Spanish (Spanisch), Swedish (Schwedisch). Slovene counts as well. English names count as written or in capitals. German names count in any case, also inflected or with
-sprachig:in deutscher Sprache,englischsprachig. A pass means a language name was found, nothing more.
Legal basis
Art. 6(9), Art. 19(8), Art. 51(8) 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(9), Art. 19(8) or Art. 51(8). The list of languages is Art. 1 of Council Regulation No 1 in its consolidated version of 1 July 2013.
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": {
"language": "TBD"
}
}The sentence repeats the wording of the requirement and names no language.
{
"title": "Synthetic rule example",
"type": "other",
"sections": {
"language": "This white paper is drawn up in a language customary in the sphere of international finance."
}
}Since 23 December 2025 the template of Implementing Regulation (EU) 2024/2984 asks for the language or languages of the white paper, from a closed list of EU languages. The check does not decide whether the language meets the home or host Member State requirement.
{
"title": "Synthetic rule example",
"type": "other",
"sections": {
"language": "Language or languages of the crypto-asset white paper: English"
}
}Limitations
- Reads one section key,
language. Text elsewhere in the draft is not considered. - Looks for a language name only. The cited paragraphs require the white paper to be drawn up in an official language of the home Member State or in a language customary in the sphere of international finance, and likewise for a host Member State where the crypto-asset is also offered. They do not require the white paper to name its language; since 23 December 2025 the template of Implementing Regulation (EU) 2024/2984 asks for it (field F.12 of Table 2, B.14 of Table 3, B.11 of Table 4). The check cannot tell which language the white paper is drawn up in, or whether that language meets the requirement. Language codes such as EN and names in other languages, such as français, do not count.
- 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.