Direct answer
MiCA and MiFID II are important starting points, not a complete launch checklist. Depending on the products and venue, an EU crypto exchange may also need to assess EMIR, MiFIR, MAR, PRIIPs, DORA, AML and transfer-of-funds rules, benchmarks, market data, outsourcing and local implementation. The stack is conditional: a rule should be tied to an actual product, entity or control.
Key facts
Rules follow facts
The stack changes when an exchange adds derivatives, retail distribution or tokenized instruments.
DORA and outsourcing
Technology, resilience and third-party arrangements are part of the launch story.
Rights and benchmarks
A reference price is also a licensing and governance dependency.
At a glance
| Layer | Why it may matter | Typical evidence |
|---|---|---|
| Market conduct | Trading, reporting and abuse controls | Surveillance, reporting and escalation procedures |
| Product and retail | Disclosure and distribution | Terms, target-market and product-governance records |
| Technology and data | Resilience, outsourcing and reference prices | ICT, vendor, benchmark and incident controls |
A practical sequence
Start with services
List each customer-facing service and product, including the reference asset.
Add the venue
Document order handling, matching, settlement, custody and reporting.
Attach adjacent rules
Map each rule to a fact, control, entity and accountable owner.
Create a versioned map
Review the stack as products, law and regulator feedback change.
The licence is not the operating system
A licence may open a regulatory door, but the exchange still needs systems that make its promises true. Reporting, disclosures, resilience, vendor controls and market surveillance sit behind the public authorisation.
That is why a good project does not end when the application PDF is assembled.
Why the stack should stay conditional
Listing every EU acronym can create the impression that every rule applies in the same way to every platform. That is not a useful compliance method.
The better approach is to connect each rule to a product, service, entity or control and record the assumption.
The practical payoff
A versioned regulatory stack helps an exchange decide what to build now, what to ask the provider, and what to leave outside the first launch.
It also gives engineering and compliance teams a shared language for change management.
Frequently asked questions
Does MiCA cover DORA?
No. DORA and other operational rules may require separate analysis.
Does MiFIR apply to every exchange?
Not automatically; the products, venue and activity determine relevance.
Are market-data rights a legal issue?
They can be, especially for indices, stocks and benchmarks.
Should every acronym be on the first page?
Only when tied to a real product or control question.
Does a stack map guarantee compliance?
No. It is a planning and accountability tool.