The interesting detail about Dusk’s privacy model isn’t that it supports confidential transactions. It’s that where the privacy lives in the stack actually matters.
I checked the current technical docs, and Dusk does not describe privacy as an automatic property of every application. DuskVM is the native Rust/WASM path specifically suited to privacy and zero-knowledge capabilities, while DuskDS offers Phoenix for shielded transfers and Moonlight for public account flows.
The EVM path is different. DuskEVM is built for Solidity and familiar EVM tooling, but the docs describe confidential functionality there as a route through Hedger, rather than simply inheriting all native privacy capabilities directly.
I think that distinction matters more than the headline “confidential smart contracts.” For anyone evaluating Dusk’s financial infrastructure, the useful question is not just whether privacy exists, but which execution path a real regulated workflow actually uses, and what data remains visible at each layer.
That implementation detail is still the part I’d want to see measured in practice.
@Dusk $DUSK #dusk
I checked the current technical docs, and Dusk does not describe privacy as an automatic property of every application. DuskVM is the native Rust/WASM path specifically suited to privacy and zero-knowledge capabilities, while DuskDS offers Phoenix for shielded transfers and Moonlight for public account flows.
The EVM path is different. DuskEVM is built for Solidity and familiar EVM tooling, but the docs describe confidential functionality there as a route through Hedger, rather than simply inheriting all native privacy capabilities directly.
I think that distinction matters more than the headline “confidential smart contracts.” For anyone evaluating Dusk’s financial infrastructure, the useful question is not just whether privacy exists, but which execution path a real regulated workflow actually uses, and what data remains visible at each layer.
That implementation detail is still the part I’d want to see measured in practice.
@Dusk $DUSK #dusk