In the evening, I opened separate windows for NPEX and 21X documents, compared the license names, and stared for a long time before I realized: I had also made one of the most common mistakes in crypto circles before—assuming that the more partner logos there are, the more the regulatory capabilities can be stacked onto the same project.
When discussing Dusk’s compliance advantages, many articles recite NPEX, 21X, MTF, and DLT-TSS all at once, as if these licenses are all built into the Dusk protocol. But when you break it down, NPEX and 21X cover different pieces.
NPEX is a Netherlands-regulated market cooperation partner. Official materials mention its MTF, Broker, and ECSP capabilities: activities for the secondary market, asset sourcing and order execution, and EU crowdfunding services all fall under this line.
21X, on the other hand, obtained the DLT-TSS license under the EU DLT Pilot Regime. This allows—within a specific framework—combining trading and settlement, using public, permissionless blockchains. Dusk is currently a trading participant of 21X; deeper DuskEVM integration is still planned.
What’s interesting is that these two partnerships aren’t duplicative stamps of approval. NPEX is more like an entry point for assets, issuers, and investors; 21X is more like the regulatory channel for digital securities trading and settlement; Dusk sits in the middle providing privacy, identity, and settlement technology. Put together, the logic is pretty coherent—but “put together” doesn’t mean legal responsibilities automatically merge.
This is also where many explainers tend to overshoot: a licensed partner doesn’t mean Dusk itself automatically inherits every license; connecting to a licensed venue doesn’t mean KYC, custody, and responsibility boundaries from another institution are naturally recognized as compatible. Announcements can prove the partnership relationship, but they can’t replace end-to-end operational data.
When I look at projects like this now, I start by asking: who owns the licenses, what assets are covered, and who is responsible to users.
Do you care more about the number of licenses held by project partners, or about which legal entity the very first real transaction ultimately lands under?
#dusk $DUSK @Dusk
When discussing Dusk’s compliance advantages, many articles recite NPEX, 21X, MTF, and DLT-TSS all at once, as if these licenses are all built into the Dusk protocol. But when you break it down, NPEX and 21X cover different pieces.
NPEX is a Netherlands-regulated market cooperation partner. Official materials mention its MTF, Broker, and ECSP capabilities: activities for the secondary market, asset sourcing and order execution, and EU crowdfunding services all fall under this line.
21X, on the other hand, obtained the DLT-TSS license under the EU DLT Pilot Regime. This allows—within a specific framework—combining trading and settlement, using public, permissionless blockchains. Dusk is currently a trading participant of 21X; deeper DuskEVM integration is still planned.
What’s interesting is that these two partnerships aren’t duplicative stamps of approval. NPEX is more like an entry point for assets, issuers, and investors; 21X is more like the regulatory channel for digital securities trading and settlement; Dusk sits in the middle providing privacy, identity, and settlement technology. Put together, the logic is pretty coherent—but “put together” doesn’t mean legal responsibilities automatically merge.
This is also where many explainers tend to overshoot: a licensed partner doesn’t mean Dusk itself automatically inherits every license; connecting to a licensed venue doesn’t mean KYC, custody, and responsibility boundaries from another institution are naturally recognized as compatible. Announcements can prove the partnership relationship, but they can’t replace end-to-end operational data.
When I look at projects like this now, I start by asking: who owns the licenses, what assets are covered, and who is responsible to users.
Do you care more about the number of licenses held by project partners, or about which legal entity the very first real transaction ultimately lands under?
#dusk $DUSK @Dusk