The regime in brief
Regulation (EU) 2022/858 established the pilot regime for market infrastructures that use distributed ledger technology: DLT multilateral trading facilities (DLT MTFs), DLT settlement systems (DLT SS), and combined DLT trading and settlement systems (DLT TSS) — for financial instruments issued onchain, subject to instrument-level notional and issuance thresholds.
Adoption is real but early: as of September 2026 the regime counts a small number of authorized DLT market infrastructures, including a single DLT MTF. That scarcity is the opportunity — the cohort of authorized operators is small, the applicant pipeline is growing, and every one of them needs venue software that produces supervision-grade evidence.
What's changing
An amending framework is reshaping the regime around smaller operators: a new DLT Trading Venue category closer to the OTF operating model, more flexible thresholds, and simplified capital treatment for smaller platforms. The direction of travel is unambiguous — the EU is widening the funnel for DLT venue authorization. (Amendment status should be verified against the Official Journal at any given moment; the software posture below does not depend on the outcome.)
What a DLT MTF applicant needs from software
| Obligation area | What the software must produce |
|---|---|
| Participant admission | Tiered admission under the venue's standards, enforced at a single onchain choke point — with an admission event log supervisors can read |
| Records & transparency | Complete, replayable, hash-chained record of every action; extracts generated from one versioned event stream rather than reconstructed from logs |
| Thresholds | Instrument-level notional and issuance thresholds as configuration, with monitoring and breach handling — thresholds are policy, not code |
| Reporting | Transaction and periodic reporting generated downstream of the event stream, in the formats the NCA expects |
| Settlement-asset policy | Quote-asset admission flags per instrument — including EU-native issuance requirements — enforced at listing |
| Resilience | Fail-closed behavior on data-feed loss, deterministic replay of every decision, documented recovery procedures |
The EU market-access realities
- Double authorization. An operator serving EU users with crypto-asset services plus operating a DLT venue generally faces both a CASP authorization and the DLT-regime authorization. Plan the perimeter as one architecture with two rulebooks, not two systems.
- EU-native settlement assets. EEA users must use EU-native issuance for regulated settlement tokens; non-EEA stablecoins are not usable for them. This is a per-deployment quote-asset policy — trivial when settlement assets are rulebook configuration, painful when they're hardcoded.
- Technology neutrality. Nothing in the regime privileges or excludes AMMs — but the ESMA perimeter reading is that an identifiable operator of a permissioned system cannot claim decentralization exemptions. The permissioned-AMM architecture described here fits: accountable operator, deterministic mechanism, supervision-grade records.
How clarivyx maps to the regime
The same core that runs the US TSV rulebook runs the EU deployment: pools and policy choke point onchain; the Rust operator layer producing records, thresholds, admission and reporting; and an EU rulebook carrying the instrument scope, threshold values, admission tiers and EU-native quote-asset policy. Authorization strategy, National Competent Authority engagement and filing remain yours — as they should.
Frequently asked questions
What is the difference between a DLT MTF and a DLT Trading Venue?
Can a non-EU company operate under the DLT Pilot Regime?
What settlement assets can a DLT venue use in the EU?
Applying under the pilot regime?
Bring your instrument scope and target NCA. We'll return the EU rulebook draft — thresholds, admission tiers, quote-asset policy, reporting formats — and the conditions-to-behavior mapping for your authorization file.