#dusk $DUSK @Dusk
Dusk is building toward a split design — DuskDS running Piecrust with zero-knowledge proof and a separate DuskEVM layer meant to run standard Solidity through Hardhat and MetaMask.
I assumed that made DuskEVM the "transparent" side. It doesn't, at least per one Dusk roadmap post — DuskEVM is planned to get homomorphic encryption for confidential transactions and obfuscated order books. Different math, not an absence of privacy.
So this isn't "one private chain with a public onboarding ramp." It's two separate privacy stacks aimed at two developer audiences — ZK proofs on one layer, HE on another. Two cryptographic approaches to maintain and audit instead of one, for whatever that ends up meaning in practice. Still roadmap, not shipped: the docs describe DuskVM as "currently embedded in DuskDS but being extracted" into its own layer.
Worth checking next: whether that extraction has actually landed or if DuskEVM's HE-based confidentiality exists anywhere outside the announcement....
Dusk is building toward a split design — DuskDS running Piecrust with zero-knowledge proof and a separate DuskEVM layer meant to run standard Solidity through Hardhat and MetaMask.
I assumed that made DuskEVM the "transparent" side. It doesn't, at least per one Dusk roadmap post — DuskEVM is planned to get homomorphic encryption for confidential transactions and obfuscated order books. Different math, not an absence of privacy.
So this isn't "one private chain with a public onboarding ramp." It's two separate privacy stacks aimed at two developer audiences — ZK proofs on one layer, HE on another. Two cryptographic approaches to maintain and audit instead of one, for whatever that ends up meaning in practice. Still roadmap, not shipped: the docs describe DuskVM as "currently embedded in DuskDS but being extracted" into its own layer.
Worth checking next: whether that extraction has actually landed or if DuskEVM's HE-based confidentiality exists anywhere outside the announcement....