Regulation (EU) 2023/1114 · Directive (EU) 2023/2226
Every figure on this page comes from a file held on disk, with its sha256 and the date it was retrieved. Where nothing is held, it says so — rather than estimating. There is no compliance score, because no regulator publishes one.
Authorisations, DAC8 implementing acts and flagged entities per state. Labels are facts from the register — never a judgement like “crypto-friendly”, which nothing on disk could support.
Straight from the register's own non-compliant file. No severity score is shown, because none is published.
This panel is where a dashboard would normally put a compliance score. There isn’t one, and this is more useful.
docs_evidence/eu-market-access/mica-register/20260812T102755Z.
CASPS.csv sha256 6695cd09464c354a58250fc49dddd87eb0663f5254bac8924e144025c5938a11 (385 rows,
modified Wed, 12 Aug 2026 08:47:01 GMT) ·
NCASP.csv sha256 fb778670226ec6d53e2cc23f210736ce02ab832c78a3a5e5ea08138deaf8dc5f (167 rows) ·
ARTZZ.csv sha256 fa1ef4da123e3d49642c69f90a81a88f6c2cc2a0b9471b2108e4dfc635ca7c67 (0 rows).
DAC8 transposition from EUR-Lex, CELEX 32023L2226.
Rendered from state/crypto_jurisdictions.json — this page never reads a
register file directly, so any front end can consume the same contract.