#dusk $DUSK @Dusk
Went looking for how $DUSK actually delivers "one workflow" for KYC, compliance, settlement, and ownership — and found the docs quietly split it into five separate pieces: DuskDS for settlement, DuskEVM/DuskVM for execution, Citadel for identity, Dusk Connect for wallet discovery, Dusk Trade as the product layer.
Nothing forces those pieces to combine. The docs say it outright — builders "choose what should be visible, what should be confidential, what should be disclosed." #Dusk hands you components. Whether they form one coherent workflow is integration work someone still has to do.
The one case I can point to is NPEX — issuance, trading, disclosure, and settlement described as unified into a single workflow. Worth flagging: that's Dusk's own framing of the partnership, not an NPEX-side confirmation or something verifiable on-chain. Treat it as one claimed instance, not a pattern yet.
What actually shifted for me is smaller than "it's not unified" — it's that "unified" is doing two different jobs in Dusk's messaging. Sometimes it means the protocol architecture, sometimes it means one specific deployment. Those aren't the same claim, and only one of them has evidence.
Next thing I'd check: any second live integration — beyond NPEX — that ties identity, execution, and settlement into one workflow without custom build work.
Went looking for how $DUSK actually delivers "one workflow" for KYC, compliance, settlement, and ownership — and found the docs quietly split it into five separate pieces: DuskDS for settlement, DuskEVM/DuskVM for execution, Citadel for identity, Dusk Connect for wallet discovery, Dusk Trade as the product layer.
Nothing forces those pieces to combine. The docs say it outright — builders "choose what should be visible, what should be confidential, what should be disclosed." #Dusk hands you components. Whether they form one coherent workflow is integration work someone still has to do.
The one case I can point to is NPEX — issuance, trading, disclosure, and settlement described as unified into a single workflow. Worth flagging: that's Dusk's own framing of the partnership, not an NPEX-side confirmation or something verifiable on-chain. Treat it as one claimed instance, not a pattern yet.
What actually shifted for me is smaller than "it's not unified" — it's that "unified" is doing two different jobs in Dusk's messaging. Sometimes it means the protocol architecture, sometimes it means one specific deployment. Those aren't the same claim, and only one of them has evidence.
Next thing I'd check: any second live integration — beyond NPEX — that ties identity, execution, and settlement into one workflow without custom build work.