Hakadian reads primary legislation end-to-end, maps every obligation to the entity that owes it, and cites the article on every answer. MiCA today. Every regulation we add inherits the same architecture.
Everything we publish is extracted from primary legislation at paragraph granularity. These numbers are live counts against the Hakadian corpus — updated within 24 hours of any ESMA or EBA publication.
MiCA’s Level 1 regulation runs to 149 articles. Since it came into force, the European Commission has adopted nine Level 2 Delegated and Implementing Regulations — covering reporting templates, order-book records, record-keeping, market abuse, sustainability disclosures and CASP authorisation. ESMA and the EBA have added dozens of Q&As, Guidelines and Statements clarifying how each article is meant to apply. More arrive every quarter.
Every compliance team we’ve spoken to is reading the same primary sources, in the same order, into the same three-column spreadsheets. The work is mechanical. The stakes — administrative fines up to 5% of annual turnover under Article 111 — are not.
The platform is organised around one promise. Any compliance officer, on any screen, can trace the answer on their monitor back to the Official Journal paragraph or ESMA publication that creates it. Eight product surfaces, one primary-source corpus underneath.
Each row is a single compliance obligation — with its regulation, article reference, severity, category, deadline and entity scope. MiCA, VARA, FCA, MAS and SEC all render the same way. Filter by any column; every record links back to its source paragraph.
Shown: a live slice of the obligations table. Platform access by subscription only.
Request a walkthrough →The ISO 20022 message schemas for MiCA trading-venue reporting — auth.116, auth.117, auth.118 — extracted down to the individual field. Every field carries its type, validation rule, and the RTS paragraph that defines it. Ready to render, ready to reconcile.
Shown: the schema browser — expand a message to see its fields. Platform access by subscription only.
Request a walkthrough →The obligation layer tells you what the regulation requires of you. The operational layer turns those requirements into signed, reconciled, audit-ready filings. Three modules, all in active development, closed to private design partners until Q3 2026.
Every reporting obligation under MiCA — and later, every crypto regulation we add — converted to a live template. Point your canonical data at Hakadian; we render the filing in the format your supervisor expects.
Before we render, we reconcile. Hakadian compares values in your trade book, client ledger and reserve book against the values about to be rendered into the report. Discrepancies surface with their magnitude, their source row, and the article the value is meant to satisfy.
Regulators do not accept “our data was wrong”. Hakadian runs a continuous break-detection layer over your reporting inputs. Each anomaly gets a severity, a workflow, a resolution owner, and a closure timestamp — captured as audit evidence.
Every answer is grounded in a cited source.
If we can’t cite it, we won’t say it.
MiCA Art. 111 sets the administrative fine ceiling at the higher of €5 million or 5% of total annual turnover, plus disgorgement of profits or losses avoided where these can be determined. These are administrative penalties only — criminal liability may apply separately under Member State law.
Hakadian covers crypto-asset regimes only — the frameworks that govern the issuance, service, and trading of crypto-assets in each jurisdiction. We start with MiCA because it is the most demanding crypto-asset regime published to date. Every framework below inherits the same structure on ingestion: article → obligation → entity → citation → status.
How Implementing Regulation 2024/2902 turns Article 22 into an EBA XBRL return. First reference date already live: 31 March 2025.
Commission Delegated Regulation 2025/416 switched trading-venue record-keeping to auth.118 JSON. NCAs start requesting the new format in Q2 2026.
Delegated Regulation 2025/413 carries MAR's STOR architecture into crypto. Event-driven, no delay, modelled on MAR 2016/957.
Explorer is free for compliance teams who want to read the structured regulation. Professional is the spreadsheet replacement. Pricing for Professional is being finalised with our first design-partner customers.
The full MiCA corpus, entity-scoped, fully cited. No credit card.
For compliance teams running real programmes across jurisdictions. The spreadsheet replacement.
If you’re a CASP, an ART issuer, an EMT issuer, or a law firm advising any of the above — and you’d rather read the regulation than paste it into a workbook — we’d like to talk.
We reply within one working day. Walkthroughs run 30 minutes, live against the platform, no deck.
MiCA Art. 143(3) allows up to 18 months for pre-existing providers to keep operating under national regimes. Many Member States have shortened that window. After 1 July 2026, every EU crypto-asset service provider needs a full MiCA authorisation — or it stops.