I was reading through Dusk's page on the NPEX partnership, and one detail caught my attention: a mention of a "DLT-TSS" license. I hadn't come across that term in a blockchain context before, so I assumed it was internal Dusk terminology.
After checking the official page, it turned out to be an actual regulatory category, a DLT Trading and Settlement System license, one of the newer designations under EU pilot regime rules for market infrastructure running on distributed ledger tech.
What surprised me was comparing that page against Dusk's earlier NPEX announcement. The original 2023 release described NPEX simply as an MTF-licensed exchange. The more recent "Regulatory Edge" page lists a fuller stack: MTF, Broker, ECSP, and the forthcoming DLT-TSS. That's a noticeable shift in scope between two official materials from the same source, not a contradiction, but a sign the partnership's regulatory coverage expanded over time rather than being fixed from day one.
The cautious read here is that Dusk isn't claiming its own license, it's inheriting NPEX's existing regulatory standing across the stack. That's a trade-off by design: it ties Dusk's compliance story to NPEX's licensing progress instead of a standalone framework.
Which raises a real question: once DLT-TSS is finalized, does that change what kinds of assets can settle on Dusk, or mainly formalize what NPEX already does?
#dusk $DUSK @Dusk
After checking the official page, it turned out to be an actual regulatory category, a DLT Trading and Settlement System license, one of the newer designations under EU pilot regime rules for market infrastructure running on distributed ledger tech.
What surprised me was comparing that page against Dusk's earlier NPEX announcement. The original 2023 release described NPEX simply as an MTF-licensed exchange. The more recent "Regulatory Edge" page lists a fuller stack: MTF, Broker, ECSP, and the forthcoming DLT-TSS. That's a noticeable shift in scope between two official materials from the same source, not a contradiction, but a sign the partnership's regulatory coverage expanded over time rather than being fixed from day one.
The cautious read here is that Dusk isn't claiming its own license, it's inheriting NPEX's existing regulatory standing across the stack. That's a trade-off by design: it ties Dusk's compliance story to NPEX's licensing progress instead of a standalone framework.
Which raises a real question: once DLT-TSS is finalized, does that change what kinds of assets can settle on Dusk, or mainly formalize what NPEX already does?
#dusk $DUSK @Dusk