#dusk $DUSK @Dusk A rather interesting detail in $DUSK that I don’t see being mentioned much:
Dusk doesn’t force users to choose between “public blockchain” and “private blockchain”.
It has Moonlight for public transactions — balances, senders, and recipients can be observed.
Phoenix goes in the opposite direction: assets are represented as shielded notes, using zero-knowledge proofs to prove that transactions are valid without publicly disclosing all information.
The good part is that these two models are not on two different chains. They are both supported on DuskDS and can be converted between each other. (DOCS)
In my opinion, this is the part worth paying attention to:
Privacy doesn’t necessarily mean “hiding everything”.
Some transactions need to be transparent, others need to be kept secure, and there are cases where only one party is allowed to view the information.
Dusk is trying to build the infrastructure in exactly that direction.
Not too loud, but definitely worth keeping an eye on. 👀
Dusk doesn’t force users to choose between “public blockchain” and “private blockchain”.
It has Moonlight for public transactions — balances, senders, and recipients can be observed.
Phoenix goes in the opposite direction: assets are represented as shielded notes, using zero-knowledge proofs to prove that transactions are valid without publicly disclosing all information.
The good part is that these two models are not on two different chains. They are both supported on DuskDS and can be converted between each other. (DOCS)
In my opinion, this is the part worth paying attention to:
Privacy doesn’t necessarily mean “hiding everything”.
Some transactions need to be transparent, others need to be kept secure, and there are cases where only one party is allowed to view the information.
Dusk is trying to build the infrastructure in exactly that direction.
Not too loud, but definitely worth keeping an eye on. 👀