I was reading through Dusk’s docs and one small detail made me look at the whole “privacy blockchain” label a bit differently.
Dusk doesn’t make everything private by default.
There are actually two transaction models. Moonlight is the more familiar public account model, while Phoenix handles shielded transactions. With Phoenix, things like the sender, receiver and amount aren’t openly visible on-chain.
At first I found that a little confusing. If privacy is such a big part of Dusk, why have a public transaction model at all?
The more I read, though, the more the reasoning started to make sense. Financial activity isn’t always a simple choice between showing everything and hiding everything. Some transactions are fine being public, while others involve information that probably shouldn’t be visible to anyone with a block explorer.
And when regulated assets are involved, there can also be situations where certain information needs to be verified or disclosed without making it public to everyone.
I think the confusing part for regular users is the word “private.” Someone could easily assume that using Dusk automatically means whatever they do is confidential. In reality, it depends on which transaction model or application they’re using.
That feels like an important distinction that doesn’t get talked about much.
Maybe privacy on-chain will eventually be less about hiding everything and more about giving users control over what becomes public in the first place.
@Dusk_Foundation #dusk $DUSK
Dusk doesn’t make everything private by default.
There are actually two transaction models. Moonlight is the more familiar public account model, while Phoenix handles shielded transactions. With Phoenix, things like the sender, receiver and amount aren’t openly visible on-chain.
At first I found that a little confusing. If privacy is such a big part of Dusk, why have a public transaction model at all?
The more I read, though, the more the reasoning started to make sense. Financial activity isn’t always a simple choice between showing everything and hiding everything. Some transactions are fine being public, while others involve information that probably shouldn’t be visible to anyone with a block explorer.
And when regulated assets are involved, there can also be situations where certain information needs to be verified or disclosed without making it public to everyone.
I think the confusing part for regular users is the word “private.” Someone could easily assume that using Dusk automatically means whatever they do is confidential. In reality, it depends on which transaction model or application they’re using.
That feels like an important distinction that doesn’t get talked about much.
Maybe privacy on-chain will eventually be less about hiding everything and more about giving users control over what becomes public in the first place.
@Dusk_Foundation #dusk $DUSK