Why would one blockchain need two different ways to move value?
Honestly, I didn’t think much about that question at first.
But when I started looking deeper into DuskDS, I noticed something I found quite interesting.
There are two native ways to handle transactions.
Moonlight is the public, account-based model. The sender, recipient and transaction amount can be visible onchain.
Then there’s Phoenix.
Phoenix works with shielded notes and zero-knowledge proofs. In simple terms, a transaction can be verified without putting the same financial details on display for everyone.
And both models settle on the same DuskDS chain.
That made me stop for a moment.
Because I don't think every financial transaction needs the same level of visibility.
Sometimes you want the activity to be easy to verify.
Other times, exposing the amount or financial position to the whole network simply doesn't make much sense.
What I find interesting is that Dusk doesn't seem to force one answer for every situation. It also has viewing keys for cases where information needs to be disclosed to an authorized party.
Maybe I'm looking at it too simply, but this changed the way I think about blockchain privacy.
Good financial privacy isn't about hiding everything. It's about knowing what should be visible, and to whom.
That sounds much closer to how real financial systems actually work.
So I'm curious:
Should a financial blockchain decide the visibility for every transaction, or should the transaction itself determine what needs to be seen?
#dusk $DUSK @Dusk
Honestly, I didn’t think much about that question at first.
But when I started looking deeper into DuskDS, I noticed something I found quite interesting.
There are two native ways to handle transactions.
Moonlight is the public, account-based model. The sender, recipient and transaction amount can be visible onchain.
Then there’s Phoenix.
Phoenix works with shielded notes and zero-knowledge proofs. In simple terms, a transaction can be verified without putting the same financial details on display for everyone.
And both models settle on the same DuskDS chain.
That made me stop for a moment.
Because I don't think every financial transaction needs the same level of visibility.
Sometimes you want the activity to be easy to verify.
Other times, exposing the amount or financial position to the whole network simply doesn't make much sense.
What I find interesting is that Dusk doesn't seem to force one answer for every situation. It also has viewing keys for cases where information needs to be disclosed to an authorized party.
Maybe I'm looking at it too simply, but this changed the way I think about blockchain privacy.
Good financial privacy isn't about hiding everything. It's about knowing what should be visible, and to whom.
That sounds much closer to how real financial systems actually work.
So I'm curious:
Should a financial blockchain decide the visibility for every transaction, or should the transaction itself determine what needs to be seen?
#dusk $DUSK @Dusk