Been reading through the @Dusk_Foundation docs today, and I think one part is easy to misunderstand.
When people hear “privacy blockchain,” it’s tempting to assume the goal is simply to hide everything. But Dusk’s design is more nuanced than that.
Dusk has two native transaction models: Moonlight, where accounts and transfers are public, and Phoenix, where balances and transfers are shielded using zero-knowledge proofs. With Phoenix, transaction details such as the amount and sender are not exposed publicly, while viewing keys can be used for selective disclosure when information needs to be shared.
That distinction is important because privacy here isn’t treated as the opposite of transparency.
The idea is more about choosing what should be visible.
This also connects with Dusk’s Confidential Security Contract (XSC) standard. XSC is designed for confidential smart contracts that can incorporate requirements such as privacy constraints and compliance rules.
So I wouldn’t describe Dusk simply as a blockchain where transactions disappear from public view. It is closer to a system where different financial workflows can have different levels of visibility.
That makes me wonder: for regulated financial applications, is selective privacy actually more useful than making everything private by default?
@Dusk_Foundation #dusk $DUSK
When people hear “privacy blockchain,” it’s tempting to assume the goal is simply to hide everything. But Dusk’s design is more nuanced than that.
Dusk has two native transaction models: Moonlight, where accounts and transfers are public, and Phoenix, where balances and transfers are shielded using zero-knowledge proofs. With Phoenix, transaction details such as the amount and sender are not exposed publicly, while viewing keys can be used for selective disclosure when information needs to be shared.
That distinction is important because privacy here isn’t treated as the opposite of transparency.
The idea is more about choosing what should be visible.
This also connects with Dusk’s Confidential Security Contract (XSC) standard. XSC is designed for confidential smart contracts that can incorporate requirements such as privacy constraints and compliance rules.
So I wouldn’t describe Dusk simply as a blockchain where transactions disappear from public view. It is closer to a system where different financial workflows can have different levels of visibility.
That makes me wonder: for regulated financial applications, is selective privacy actually more useful than making everything private by default?
@Dusk_Foundation #dusk $DUSK