MiCA register and change log, as published by CryptoCodes.eu ============================================================= Files mica-register.csv / .json one row per legal entity (LEI) mica-register-changes.csv / .json one row per change between two ESMA lists Human-readable versions https://www.cryptocodes.eu/mica/authorisations https://www.cryptocodes.eu/mica/authorisations/changes Source European Securities and Markets Authority (ESMA), interim MiCA register, file CASPS.csv: https://www.esma.europa.eu/sites/default/files/2024-12/CASPS.csv Available free of charge from ESMA: https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica The date of the ESMA list is in every file (esma_list_date). What we changed - dates written as ISO 8601 - country codes normalised (spelling variants, spaces); legal basis written as Art. 60 or Art. 63 MiCA - home Member State added to the passport countries where ESMA left it out - entries with the same LEI merged into one row (all passport countries, earliest date) - entries whose end date has passed left out - services shortened to ESMA's own letter codes a to j - all 30 EEA countries shown as EEA Notice required by ESMA This document has been drafted using material downloaded from ESMA’s website. ESMA does not endorse this publication and in no way is liable for copyright or other intellectual property rights infringements nor for any damages caused to third parties through this publication. CryptoCodes.eu is not affiliated with ESMA. Licence - Values taken from CASPS.csv (names, LEI, authority, Member State, dates, services, passport countries, legal basis), also where reformatted: reused under ESMA's legal notice, https://www.esma.europa.eu/about-esma/legal-notice-and-data-protection These are not covered by CC BY 4.0. - Our own work (the merging per LEI, the change log, the notes and the column descriptions): CC BY 4.0, https://creativecommons.org/licenses/by/4.0/ How to cite Source: ESMA interim MiCA register, processed by CryptoCodes.eu (https://www.cryptocodes.eu/mica/authorisations), ESMA list of . Absence from these files says nothing about whether a provider is authorised: check the competent authority. Not legal or financial advice.