DUSK — the interesting detail is that XSC itself is not the whole privacy mechanism. It is better understood as a contract standard sitting inside a larger privacy-and-compliance stack.

Dusk’s current docs define the Confidential Security Contract Standard as a way to build confidential smart contracts around requirements such as privacy constraints and compliance rules.

Then I checked where confidentiality actually comes from.

At the protocol layer, Dusk separates public Moonlight transactions from shielded Phoenix transfers.

Phoenix uses zero-knowledge proofs so transaction details such as amounts and specific notes can remain hidden, while viewing keys can support controlled disclosure.

That distinction matters because an XSC-compatible financial workflow is not automatically equivalent to a fully private workflow. Dusk’s own architecture also puts selective disclosure and identity controls in Citadel, while smart-contract execution can happen through DuskVM or DuskEVM.

So the useful question is less “Does Dusk have XSC?” and more: which real financial workflows actually combine XSC-style contract rules with shielded transfers and selective disclosure in production?

@Dusk $DUSK #dusk