Dusk ($DUSK #dusk @Dusk Foundation) doesn't just imply its compliance is protocol-native — it says so directly. Dusk's own July 2025 post states that through NPEX, Dusk gains a full suite of financial licences — MTF, Broker, ECSP and the forthcoming DLT-TSS — embedding compliance across the protocol (CoinDesk) .
Read that list carefully. Through NPEX, Dusk inherits the MTF, Broker, and ECSP licenses, while the DLT-TSS license — which would enable native issuance and tokenization of regulated assets on-chain — is still listed as in progress (CoinDesk) . The one license that would let Dusk issue assets without routing through NPEX is the one that isn't live yet.
What changed for me: this isn't an arm's-length vendor deal either. Dusk acquired roughly a 10% stake in NPEX back in 2020 (Tracxn) . So "protocol-level compliance" currently rests on partial ownership of one Dutch MTF holder, not on Dusk possessing regulatory standing in its own name.
Until DLT-TSS goes live, "licenses embedded in the protocol" reads closer to "licenses embedded in an affiliate." That's a meaningfully different institutional trust model than the phrasing suggests.
What I'd verify next: DLT-TSS approval status, and whether it transfers issuance authority to Dusk directly or keeps NPEX as permanent license-holder of record.